WING FC boards won't ARM

[mickey2011]

Board: WING FC/FF35 version 0 Configurator: INAV 7.0.1 INAV 7.0.0 and the later versions 6

Trying to set up as a simple 'Wing FC' for a small 'Z84 Wing' i.e. 1 motor, 2 servo's, GPS, No FPV.

Issue is that they will not ARM, configurator 'setup' reports the NAVIGATION is not safe.

CLI ARMING Status reports "CLI NAV"

Many, many experiments show that if ANY 'NAV type MODEs are 'configured' (only configured, not activated) in the MODE setup/CLI then they won't ARM

Removing ALL NAVE MODES , sometimes allows ARMing but normally startover with a new/fresh INAV install and it will ARM, so long as NO 'NAV modes are configured.

Features.... GPS, No OSD, FrSky SBUS RX, Telemetry using SOFTSERIAL, Magnometer deactivated.

I have 3 of these boards with the same issue, the identical setup in MAtek WMN and SpeedyBee Wing boards works fine.

[b14ckyy]

If nav modes are configured or rth, you need a valid GPS fix to arm. This is normal because otherwise you have no home position.

[mickey2011]

Yes I am aware of this, this issue exists with a valid GPS fix, I can normally get 8 plus Sats

On Mon, 25 Mar 2024 at 21:00, b14ckyy @.***> wrote:

If nav modes are configured or rth, you need a valid GPS fix to arm. This is normal because otherwise you have no home position.

— Reply to this email directly, view it on GitHub https://github.com/iNavFlight/inav/issues/9853#issuecomment-2017418216, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJWTIXVZWCFOQ73K5C3RDGTYZ7KS3AVCNFSM6AAAAABFGCYPJKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJXGQYTQMRRGY . You are receiving this because you authored the thread.Message ID: @.***>

[b14ckyy]

Can you attach a txt with your diff please. Do the other working setups use the same GPS module? What GPS module exactly is in each setup?

Beside the configurable minimum satellite number limit, there is also a hardcoded maximum HDOP limit I think. Interferences, electrical noise or reflections (from carbon parts) can cause a high HDOP despite having enough satellites. I think, but I am not sure about that, the max HDOP is 5.5. You can check that in the GPS tab.

[mickey2011]

Yes I will tomorrow. My GPS’s are all Beitain BN220 or 880, I have tried both types and as I mentioned, my setups work just fine on both Matek and Speedybee boards. I have three WING FC boards and would like to use them on Simple aircraft like Wings.

Thanks for your help

On Mon, 25 Mar 2024 at 21:38, b14ckyy @.***> wrote:

Can you attach a txt with your diff please. Do the other working setups use the same GPS module? What GPS module exactly is in each setup?

Beside the configurable minimum satellite number limit, there is also a hardcoded maximum HDOP limit I think. Interferences, electrical noise or reflections (from carbon parts) can cause a high HDOP despite having enough satellites. I think, but I am not sure about that, the max HDOP is 5.5. You can check that in the GPS tab.

— Reply to this email directly, view it on GitHub https://github.com/iNavFlight/inav/issues/9853#issuecomment-2017473541, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJWTIXVHNQG4EUPIN6XDP2TYZ7PBZAVCNFSM6AAAAABFGCYPJKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJXGQ3TGNJUGE . You are receiving this because you authored the thread.Message ID: @.***>

[breadoven]

Can you arm using arming bypass, i.e. Yaw stick right, when the Nav modes are configured ? (Setting nav_extra_arming_safety)

[mickey2011]

ah, I don't think this is a feature in INAV 7.0.0 ???

On Mon, 25 Mar 2024 at 23:30, breadoven @.***> wrote:

Can you arm using arming bypass, i.e. Yaw stick right, when the Nav modes are configured ? (Setting nav_extra_arming_safety)

— Reply to this email directly, view it on GitHub https://github.com/iNavFlight/inav/issues/9853#issuecomment-2017682530, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJWTIXQG7ECTCOWGSUAWHXTYZ74F7AVCNFSM6AAAAABFGCYPJKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJXGY4DENJTGA . You are receiving this because you authored the thread.Message ID: @.***>

[mickey2011]

Hello WINGFC INAV 7.0.0 'Diff All" and ARM status.txt files attached

Thanks Cheers

On Mon, 25 Mar 2024 at 21:38, b14ckyy @.***> wrote:

Can you attach a txt with your diff please. Do the other working setups use the same GPS module? What GPS module exactly is in each setup?

Beside the configurable minimum satellite number limit, there is also a hardcoded maximum HDOP limit I think. Interferences, electrical noise or reflections (from carbon parts) can cause a high HDOP despite having enough satellites. I think, but I am not sure about that, the max HDOP is 5.5. You can check that in the GPS tab.

— Reply to this email directly, view it on GitHub https://github.com/iNavFlight/inav/issues/9853#issuecomment-2017473541, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJWTIXVHNQG4EUPIN6XDP2TYZ7PBZAVCNFSM6AAAAABFGCYPJKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJXGQ3TGNJUGE . You are receiving this because you authored the thread.Message ID: @.***>

status

INAV/WINGFC 7.0.0 Dec 5 2023 / 09:43:11 (895a4f31) GCC-10.3.1 20210824 (release) System Uptime: 97 seconds Current Time: 2041-06-28T13:04:00.000+12:00 Voltage: 11.07V (3S battery - OK) CPU Clock=168MHz, GYRO=MPU9250, ACC=MPU9250, BARO=BMP280 STM32 system clocks: SYSCLK = 168 MHz HCLK = 168 MHz PCLK1 = 42 MHz PCLK2 = 84 MHz Sensor status: GYRO=OK, ACC=OK, MAG=NONE, BARO=OK, RANGEFINDER=NONE, OPFLOW=NONE, GPS=OK Stack size: 6144, Stack address: 0x10010000, Heap available: 1728 I2C Errors: 0, config size: 9220, max available config: 131072 ADC channel usage: BATTERY : configured = ADC 3, used = ADC 3 RSSI : configured = none, used = none CURRENT : configured = ADC 2, used = ADC 2 AIRSPEED : configured = ADC 1, used = none System load: 5, cycle time: 1017, PID rate: 983, RX rate: 113, System rate: 9 Arming disabled flags: NAV CLI OSD: not enabled VTX: not detected GPS: HW Version: UBLOX8 Proto: 18.00 Baud: 19200 GNSS Capabilities: GNSS Provider active/default GPS 1/1 Galileo 0/0 BeiDou 0/0 Glonass 0/1 Max concurrent: 3 diff all

version

INAV/WINGFC 7.0.0 Dec 5 2023 / 09:43:11 (895a4f31)

GCC-10.3.1 20210824 (release)

start the command batch

batch start

reset configuration to default settings

defaults noreboot

resources

Timer overrides

Outputs [servo]

servo 1 1000 2000 1500 -100

safehome

features

feature -OSD feature MOTOR_STOP feature SOFTSERIAL feature BLACKBOX feature PWM_OUTPUT_ENABLE

beeper

blackbox

blackbox NAV_ACC blackbox NAV_POS blackbox NAV_PID blackbox -MAG blackbox ACC blackbox ATTI blackbox RC_DATA blackbox RC_COMMAND blackbox MOTORS blackbox -GYRO_RAW blackbox -PEAKS_R blackbox -PEAKS_P blackbox -PEAKS_Y

Receiver: Channel map

Ports

serial 0 0 57600 115200 0 115200 serial 1 0 115200 115200 0 115200 serial 2 64 115200 115200 0 115200 serial 3 0 115200 115200 0 115200 serial 4 2 115200 19200 0 115200 serial 5 0 115200 115200 0 115200 serial 30 32 115200 115200 0 115200

Modes [aux]

aux 0 0 4 1875 2100 aux 1 1 5 1875 2100 aux 2 12 5 900 1075 aux 3 11 8 1425 1600 aux 4 10 6 1400 1600 aux 5 28 8 1900 2100 aux 6 3 7 1850 2100 aux 7 21 9 1550 1700 aux 8 37 9 1300 1475 aux 9 36 10 1875 2100 aux 10 27 6 1850 2100

Adjustments [adjrange]

Receiver rxrange

temp_sensor

Mission Control Waypoints [wp]

wp 0 invalid

OSD [osd_layout]

osd_layout 0 0 23 0 H osd_layout 0 1 12 0 H osd_layout 0 7 13 12 H osd_layout 0 9 1 2 H osd_layout 0 11 2 3 H osd_layout 0 12 1 4 H osd_layout 0 14 0 11 H osd_layout 0 15 1 0 H osd_layout 0 28 23 11 H osd_layout 0 30 1 13 H

Programming: logic

Programming: global variables

Programming: PID controllers

master

set gyro_main_lpf_hz = 25 set dynamic_gyro_notch_q = 250 set dynamic_gyro_notch_min_hz = 30 set gyro_zero_x = -16 set gyro_zero_y = -2 set gyro_zero_z = 16 set ins_gravity_cmss = 978.388 set acc_hardware = MPU9250 set acczero_x = 4 set acczero_y = 52 set acczero_z = 66 set accgain_x = 4093 set accgain_y = 4093 set accgain_z = 4076 set mag_hardware = NONE set baro_hardware = BMP280 set serialrx_provider = SBUS set motor_pwm_protocol = STANDARD set failsafe_procedure = RTH set align_board_yaw = 1800 set small_angle = 180 set applied_defaults = 3 set airmode_type = STICK_CENTER_ONCE set nav_wp_radius = 3000 set nav_wp_max_safe_distance = 500 set nav_fw_wp_tracking_accuracy = 6 set nav_fw_wp_turn_smoothing = ON set nav_overrides_motor_stop = AUTO_ONLY set nav_rth_climb_first = OFF set nav_rth_allow_landing = NEVER set nav_rth_alt_control_override = ON set nav_max_altitude = 9500 set nav_rth_altitude = 5000 set nav_rth_home_altitude = 3500 set safehome_usage_mode = OFF set nav_fw_loiter_radius = 4500 set nav_fw_control_smoothness = 2 set nav_fw_launch_max_angle = 60 set nav_fw_launch_motor_delay = 75 set nav_fw_launch_min_time = 500 set nav_fw_launch_max_altitude = 7000 set nav_fw_launch_climb_angle = 30 set nav_fw_allow_manual_thr_increase = ON set osd_home_position_arm_screen = OFF set osd_switch_indicators_align_left = OFF set tz_offset = 720

mixer_profile

mixer_profile 1

set model_preview_type = 8 set motorstop_on_low = ON set mixer_pid_profile_linking = ON

Mixer: motor mixer

mmix reset

mmix 0 1.000 0.000 0.000 0.000

Mixer: servo mixer

smix reset

smix 0 1 0 50 0 -1 smix 1 1 1 50 0 -1 smix 2 2 0 -50 0 -1 smix 3 2 1 50 0 -1

mixer_profile

mixer_profile 2

Mixer: motor mixer

Mixer: servo mixer

profile

profile 1

set fw_p_pitch = 4 set fw_i_pitch = 5 set fw_d_pitch = 5 set fw_ff_pitch = 80 set fw_p_roll = 4 set fw_i_roll = 3 set fw_d_roll = 7 set fw_p_yaw = 50 set fw_i_yaw = 0 set fw_d_yaw = 20 set fw_ff_yaw = 255 set max_angle_inclination_rll = 600 set max_angle_inclination_pit = 600 set dterm_lpf_hz = 10 set fw_turn_assist_pitch_gain = 0.400 set nav_fw_pos_z_p = 25 set nav_fw_pos_z_d = 8 set nav_fw_pos_xy_p = 55 set d_boost_min = 1.000 set d_boost_max = 1.000 set fw_level_pitch_trim = -5.000 set rc_expo = 30 set rc_yaw_expo = 30 set roll_rate = 18 set pitch_rate = 9 set yaw_rate = 3

profile

profile 2

set fw_p_pitch = 15 set fw_i_pitch = 5 set fw_d_pitch = 5 set fw_ff_pitch = 80 set fw_p_roll = 15 set fw_i_roll = 3 set fw_d_roll = 7 set fw_p_yaw = 50 set fw_i_yaw = 0 set fw_d_yaw = 20 set fw_ff_yaw = 255 set max_angle_inclination_rll = 450 set dterm_lpf_hz = 10 set fw_turn_assist_pitch_gain = 0.400 set nav_fw_pos_z_p = 25 set nav_fw_pos_z_d = 8 set nav_fw_pos_xy_p = 55 set d_boost_min = 1.000 set d_boost_max = 1.000 set rc_expo = 30 set rc_yaw_expo = 30 set roll_rate = 18 set pitch_rate = 9 set yaw_rate = 3

profile

profile 3

set fw_p_pitch = 15 set fw_i_pitch = 5 set fw_d_pitch = 5 set fw_ff_pitch = 80 set fw_p_roll = 15 set fw_i_roll = 3 set fw_d_roll = 7 set fw_p_yaw = 50 set fw_i_yaw = 0 set fw_d_yaw = 20 set fw_ff_yaw = 255 set max_angle_inclination_rll = 450 set dterm_lpf_hz = 10 set fw_turn_assist_pitch_gain = 0.400 set nav_fw_pos_z_p = 25 set nav_fw_pos_z_d = 8 set nav_fw_pos_xy_p = 55 set d_boost_min = 1.000 set d_boost_max = 1.000 set rc_expo = 30 set rc_yaw_expo = 30 set roll_rate = 18 set pitch_rate = 9 set yaw_rate = 3

battery_profile

battery_profile 1

set battery_capacity = 1300 set throttle_idle = 5.000 set nav_fw_min_thr = 1150 set nav_fw_launch_thr = 1300 set nav_fw_launch_idle_thr = 1150

battery_profile

battery_profile 2

set throttle_idle = 5.000

battery_profile

battery_profile 3

set throttle_idle = 5.000

restore original profile selection

mixer_profile 1 profile 1 battery_profile 1

save configuration

save

[sensei-hacker]

You may want to try turning off the virtual airspeed sensor.

It's saying navigation is unsafe, which indicates a sensor problem or a waypoint mission loaded, but I don't see a waypoint mission or problems reported with the physical sensors.

[mickey2011]

Thanks for that, I went looking to turn it off, but couldn’t find how to do it.

Can you advise.

Thanks

On Tue, 26 Mar 2024 at 17:14, Sensei @.***> wrote:

You may want to try turning off the virtual airspeed sensor.

It's saying navigation is unsafe, which indicates a sensor problem or a waypoint mission loaded, but I don't see a waypoint mission or problems reported with the physical sensors.

— Reply to this email directly, view it on GitHub https://github.com/iNavFlight/inav/issues/9853#issuecomment-2019350599, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJWTIXTWZURV6SH6F533MWDY2DY3PAVCNFSM6AAAAABFGCYPJKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJZGM2TANJZHE . You are receiving this because you authored the thread.Message ID: @.***>

[sensei-hacker]

On the Configuration tab.

In 7.0, the virtual pitot was turned on by default. That will be turned off again in 7.1.

[mickey2011]

Issue APPEARS resolved, in 7.1RC.

Thanks for all your help

[b14ckyy]

If you still have issues, just reply here.