All calibrations carried out successfully but GPS keeps from arming. A short dump provided. Any numbers or settings need to be changed or something else

Thanks

et_gps =
### ERROR: Invalid name

# get_gps
gps_provider = UBLOX7
Allowed values: NMEA, UBLOX, UNUSED, NAZA, UBLOX7, MTK, MSP

gps_sbas_mode = AUTO
Allowed values: AUTO, EGNOS, WAAS, MSAS, GAGAN, NONE

gps_dyn_model = AIR_1G
Allowed values: PEDESTRIAN, AIR_1G, AIR_4G

gps_auto_config = ON
Allowed values: OFF, ON

gps_auto_baud = ON
Allowed values: OFF, ON

gps_ublox_use_galileo = ON
Allowed values: OFF, ON

gps_min_sats = 6
Allowed range: 5 - 10

inav_use_gps_velned = ON
Allowed values: OFF, ON

inav_use_gps_no_baro = OFF
Allowed values: OFF, ON

inav_w_z_gps_p =  0.200
Allowed range: 0 - 10

inav_w_z_gps_v =  0.100
Allowed range: 0 - 10

inav_w_xy_gps_p =  1.000
Allowed range: 0 - 10

inav_w_xy_gps_v =  2.000
Allowed range: 0 - 10


#

sorry forgot to mention hardware
Matek m8n 5883
FC Matek 722 SE

Your current settings require 6 satellites to be able to arm.

In Betaflight we can set the following to arm without a GPS fix but this will probably not be available in iNav:

set gps_rescue_allow_arming_without_fix = ON

In Inav it's
set nav_extra_arming_safety = off
save

(02-Jan-2022, 08:50 PM)Major Tom Wrote: In Inav it's
set nav_extra_arming_safety = off
save

(02-Jan-2022, 08:50 PM)Major Tom Wrote: In Inav it's
set nav_extra_arming_safety = off
save

Turning "extra arming safety" command off, no change. Replaced 5883 with new one. Compass calibrated and working as expected but GPS not connecting. I now get error "gyro_hardware_LPF". Is this something to do with a low pass filter? Could inav 4 be contributing to this issue. I have another drone with similar parts but using open Tx, without problems. I like to get this problem solved, I have no clue as what to do next

Try Betaflight for a test to ensure its not really a hardware/configuration issue.

Also try iNav 3.0x to test.

Is GPS icon in Inav Configurator blue or red?

(06-Jan-2022, 07:55 AM)kafie1980 Wrote: Try Betaflight for a test to ensure its not really a hardware/configuration issue.

Also try iNav 3.0x to test.

GPS and RTH Red. I will try 3.0 next