- Joined
- Dec 28, 2016
- Messages
- 113
- Reaction score
- 24
You're right. You're .DAT stimulated 2 bugs, one in DatCon , the other in CsvView. Independently they each don't cause a problem. But, together they are a problem. Anyway, I'll be fixing those bugs. I've attached a .zip containing a .csv that can be fed to CsvView and a FLY048.txt.log. These include the second flight you referred to.
At time 980 APP_AUTO_GOHOME was initiated at the direction of the pilot. Following at time 1007 connection with RC was lost and the go home action changed to OUTOF_CONTROL_GOHOME.
It's worth noting, according to the eventLog stream, that the AC was aware of the airport restriction at time 927. See the attached FLY048.txt.log. I haven't looked closely, but it doesn't seem that the AC's flight path was ever affected by this.
Not much changed as a result of the RC disconnect. The AC had already entered a GoHome and had turned towards home. It then flew sideways (to the left) and started descending.This continued after the disconnect but the descent stopped at 20 meters.
View attachment 76430
View attachment 76431
View attachment 76432
Just for grins I took a closer look at the the very end of the recording. To do this I ran DatCon with a sample rate of 200 hZ instead of the default 30 hZ. Then looked at the volts being applied to the motors by the ESC. This is much higher speed data than the battery data.
View attachment 76442
I'll speculate that the voltage fluctuation at the very end was the result of the battery coming loose.
Wow, that's interesting analysis... I just wonder if the flight controls were some way confused being at the boundary of the authorized zone. The log entries that I saw seemed to bounce back and forth like it was arguing with itself about what to do. That's an over-simplification, but my concern all along has been that the software didn't perform as we understood it should.
When my son commanded a RTH, since the direction it turned was away from the authorized flight zone, I could see no reason for it to hesitate. It appeared to begin gaining altitude, then went back on its downward path and disconnected. The fact that it hovered at 20 meters for some time then began descending again is odd. Could the last little bit of time where the voltages went nuts been it coming into contact with a tree? In Google Earth 3D, the last elevation was close enough to the height of trees in the vicinity that it wouldn't surprise me. I know the 3D render is just an approximation based on the aerial photos it has available, so trees could've been taller, and altitude wouldn't be precise enough to exclude that possibility.
Thanks for your efforts on this... we are not yet ready to test fly the P4 after this. I am pretty sure the firmware is in need of updating, so if anyone has words of advice or warning about which version to avoid, would appreciate that as well as feedback on DJI Go vs. DJI Go 4.