inav
inav copied to clipboard
iNavFlight
Complete configuration being wiped
There seems to be an issue in 3.0 where the flight controller randomly loses its configuration. I had this problem once but assumed it was something I did wrong. However, since the 3.0 release, at least two other users on FB reported this problem so I think it is a bug.
The steps I took to get run into this problem were:
- Have a
difffrom a previous 3.0 setup - Flash the 3.0 stable release
- Choose "Airplane without a tail" platform
- Restore
diff - Power cycle with a battery (don't know if it happens with just USB power)
- Notice the configuration has been wiped
The problem is I have done these exact steps 10's of times with the RC's and older beta builds, and only encountered this problem once. So far I have also not heard anyone running into this issue multiple times. I wouldn't know how to reproduce it again.
I realize that this makes it very difficult to find the cause so I'm opening this issue to collect more experiences. Maybe it rings a bell for someone.
Couple of point: 3 users complains about the same all on F411-wse so far. We setup the FC from scratch, all is ready for maiden. Connect the FC again to inav for more checks of config and the FC is completely reset. Matek says they are not aware of issues like this. I had no issues on previous builds.
Testing but quick note: I've been using a F411-WSE on 3.0 since 2.6 came out and have not seen the issue. Are we sure that the problem is not people forgetting to type save? :)
Testing but quick note: I've been using a F411-WSE on 3.0 since 2.6 came out and have not seen the issue. Are we sure that the problem is not people forgetting to type save? :)
Seriously?! Sorry, we are very dumb peoples...
Haven't seen this issue on F411-Wing... yet. Have reflashed the board several times this week and the only difference from the above mentioned steps is that I do not do 3. Choose "Airplane without a tail" platform, but the rest is all the same. The firmware is the one with double softserials enabled.
Experienced it a few months back using development FW. Was an F411_wing.
The Windows configurator has become very sluggish in 3.0. PID, Advanced and OSD tabs are very slow to open, And the reboots are slow sometimes too.
I've got into the habit of closing the configurator and power cycle the FC (USB only) after a flash. And do the same after loading diff all files.
The Windows configurator has become very sluggish in 3.0. PID, Advanced and OSD tabs are very slow to open, And the reboots are slow sometimes too.
that's known because of a lot more stuff get's loaded on these pages compared to older versions. The developers know about this and will address it in the future. But that means a lot of rework how the Configurator communicates with the FC. For now we have to live with it.
regarding the main issue: I have unfortunately (or luckily) not seen that yet on any of my planes. But Where I have seen a simular issue is on my U360GTS antenna tracker that is running on an SPRacing F3 witht he latest release candidate firmware. and it happened multiple times on one evening. Sometimes with battery power cycle, sometiomes with USB power cycle. All Config wiped.
So there is something that can indeed happen to the flash memory to lose all the config. The latest added feature to the tracker firmware is a home save option that can restore the last home point after a power loss. So the Tracker is writing to the flash memory while it is running.
I wonder if there is something in INAV that can write to the flash even when no settings is changed by the user and the plane was not armed and corrupts the flash storage?
It would be good to know the status of the LEDs if someone can reproduce the issue.
I've run into the problem a couple of times when restoring (parts of) diffs, but I cannot reproduce it reliably.
its random, maybe 1 in 10/20 reboots...
When you say "reboots" are you talking about rebooting through CMS or power cycles?
restoring (parts of) diffs...
This is a different story, happened to me yesterday just after posting my previous message. Copied maybe 25 diff lines because I have seen some red warning message and wanted to see what was it about. Without saving, and just exiting the CLI (which means reboot) and reconnecting to Configurator the setup message for selecting the type of vehicle appeared (as when starting from scratch).
its random, maybe 1 in 10/20 reboots...
When you say "reboots" are you talking about rebooting through CMS or power cycles?
Yes. Unplug/ plus usb only, or battery only.
its random, maybe 1 in 10/20 reboots...
When you say "reboots" are you talking about rebooting through CMS or power cycles?
Yes. Unplug/ plus usb only, or battery only.
Cool. Next time it happens check the LEDs. I want to rule out a faulty DFU boot button.
I think it it very unlikely that this is a hardware issue. While two people have told me they encountered this issue before 3.0, the number of Facebook posts about this exploded after the latest release.
It happened after a partial diff all load without saving and then close and reopen communications with configurator. Not even rebooting. When full loading full "diff all" and save things have always went smooth.
I've noticed something strange. Following the steps requested to try and reproduce the issue, I noticed that after selecting the preset, I can go and click in the CLI or any tab. If I don't click away, the board reboots. Could this cause issues or miss something if I click away before this reboot?
I ran some more tests today. This time with a F411WSE. I noticed a discrepancy in the reboot cycle after choosing these model defaults. Sometimes it reboots and other times it doesn't. Then after loading the diff all files and rebooting. It appears to complete the reboot for the model default. Which might explain why it clears the diff all settings.
As a side note. I have experienced the same issue with the OSD tab in 3.0. It used to do a disconnect and reconnect of the FC 7456 after loading the font prior to 3.0. This could be heard via the USB audio on the PC. And the configurator would close down the OSD page on reboot, then reload the page again. Now it disconnects after the font load, But the configurator doesn't always exit the OSD tab. If I try to change any of the font previews, it works for a bit then locks up until after a power cycle.
I am not sure if it's same issue. Matek F405 WSE - Inav3.0.
Wipe didn't happen since flashed and several power cycles.
But at todays maiden after a not that hard crash all my settings are gone, too. I thought it may happened because lipo and gps unit have been ripped off and ejected, but sounds a bit related to this.
Since I already set up everything again, I don't have a lot further details but will keep an eye on this.
Regards, Ingo
Suffering from this issue, these are the steps I take on a Matek 765. Connected over USB, not trying to load a diff, starting from a clean slate.
Flash board with Inav using the latest configurator. Connect up and it asks me to choose a pre-set (wing without tail), FC reboots. Connect up again and change ports for GPS and RC link. Hit the save and reboot button.
Sometimes the settings are saved, sometimes not. If the settings save, I got to the config tab to enable GPS. When I hit save, again sometimes it's saved, sometimes everything is reset to default (ports and other settings).
I "think" the mixer gets reset to default too as it asks me to configure it after a couple reboots (I'm not sure if that little popup the first time you connect is supposed to do it or not).
I've flashed it 2 or 3 times and the issues persist. Tried doing it with the battery plugged in and no difference.
It just happened to me again. I flew the plane this morning, all well setup, all good and great! Arrived at home, plug the USB to check/modify one thing and the board is clean again.... (F411-wse)
I tried on an F765 yesterday a lot. With presets applied, aborted by tab change, diff transferred and many other usual and unusual actions. Could not reproduce. Also tried a few times with an F411-WSE with no "luck".
Will do more tests. F411WSE seems to be the most prominent one.
just happened to me. Matek F411WSE.
the entire board was wiped. Did not even show up as a comport when plugged in to computer. I had to hold the boot button to get into DFU mode to reflash. Luckily, from knowing about this issue, i grabbed a diff yesterday.
last things i did: i was in cli and changed some launch parameters, i think i forgot to hit save.
continuous servo autotrim is enabled.
Now it hit me too.
Talon 250G. F411-WSE. No dump saved beforehand. It was flying fine last time. Today I wanted to connect it to the PC to get a diff for a friend and this screen welcomed me.
Have to check the 2 other F411WSE setups too.
Wondering if those new features that save to the auto eeprom are causing issues with this board
I don't think autolevel automatically saves to eeprom on disarm. Continuous servo trim does but iirc there was one report of this problem with that feature disabled. I could be wrong on that though.