Maybe you don’t have any errors. Which is not a bad thing
You can test this theory. Trigger a GPS no lock for 5 seconds by putting your hand over the GPS until lock is lost, and keep in there for 5 seconds. OR Trigger Battery Failsafe (FS_BATT_VOLTAGE) by setting the voltage to higher voltage i.e 12.2V for a 3S, for example. Wait for the voltage to trigger the condition, then check for the corresponding ERR message in the log
This came about because I was stuck with FAILSAFE plastered on the MP HUD and couldn’t figure out what was causing it. The data flash log wasn’t behaving as the wiki said, so I was unable to see exactly what was causing the HUD display. I finally cleared the problem, but still don’t know what it was.
Still have the data flash, if it would help with documenting how to pull the ERR entries.
I’m confused, too. The FAILSAFE was in the HUD throughout the entire day, both flights in the morning and in MP for a couple of days until I was able to clear it. Obviously, the ERR message option only shows in the data flash when there is an error, but all 4 data flash files were created within about 2 hours from start to finish. Batteries connected, arm/disarm while trying to clear it in the HUD. Very frustrating, sigh.
Thanks for finding it, I guess I kept checking files 1,3, and 4. 8-(
I realize MP just shows what is coming over the data stream. Other then checking all the params, can you think of a way to have diagnosed the error? The other data flash files were all when the APM was armed and I had the same HUD banner.