Open chucky-whiskers opened 11 months ago
Not a solution. But hopefully it will put your mind at ease. No settings are save in flight. You have to disarm to trigger that save event. Then it is only continuous servo trim and stats that will do this.
Auto tune and auto level trim do not call for the settings to be saved.
Could this be related to the compiler toolchain change for Inav 7 and optimization levels conflict that has already been discussed here?
https://github.com/iNavFlight/inav/issues/8905#issuecomment-1495278006
@chucky-whiskers I agree with your observation. Do you also experience problems with this flight controller refusing to connect to the configurator, when black box logging is enabled ? I've found this to be the case with every SD card and workaround I have tried. And nothing short of disabling the logging helps.
I have not used an SD card or logging with this flight controller yet.
Can you please check if this is still an issue with 7.1 RC1? Then we can have a look again.
Yep. Its still a problem. Especially when logging is enable. IF you're lucky to get it to log in the first place.
OK testing time tomorrow. Have not yet updated my clouds above 6.1.1
I am having this issue while saving custom programming logic. Once I save receiver input freezes
Same issue on Matek H743 Wing V2 Inav 7.1.1 FC firmware 7.1.2
Found about the issue during OSD setup. Lucky me, as I had continuus servo trim on, and planned Maiden with fpv, not classic. 2.4m glider wing, ~1.5kgs, flying by itself .... quite scary i would say.
Regarding black box SD card: it was quite frustrating before i found solution which is: do not to use it :)
PLEASE DELETE THE TEXT ABOVE AFTER READING AND UNDERSTANDING IT
Current Behavior
INAV runs properly on flight controller when configurator is connected until EEPROM is saved without a reboot. Radio connection is still present, but the servos and motors lock up and receive no commands (even in manual mode). Configurator also can no longer communicate with FC until rebooted.
Steps to Reproduce
Expected behavior
The EEPROM settings should save and the program should continue to run without glitches.
Suggested solution(s)
Force a reboot when saving all settings or find the glitch in the program. I'm worried that something like auto-tune will save in-flight and cause the system (and plane) to crash.
Additional context
I HAVE TRIED REFLASHING FIRMWARE.
https://pastebin.com/g2aArQcd