Recent content by BudWalker

The "Total Error Ratio 100,34%" is an indication that DatCon couldn't make any sense of the .DAT. Perhaps I should be a bit more direct. DatCon will not work for any of these files you are asking asking about. When CsvView is given a file with the .DAT extension CsvView will use DatCon to...

Not that I'm aware of. What happens when one of these files is submitted to DatCon?

Good question. The P4P did seem to be in a bit of a hurry. I've noticed this with my P3 when RTH was caused by a low battery. The eventLog from the .txt log had this entry "1163.8 : Low power. Returning home.; RTH: Preascending.; Flight mode changed to Go Home."

You're right. The abrupt power loss was caused by the impact with the ground. The impact is seen in the accelerometer data Looks like the impact started at about 1197.865 secs, just 0.07 secs before the .DAT ends. At 1197.242 full throttle was applied. The P4P had been increasing motor...

This is a bit different than several other P4 incidents where there was an abrupt loss of power. Most look like this Beginning to hate phantoms ... In your incident the voltages fluctuated some before collapsing I don’t have a compelling explanation why one of the voltages increased to the...

Can you provide FLY107.DAT and FLY108.DAT using Dropbox or GoogleDrive? Often it's unclear exactly what significance eventLog entries have.

Bummer. Was the battery on when you retrieved the P4?

Nothing unusual about the .txt log except that it stops abruptly. This is usually caused by a battery that comes loose. The .DAT from the P4 will have info that will allow us to determine if this what happened. If the P4 is like the P3 then the desired USB port will be in the nose, not in the...

Can you provide the flight logs that you have?

Good luck with this. I'm the author of DatCon which is a Java app that converts a .DAT log file to .csv. The source code can be found at GitHub - BudWalkerJava/DatCon There have been a few attempts that I know of to convert the Java code to Python. AFAIK these attempts were not successful...

All the DJI drones I know about will maintain an IMU temperature of 65° Celsius. That's 149° fahrenheit. I.e., the IMU temperature you're seeing is normal.

Can you provide the .DAT here? You will need to use a public sharing site like DropBox or GoogleDrive.

It would appear that the right front motor has a problem. Compared to the other motors the current is generally higher and very erratic. Here the red plot shows the right front motor current. Looking at the last second or two of accelerometer data the impact with the ground occurs at 92.418...

That's probably best. I can't really determine the cause. E.g. at the end where motorSpeeds go to 0 the voltage at the motors shows 0.0. That shouldn't happen. Normally, the motor voltages will be close to the battery voltage. I don't know what would cause that...

I'm still looking at FLY210.DAT (the first flight). But, FLY212.DAT looks like the software crashed at time 7.375 secs when the P4PRTK was at 4.6 m above take off. Looks like it had travelled 2.6 m from launch site. Is there anything more you can say about the second flight?