Hey all, I'm pretty new to the Crazyflie(2.1) platform so perhaps this is just user error... but I've hit a bit of a conundrum and tried everything I could think to do with the python client, logging the results over crazy radio (all zeroes from the stabilizer) and leaving them on the stablest surface I could find until they could calibrate. No matter what I do, the problem drones always report the following output to console in the python client.
SYS: ----------------------------
SYS: Crazyflie 2.1 is up and running!
SYS: Production release 2020.06
SYS: I am 0x20383347344D5008002D0057 and I have 1024KB of flash!
CFGBLK: v1, verification [OK]
DECK_CORE: 0 deck(s) found
IMU: BMI088 Gyro I2C connection [OK].
IMU: BMI088 Accel I2C connection [OK]
IMU: BMP388 I2C connection [OK]
ESTIMATOR: Using Complementary (1) estimator
CONTROLLER: Using PID (1) controller
MTR-DRV: Using brushed motor driver
EEPROM: I2C connection [OK].
IMU: BMI088 gyro self-test [OK]
STAB: Wait for sensor calibration...
SYS: Free heap: 13216 bytes
With it just ending there and never completing the process as it normally would (and does) for the other drones I acquired, which I was able to compare it to.
SYS: ----------------------------
SYS: Crazyflie 2.1 is up and running!
SYS: Production release 2020.06
SYS: I am 0x20383347344D50070039004A and I have 1024KB of flash!
CFGBLK: v1, verification [OK]
DECK_CORE: 0 deck(s) found
IMU: BMI088 Gyro I2C connection [OK].
IMU: BMI088 Accel I2C connection [OK]
IMU: BMP388 I2C connection [OK]
ESTIMATOR: Using Complementary (1) estimator
CONTROLLER: Using PID (1) controller
MTR-DRV: Using brushed motor driver
EEPROM: I2C connection [OK].
IMU: BMI088 gyro self-test [OK]
STAB: Wait for sensor calibration...
SYS: Free heap: 13216 bytes
STAB: Ready to fly.
I speculated that it might be a some sort of hardware error, but thinking back it seems to have occurred the same way to two of my drones (which I then learned not to try on the others): I changed the radio channel from the default 80 to some other one following the upload of the newest firmware(
https://github.com/bitcraze/crazyflie-r ... 020.06.zip) via the boot loader, which immediately caused them to go from sending telemetry data while connected to none at all. Switching back to the default channel unfortunately did not restore telemetry data, which prompted me to start trying to figure out why and then clued me into the stabilizer not calibrating. I'm not really certain what I could have done to bust the stabilizer otherwise, or how to return them to their original out of the box state (tried the python EEPROM script, no luck) so any advice you all could provide on what might have gone wrong or what I might be overlooking in the crazyflie that's accessible by Python would be super appreciated.