Closed userod closed 4 years ago
issue-label-bot[bot]
commented
4 years ago Issue-Label Bot is automatically applying the label BUG to this issue, with a confidence of 0.64. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!
Links: app homepage, dashboard and code for this bot.
digitalentity
commented
4 years ago You should flash will full erase
peteoz
commented
3 years ago it's the same iNav bug that's causing "invalid settings" error, I don't think it's related to flash without full erase only, as I always do flash with full erase and still observed same issue. my observation is this happens when CPU runs out of resources. some settings get corrupted and certain values are set to non-default values, in my case gyro_hardware_lpf, heading_hold_rate_limit and acc_lpf_hz got set to "101" and in case of gyro_hardware_lpf that's obviously invalid settings. it happened after I changed FC loop time from default 1kHz to 2kHz and after reboot iNav configurator became mostly unresponsive, I was still able to enter CLI and change the loop time back to default but the other settings were already corrupted. btw. I'm on iNav 3.01 but same thing happened to friend of mine who is running iNav 2.6.1
joe8012
commented
2 years ago This showed up with Inav 4.0. acc_lpf_hz = 102
MrD-RC
commented
2 years ago It’s basically the same issue as this https://github.com/iNavFlight/inav/issues/7281
This will show you how to fix it https://inavfixedwinggroup.com/rc-news/inav-random-config-change-bug/
joe8012
commented
2 years ago Thanks Darren. I had three of the four parameters wrong. No wonder I had such a hard time tuning my wing.
Hi all, not so much an issue per say but it seems like my 'acc_lpf_hz' set itself to 102 during set up after installing 2.5.0 FC firmware. How does this happen? (I hadn't flown the FC yet). seems like the default is down around 20..?