iNavFlight
8.0 RC2 Hanging on "waiting for data" page
Speedybee F405 Mini, INAV 8.0
90% of the times I click reboot and save after adjusting something, in any tab, it will just hang on the "waiting for data" page and I have to unplug/replug the USB.
Same here, usually clicking the Disconnect/Connect button a few times solves the issue. Does not happen with the 7.1.2 Configurator. Matek F405-STD
For me it pretty much happens always after a new flash (full chip erase) and selecting "Airplane without a tail" from the "Default values" selection box. After the FC does it's reboot it shows the above screen and hangs. When just changing a single setting and clicking the "Save and Reboot" button it usually works fine.
It's been hanging up for me since 6.0 on full chip erase/resets but only when I initially do the reset/erase...on 8.0 it's hanging after almost every "save and reboot" I do regardless of how much I had changed. I also tried it today on a Matek 405WMN and it does the same.
Try clicking the "Flush settings cache" button in the main application settings box, Also restart Configurator after flashing and flushing the settings cache.
Try clicking the "Flush settings cache" button in the main application settings box, Also restart Configurator after flashing and flushing the settings cache.
This could work as a temporary work-around. As with the v7 Configurator, this should not be needed to do.
I can confirm that this issue still occasionally appears, in my case only through slow wireless connections like Bluetooth or mLRS Data Links. A quick disconnect and reconnect solves it but not reliably repeatable.
exact same issue Speedybee F405 Mini, INAV 8.0, FC FIRMWARE7.1.2 [SPEEDYBEEF405WING]
on mac
it will just hang on the "waiting for data" page when I try to go to Mixer tab and I have to disconnect and reconnect EVERY time to make it responsive again (until I click Mixer tab again and it hangs).
The Flush settings cache did not make any difference....
Any more ideas?
Can anyone who has this issue at a high rate and only on wings, please go into CLI and type:
set looptime = 1000
then save. Please check if that reduces the rate of this bug. Quads should stay at looptime 500 though.
I "solved" the problem after seeing inav 8-0 only wants 8-0 firmwares for the FC, and as I wrote in previous post: INAV 8.0, FC FIRMWARE7.1.2....
All works when using INAV 7.x
@b14ckyy do you want me to test the loop time fix for the INAV 8.0, FC FIRMWARE7.1.2 combo or is that then irrelevant?
