Since DJI encrypt the screen device DAT of some FLY App using drones and seemingly delete the DATs during a sync, it would be very helpful,  FOR ALL FLY App using drones if the motor rpms could be added to the .txt flight log.


In fact I think I will turn this into a poll to see how many members favour the idea.

Please vote rather than just have a look at the thread.
Thanks for looking and, if you vote, participating.

Edit.
With BudWalker's comment in mind I have added a 3rd option. If you use it please say in a post/reply what you think would be better.
I have also increased the number of votes to two.
Edit 2
It looks like those who have voted are stuck with their original single vote, sorry about that !

Edit 3
from Mobilehomer's comment, #16, in order to see the poll you may need to use a computer.
I've added a 4th option, it was supposed to read
"I think adding the motor rpm's would be a good idea but I also think additional data streams would add to the value of the  motor rpm's", if you tick the 4th option please say what additional data you think would be useful.

Voted to see it added

+1 this could prove very useful.  

Why not adding this? May be helpful in solving a crash and other things.

Only if it is not going to cripple even more a hot running CPU/GPU like the one in the Mini 3 Pro...

Burt37 Posted at 9-10 00:09
Only if it is not going to cripple even more a hot running CPU/GPU like the one in the Mini 3 Pro...

Thanks for the PM...

The motor rpms are already recorded in the screen device DAT and presumably the DAT on the Mini 3 Pro and the other DJI models so this will not add to the work load of the drone's cpu.
The problem for people who sync their logs is that the screen device DATs are deleted during a sync and the drone's DAT is encrypted and unreadable to anyone bar DJI.
Additionally, with some FLY app using drones the screen device DAT is also encrypted e.g. the mini 2 and, I think, the Mavic 3 series.
So, quite often, people come here seeking assistance and they have no means of finding out the motor rpms i.e. they have no access to the relevant DAT, and motor rpms would be quite useful at times.

Yes, that would be helpful sometimes.

Motor RPMs weren't useful to me in the last six incidents that I've looked at. Based on these incidents my vote would be for the following data

GPS velocities (velE, velN, velD). These are different from the velocities computed by the Flight Controller.
magnetometer data (IMU_ATTI: magX, magY, magZ)
gyro data (IMU_ATTI: gyroX, gyroY, gyroZ)

Which quadrant losses thrust can usually be determined from the roll, pitch and heading data found in the .txt. Which type of propulsion loss (lost prop or blocked motor) requires knowing motor currents. So if motor RPMs are to be included in this list then motor currents should also be included.

BudWalker Posted at 9-10 07:12
Motor RPMs weren't useful to me in the last six incidents that I've looked at. Based on these incidents my vote would be for the following data

GPS velocities (velE, velN, velD). These are different from the velocities computed by the Flight Controller.

You’re right and I see know reason it cannot be shown along with RPM’’s

error
cheers
JJB

Dirty Bird Posted at 9-10 05:24
When you own one let us know.

Give up man... You are boring now...

Burt37 and Dirty Bird please do not start bickering in this thread.

???

No poll, just discussion.

dwallersv Posted at 9-10 14:27
???    No poll, just discussion.

I suggest you look again.

Sean-bumble-bee Posted at 9-10 14:42
I suggest you look again.

He's probably on a phone. Polls don't show up on the mobile browser.

Thank you for your recommendations. Please rest assured that we will register the information and provide feedback to the related departments for evaluation. In the future, we will optimize and improve the product or service based on user comments. Thank you for your support and understanding.

Thanks Tony.

Sean-bumble-bee Posted at 9-15 01:20
Thanks Tony.

You are most welcome Sean. Have a great day ahead.

Being able to see the data for motor speeds was very helpful for monitoring the performance health of Mini prop blades, back when prop deformation due to improper storage was such a big issue.

Zbip57 Posted at 9-16 05:03
Being able to see the data for motor speeds was very helpful for monitoring the performance health of Mini prop blades, back when prop deformation due to improper storage was such a big issue.

Indeed it was Zbip57 and thanks. BTW, if I may ask, did you vote?

Sean-bumble-bee Posted at 9-16 05:56
Indeed it was Zbip57 and thanks. BTW, if I may ask, did you vote?

Strange.  I'm on a computer, using Firefox browser, and didn't see the poll before.  But it showed up just now.  Voted now.

Zbip57 Posted at 9-16 11:27
Strange.  I'm on a computer, using Firefox browser, and didn't see the poll before.  But it showed up just now.  Voted now.

Great, cheers.