Has anyone experienced this message during flight and still managed to land safely without issues?
Is there a restriction on altitude from your settings? And you are crossing it? Give more details to us.
I can guess that controls are trying to suddenly limit height by reducing motor speed and large deviation in motor currents is triggering this message.
Give us your logs.
Anyway check props for safety
Looks exactly what happened to me. I'm willing to bet the first log will show some sort of data disconnect error. I have a feeling the app likes to freak out on short total disconnects. What versions of firmware and Go are you running?
The quad might not have liked being knocked around at that speed, may have thrown the error from aggressive stability correction? Does the error show up in the DJI Go log when you play it back?
I wonder if it reached an RPM that the motors typically only hit with no load (no props) due to the wind pushing the craft faster.
Is there a restriction on altitude from your settings? And you are crossing it? Give more details to us.
I can guess that controls are trying to suddenly limit height by reducing motor speed and large deviation in motor currents is triggering this message.
Give us your logs.
Anyway check props for safety
There are two .DATs, each for a separate flight. Did the warning message occur in each of these flights? Would it be possible for you to post the .txt files for these two flights? It might be easier if you uploaded them to https://www.phantomhelp.com/LogViewer/Upload/ and then provide the link here.Here are the flight logs + dat files off the bird. Hopefully you can see what went wrong.
Dropbox - 5-7-16
There are two .DATs, each for a separate flight. Did the warning message occur in each of these flights? Would it be possible for you to post the .txt files for these two flights? It might be easier if you uploaded them to https://www.phantomhelp.com/LogViewer/Upload/ and then provide the link here.
I wasn't able to do much with this flight. FLY399.DAT corresponds to the two .txt files. I don't know why the .txt got split into two files but it's clear that those two .txts correspond to FLY399.DAT.
The warning message didn't appear in the .csv generated by DatCon from FLY399.DAT. But, I think that's because DatCon doesn't know about those types of messages. I had asked for the .txt file so that I could know what time the message occurred which would help locate that info. That would've allowed me to implement that in DatCon.
I believe you when you say that the message doesn't appear on the playback because I've seen the same thing. In my case the Go app said "compass error" which did not appear on the replay. Several months later with a newer version of the Go app what appears is "GPS no signal" on a greyed out screen. Go figure.
Sorry I couldn't help much. If it happens again I'd definitely be interested in looking at the .DAT and .txt for that flight.