iNav 6.0 - Cannot disengage Manual Flight Mode

[AdamGFPV]

Description: When setting up flight modes, if there is a range added for Manual mode, there is no way to disengage manual mode, which means Acro is not accessible. When the value for the channel falls outside of the specified range to activate manual, manual mode remains active no matter what. (Please see attached screen shot).

Note: If i setup an identical model in 5.1 and 6.0, the issue does not occur in 5.1, but it does occur in 6.0.

Note 2: This issue does not occur on all of my flight controllers on iNav 6.0.

Hardware: Matek H743 WLITE

Steps to replicate: 1: Set FC in DFU and flash inav 6.0 with full chip erase 2: Connect and select plane without a tail (wing/delta) 3: On serial tab, set 'Serial Receiver Provider' to 'CRSF'. Save and reboot. 4: Go to modes tab, can see Acro is enabled as no flight modes have a range added. Add manual mode and set small range e.g. min: 1125 - Max 1300. Hit Save. (now have to reboot FC as it stops responding to receiver). 5: Go to Modes tab, Manual flight mode will be enabled no matter what value the channel is on, even when outside of the specified range for manual. Therefore it's impossible to activate Acro mode.

Again, I have done the above steps exactly as described on the same FC with both iNav 5.1 and iNav 6.0 and the problem only occurs on 6.0.

Please let me know if any further info is required or if a video screen recording would help.

Thanks Adam

[DzikuVx]

Duplicate of https://github.com/iNavFlight/inav/issues/8905 Closing

[AdamGFPV]

This issue is definitely not a duplicate of #8905 I briefly mentioned a side issue in brackets on step 4 which describes #8905

Please read again and re-open. Crossfire is responding fine after reboot and I cannot access Acro due to Manual mode remaining on at all times.

[AdamGFPV]

Just to add to this issue, I can confirm that if I switch my Serial receiver provider to SBUS and use a Dragonlink receiver instead, BOTH the issue in this thread AND separate issue #8905 are still present.

[DzikuVx]

Now, the question is what happens if you restart Configurator?

[AdamGFPV]

If I restart Configurator same problem. If I re-flash 6.0 with full chip erase and start again, same problem. Also tried on 2 different computers.

If I flash 5.1 on the same FC, problem is gone. Flash back to inav 6 and issue is back again.

[breadoven]

I assume sensors have finished calibrating ? Manual remains active if disarmed and sensors are still calibrating.

[DzikuVx]

@AdamGFPV please perform this scenario:

1. Reproduce
2. Shutdown Configurator without rebooting FC
3. Start Configurator
4. Connect
5. Check the state

[AdamGFPV]

I assume sensors have finished calibrating ? Manual remains active if disarmed and sensors are still calibrating.

I believe they only calibrate when powered by a battery? This is a new FC I have not soldered a power connector on yet. It is just powered by USB.

[AdamGFPV]

@AdamGFPV please perform this scenario:

1. Reproduce
2. Shutdown Configurator without rebooting FC
3. Start Configurator
4. Connect
5. Check the state

I've just tried this again to be double sure. The issue is still present.

Would it help if i made a video screen recording?

[breadoven]

I assume sensors have finished calibrating ? Manual remains active if disarmed and sensors are still calibrating.

I believe they only calibrate when powered by a battery? This is a new FC I have not soldered a power connector on yet. It is just powered by USB.

Shouldn't need a battery as far as I'm aware, on board sensors are powered by USB. The Gyro, Acc and Baro are showing as blue in the above screenshot so doesn't look like this is the issue. However, easy to check though since calibration would result in in ARM blocker. Check Status in the CLI.

[AdamGFPV]

Shouldn't need a battery as far as I'm aware, on board sensors are powered by USB. The Gyro, Acc and Baro are showing as blue in the above screenshot so doesn't look like this is the issue. However, easy to check though since calibration would result in in ARM blocker. Check Status in the CLI.

Entering CLI Mode, type 'exit' to return, or 'help'

status

INAV/MATEKH743 6.0.0 Mar 22 2023 / 10:48:04 (084101ac) GCC-10.2.1 20201103 (release) System Uptime: 47 seconds Current Time: 2041-06-28T01:04:00.000+00:00 Voltage: 0.00V (1S battery - NOT PRESENT) CPU Clock=480MHz, GYRO=ICM42605, ACC=ICM42605, BARO=SPL06 STM32 system clocks: SYSCLK = 480 MHz HCLK = 240 MHz PCLK1 = 120 MHz PCLK2 = 120 MHz Sensor status: GYRO=OK, ACC=OK, MAG=NONE, BARO=OK, RANGEFINDER=NONE, OPFLOW=NONE, GPS=NONE SD card: Startup failed Stack size: 6144, Stack address: 0x20020000, Heap available: 1716 I2C Errors: 50, config size: 9067, max available config: 131072 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: 1, cycle time: 1001, PID rate: 999, RX rate: 111, System rate: 10 Arming disabled flags: CAL ACC CLI OSD: MAX7456 [30 x 16] VTX: not detected

[breadoven]

Looks like the ACC is not calibrated: https://github.com/iNavFlight/inav/wiki/%22Something%22-is-disabled----Reasons

Which is strange because the status also says the ACC is OK ?

[AdamGFPV]

Ok so after a ACC calibration the issue is no longer present.

The strange thing is that this is not the case on iNav 5.1. ACC Cal is not needed

I am also sure that when I first found this issue, I had already calibrated the ACC when it occurred.

Thanks

[preisedj]

I have a similar thing happening with the same FC and INAV 6.0. The system stays in Manual mode even after selecting any other Flight Mode. In the Modes tab, the other flight modes light up as I step through them, but the Manual mode continues to be lit and overrides any other mode selection throughout. But once the GPS locks in, this condition clears and everything performs as it should.