CrazyFlie 2.0 - Propellers won't turn, won't turn on unless plugged in

Post here to get support
dronebus
Beginner
Posts: 5
Joined: Thu Jun 22, 2017 12:19 am

CrazyFlie 2.0 - Propellers won't turn, won't turn on unless plugged in

Post by dronebus » Thu Jun 22, 2017 12:24 am

Just received my CrazyFlie 2.0 today. I followed the assembly instructions, board passed self-test etc... However now that the drone is fully assembled I'm noticing a couple behaviors:
  • When plugged in to the USB, the blue LEDS are solid lit, and the red LED blinks twice per second, indicating all is good to go. However when applying throttle, the propellers move barely, or not at all.
  • When not plugged in, there are no lights or anything, power button is unresponsive.
  • If I repeatedly cycle both controls and press buttons when plugged in, I can effect some movement from the propellers, usually 1/2 to 2-3 turns.
Any idea what's going on?

UPDATE:

Pulled this log from the console, looks like there is an issue with the MPU6500:

Code: Select all

SYS: ----------------------------
SYS: Crazyflie 2.0 is up and running!
SYS: Build 0:df11f2550b81 (2017.05) CLEAN
SYS: I am 0x3131393135355115400030 and I have 1024KB of flash!
CFGBLK: v1, verification [OK]
MPU9250 I2C connection [OK].
AK8963 I2C connection [OK].
LPS25H I2C connection [OK].
DECK_DRIVERS: Found 9 drivers
DECK_INFO: Found 0 deck memory.
DECK_CORE: 0 deck enumerated
EEPROM: I2C connection [OK].
MPU6500: Self test gyro Y [FAIL]. low: -14.0, high: 14.0, measured: -29.75
MPU6500: Self test gyro X [FAIL]. low: -14.0, high: 14.0, measured: 32.13
MPU6500: Self test gyro X [FAIL]. low: -14.0, high: 14.0, measured: 33.49
MPU6500: Self test gyro Y [FAIL]. low: -14.0, high: 14.0, measured: 38.08
MPU6500: Self test gyro X [FAIL]. low: -14.0, high: 14.0, measured: -15.92
MPU6500: Self test gyro X [FAIL]. low: -14.0, high: 14.0, measured: 84.80
MPU6500: Self test gyro X [FAIL]. low: -14.0, high: 14.0, measured: 51.15
MPU6500: Self test acc X [FAIL]. low: -14.0, high: 14.0, measured: 34.29
AK8963: Self test [OK].
SYS: Free heap: 20048 bytes
UPDATE 2:
The MPU6500 failure is not consistently logged, I've not seen it repeat more than once on several restarts/reconnects.
Last edited by dronebus on Wed Jul 05, 2017 7:21 pm, edited 1 time in total.

tobias
Bitcraze
Posts: 1818
Joined: Mon Jan 28, 2013 7:17 pm
Location: Sweden

Re: CrazyFlie 2.0 - Propellers won't turn, won't turn on unless plugged in

Post by tobias » Thu Jun 22, 2017 7:47 am

Sounds like a battery problem. Have you let the battery charge for a longer period of time (1h)?

The MPU6500 issue is probably because you didn't leave it on a stable surface quick enough so the self test failed. It needs to be stable during the testing phase.

dronebus
Beginner
Posts: 5
Joined: Thu Jun 22, 2017 12:19 am

Re: CrazyFlie 2.0 - Propellers won't turn, won't turn on unless plugged in

Post by dronebus » Thu Jun 22, 2017 1:32 pm

tobias wrote:Sounds like a battery problem. Have you let the battery charge for a longer period of time (1h)?
The initial charging was probably 45-50 min. I'll try it for longer today. Assuming that doesn't work, what are the next steps?

UPDATE: I've had it charging for about 2 hours now. Absolutely no response from the power button if the drone is unplugged. Does not appear to be holding any kind of charge.

tobias
Bitcraze
Posts: 1818
Joined: Mon Jan 28, 2013 7:17 pm
Location: Sweden

Re: CrazyFlie 2.0 - Propellers won't turn, won't turn on unless plugged in

Post by tobias » Thu Jun 22, 2017 7:59 pm

Most likely a dead battery then. Do you have access to a multimeter you could check its voltage with just to be sure? If so send us an email to support@bitcraze.io and we will arrange a replacement battery.

tobias
Bitcraze
Posts: 1818
Joined: Mon Jan 28, 2013 7:17 pm
Location: Sweden

Re: CrazyFlie 2.0 - Propellers won't turn, won't turn on unless plugged in

Post by tobias » Thu Jun 22, 2017 7:59 pm

Most likely a dead battery then. Do you have access to a multimeter you could check its voltage with just to be sure? If so send us an email to support@bitcraze.io and we will arrange a replacement battery.

dronebus
Beginner
Posts: 5
Joined: Thu Jun 22, 2017 12:19 am

Re: CrazyFlie 2.0 - Propellers won't turn, won't turn on unless plugged in

Post by dronebus » Fri Jun 23, 2017 3:03 pm

tobias wrote:Do you have access to a multimeter you could check its voltage with just to be sure?
I checked the following:

When plugged in:
VUSB +/- = 5.12V
VCC/GND = ~3V

When not plugged in:
VUSB +/- = 0V
VCC/GND = 0V

It still does not power on when plugged in.

I'll go ahead and send an email to support.

arnaud
Bitcraze
Posts: 1887
Joined: Tue Feb 06, 2007 12:36 pm

Re: CrazyFlie 2.0 - Propellers won't turn, won't turn on unless plugged in

Post by arnaud » Tue Jun 27, 2017 7:48 am

Thank you for your email, we solved that there.

dronebus
Beginner
Posts: 5
Joined: Thu Jun 22, 2017 12:19 am

Re: CrazyFlie 2.0 - Propellers won't turn, won't turn on unless plugged in

Post by dronebus » Wed Jul 05, 2017 7:22 pm

I've received the new battery today, and charged it for over an hour. I'm still seeing the exact same behavior as in the original post. Will not turn on unless plugged in to USB.

tobias
Bitcraze
Posts: 1818
Joined: Mon Jan 28, 2013 7:17 pm
Location: Sweden

Re: CrazyFlie 2.0 - Propellers won't turn, won't turn on unless plugged in

Post by tobias » Fri Jul 07, 2017 8:00 am

Bummer, to bad we didn't know that before so we could have sent out a replacement CF2 board at the same time. Then the issue lies within the power management chip, or the wires. Just to be sure can you check that you have voltage at the soldering pads of the battery cable?

dronebus
Beginner
Posts: 5
Joined: Thu Jun 22, 2017 12:19 am

Re: CrazyFlie 2.0 - Propellers won't turn, won't turn on unless plugged in

Post by dronebus » Mon Jul 17, 2017 9:00 pm

So I think I've identified a potential problem. It appears that the battery connector has been soldered to the board with the polarity reversed.

I could at least attempt to de/re-solder the connection appropriately if you think that is potentially the root cause. Otherwise some kind of RMA or replacement might be appropriate.

Post Reply