Replies: 1 comment 1 reply
-
That can happen if you write INAV 7 or 8 over the top of INAV 6, but turn off the erase setting. That leaves a binary representation of the INAV 6 settings on the FC - which are not compatible with 7 or 8. The specific setting you are running into here can be corrected with: set inav_max_eph_epv = 1000 But it's suggested to follow the upgrade procedure listed on the download page and in the release notes. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi All,
getting "Waiting for GPS fix" error but as a matter of fact it seems there is a gps lock. There are plenty of satellites visible. In inav configurator the map is showing the precise place.
Please kindly help if someone faced this issue.
Thanks!
NAV/MATEKF411TE 7.1.2 May 31 2024 / 23:53:43 (4e1e59e)
GCC-10.3.1 20210824 (release)
System Uptime: 377 seconds
Current Time: 2025-03-11T17:07:28.952+00:00
Voltage: 11.59V (3S battery - OK)
CPU Clock=96MHz, GYRO=ICM42605, ACC=ICM42605, BARO=SPL06
STM32 system clocks:
SYSCLK = 96 MHz
HCLK = 96 MHz
PCLK1 = 48 MHz
PCLK2 = 96 MHz
Sensor status: GYRO=OK, ACC=OK, MAG=NONE, BARO=OK, RANGEFINDER=NONE, OPFLOW=NONE, GPS=OK
Stack size: 6144, Stack address: 0x20020000, Heap available: 1728
I2C Errors: 0, config size: 10031, max available config: 16384
ADC channel usage:
BATTERY : configured = ADC 1, used = ADC 1
RSSI : configured = ADC 3, used = none
CURRENT : configured = ADC 2, used = ADC 2
AIRSPEED : configured = ADC 4, used = none
System load: 20, cycle time: 1009, PID rate: 991, RX rate: 494, System rate: 9
Arming disabled flags: NAV CLI
OSD: MSP DisplayPort [53 x 20]
VTX: not detected
GPS: HW Version: UBLOX9 Proto: 32.00 Baud: 115200
GNSS Capabilities:
GNSS Provider active/default
GPS 1/1
Galileo 1/1
BeiDou 1/1
Glonass 1/1
Max concurrent: 4
Beta Was this translation helpful? Give feedback.
All reactions