At time 402 the ultrasonic height sensor went from 5.4 meters to 0 indicating the Mavic sensed something immediately below it. The response was to speed up to avoid the obstacle. There was no control input at this point.
Yeah, I thought about that. Doesn't make complete sense to me either. I was supposing there might be some subtlety involving being in the Active Track mode. The timing was just too compelling as it was only 0.35 secs from the ultrasonic height going to 0.0 and the horizontal speed starting to increase. I suspect that time interval is even less if motorCommanded speed were looked at in the .DATIs it expected behavior for the Mavic to move forwards to avoid an obstacle? I've never experienced nor heard of that kind of response. I've only ever seen the Mavic ascend to avoid an obstacle below it.
Hi, thanks for the deep analysis.Yeah, I thought about that. Doesn't make complete sense to me either. I was supposing there might be some subtlety involving being in the Active Track mode. The timing was just too compelling as it was only 0.35 secs from the ultrasonic height going to 0.0 and the horizontal speed starting to increase. I suspect that time interval is even less if motorCommanded speed were looked at in the .DAT
My mistake. That changes everything. I forgot, the .txt uses 0.0 for vpsHeight when the sensor isn't reporting a value. The .DAT conversion represents this undefined state properly.Hi, thanks for the deep analysis.
I updated the .DAT file with the correct one. I'm not sure if it helps more but from this file I can see that as you said the vpsHeight suddenly goes to "?" which corresponds to 0 in the txt. The strange part is the Pitch between 403 and 405. This actually corresponds to the noise I heard when it was approaching me. It was tilting like crazy from side to side while going forwards (this is not seen in the video because of the gimbal). The main root cause of this behavior is still not clear to me. As you said if vpsHeight suddenly goes to 0 it should try to ascend.
BTW the vpsHeight drops to 0 several times in this log but only the last time the Mavic goes crazy.
If you notice when watching the video. The distance and altitude displays on screen hardly change a jot as the Mavic is careering towards you. The Mavic must of thought it was virtually stationery.......and was having a blonde moment....what could that point to?
Hmmm, just watched this video of P4 active track, I'd be ready to switch out and will be cautious with profile mode.
Sent from my iPad using Tapatalk
Hi all,
I'm pretty new in the forum but I have one very interesting case to share with you which happened 2 days ago with my Mavic.
The Mavic was in Active Track (Profile) mode and suddenly it accelerated towards me and my wife. Luckily it missed us and nobody was hurt. I was able to pull the sticks Up and Backwards which forced the Mavic to stop otherwise it would have crashed into us or in the trees.
Here is the Flight Log (issues occurs around 7th min): Phantom Log Viewer - PhantomHelp.com
Here is the DAT file (updated): FLY055.DAT
Here is the Video from my phone of the actual accident (50s):
I didn't press anything on the remote or in the app, and according to the logs there were 13 satellites and no problems with the battery or compass. However, maybe I missed something in the log which caused this strange behavior. Please, give it a look and let me know what could cause this spontaneous change in the flight of my Mavic.
This was the second battery that day with no issues. I flew it the day after with no issues again but didn't try the Profile mode If you are interested, here is the video from the same day before the accident:
And soon I will post a video from the following day skiing with my friends.
Regards,
Dimitar
Yes, this happened the day before the last update came on my phone.was all batt firmwares updated?
We use essential cookies to make this site work, and optional cookies to enhance your experience.