Gyro Calibration/Initialization on BETAFPVF411 1s AIO | Betaflight | Page 1

gusty smelt May 1, 2024, 2:02 PM

#

I recently replaced two BETAFPVF411 1s AIO’s both are of the same 2.1 revision. However, I have encountered an issue with the gyro calibration/initialization process.

Upon setting up and testing the flight controllers, I found that the FCs fail to calibrate properly during the initialization process after plugging in the USB cable. (Setting the gyro_calib_noise_limit has no effect) The arming flag within the configurator is stuck at 'calibrating', the model does not move on the setup tab and the sensors tab also shows no movement.

I have attempted various troubleshooting steps and the only way in which I can get both FCs to work correctly is to set both dshot_bitbang to ON and acc_calibration to a value I found in the dump file on the betafpv website within the CLI. By doing this the configurator will then report the gyro correctly.

I found that the two FCs also behave differently when it comes to the dshot_bitbang setting. One unit works correctly with this setting turned OFF, while the other unit only functions properly when dshot_bitbang is set to ON. This behaviour is surprising since both units are supposed to be identical (2.1 revision).

The issue persists across 4.4 and 4.5 betaflight stable releases.

Should I log an issue on Github for this or is there a reason for this strange behaviour?

ripe mural May 1, 2024, 2:12 PM

#

Can you post the output of status in the BF CLI?

gusty smelt May 1, 2024, 2:16 PM

#

Sure, would you like it with dshot_bitbang to ON and acc_calibration set via the CLI i.e working or without these set i.e not working?

ripe mural May 1, 2024, 2:16 PM

#

Doesn't matter

gusty smelt May 1, 2024, 2:17 PM

#

I send it once I return home from work in a hour or so.

stone shadow May 1, 2024, 2:40 PM

#

gusty smelt I recently replaced two BETAFPVF411 1s AIO’s both are of the same 2.1 revision. ...

I had this issue on my BetaFPV FC too. I've asked BetaFPV: the answer was: this is BF issue.

ruby leaf May 1, 2024, 2:44 PM

#

There is an open issue. Different behaviour on 2 different v2.1's is a new one though https://github.com/betaflight/betaflight/issues/13102
Hard to resolve, as with DMA would be preferred if it works, as gyro looses its DMA channel with bitbang. So no reason to change behaviour for old hardware

#

Just to fix whatever BetaFPV or the manafacturer decided to change in this batch harold

gusty smelt May 1, 2024, 3:14 PM

#

Here is the status output for what its worth
# status MCU F411 Clock=108MHz (PLLP-HSE), Vref=3.31V, Core temp=30degC Stack size: 2048, Stack address: 0x2001fff0 Configuration: CONFIGURED, size: 3610, max available: 16384 Devices detected: SPI:1, I2C:0 Gyros detected: gyro 1 locked GYRO=BMI270, ACC=BMI270 OSD: MAX7456 (30 x 13) BUILD KEY: d7f9780ab694e930e203d1268f2d6928 (4.5.0) System Uptime: 67 seconds, Current Time: 2024-05-01T15:12:47.322+00:00 CPU:42%, cycle time: 312, GYRO rate: 3205, RX rate: 15, System rate: 9 Voltage: 74 * 0.01V (0S battery - INIT) I2C Errors: 0 FLASH: JEDEC ID=0x00ef4017 8M Arming disable flags: RXLOSS ANGLE CLI MSP DSHOT_TELEM

#Gyro Calibration/Initialization on BETAFPVF411 1s AIO