BigQuad deck resetting the crazyflie
Posted: Sun Sep 03, 2017 6:48 am
Hi,
I have purchased a few BigQuad decks for my crazyflies, but they aren't working for me. I can usually get the motors to spin for a few seconds and then the crazyflie just reboots.
1) I am successfully compiling the driver (I hard coded the flag)
2) I tested the esc+motors using one of these guys (https://www.amazon.com/gp/product/B00LT ... UTF8&psc=1) and they spin properly
3) This is the esc I am using (https://www.amazon.com/gp/product/B01I8 ... UTF8&psc=1)
4) I have tried different timing settings with mixed results but I am not sure what would work anyway (https://github.com/bitcraze/crazyflie-f ... tors.h#L91)
5) I have added capacitors to the motor connector and the power line between the esc and the BigQuad board to try and filter the signals
6) I have sometimes successfully gotten the motors to spin up by setting that parameter that manually sets the PWM (20000 for example)
If anyone in the community or the dev team (Marcus?) has experienced something similar, or if anyone has ideas, I'd love to chat! Right now I suspect either a timing issue or current spike / parasitic capacitance somewhere on the board.
Thanks!
I have purchased a few BigQuad decks for my crazyflies, but they aren't working for me. I can usually get the motors to spin for a few seconds and then the crazyflie just reboots.
1) I am successfully compiling the driver (I hard coded the flag)
2) I tested the esc+motors using one of these guys (https://www.amazon.com/gp/product/B00LT ... UTF8&psc=1) and they spin properly
3) This is the esc I am using (https://www.amazon.com/gp/product/B01I8 ... UTF8&psc=1)
4) I have tried different timing settings with mixed results but I am not sure what would work anyway (https://github.com/bitcraze/crazyflie-f ... tors.h#L91)
5) I have added capacitors to the motor connector and the power line between the esc and the BigQuad board to try and filter the signals
6) I have sometimes successfully gotten the motors to spin up by setting that parameter that manually sets the PWM (20000 for example)
If anyone in the community or the dev team (Marcus?) has experienced something similar, or if anyone has ideas, I'd love to chat! Right now I suspect either a timing issue or current spike / parasitic capacitance somewhere on the board.
Thanks!