Bitcraze Forums

Big thanks for doing this extensive testing! The sd-logging is a bit challenging as it is resource limited and when getting close to the limit strange things start to happen. Best would be if it didn't but we are not there yet. By resources I mean mainly CPU time and SPI bus time. As both UWB and fl...

Let us know how it goes!

Female Battery Connector: 51005-0200 at molex.com
Male Battery Connector: 51006-0200 at molex.com

I'm not sure most batteries specify it so I would go by the looks. Also check that the polarity is the same, which if not, can be switched afterwards.

Sorry but we don't have that data and I have not heard of anyone else doing that type of measurement either. I guess the only way to measure it is in a wind tunnel...? It would be really good data to have though!

Without trying this I think the problem is the send_emergency_stop_watchdog which needs to be sent at least every second. If you try with a time step of 1 does it work then?

Batteries all looks good. Then let's test with new motors and propellers. I have replied to the email request.

Where did you buy it? Looks like a clone!

Try a cold boot recovery as linked to in the end of this post.

It sounds very much like it is the motors and propellers. If you can switch motors and get it to work properly that is my conclusion. Send us an email to support at bitcraze.io and we can send you some spare motors and propellers. The only twist to this is that we have not seen this type of problem ...

Glad it worked out!

Then the problem is most likely that the BigQuad deck is not powered with 5V. So remove the CF Li-Po and connect the 5V output from the PDB to one of the BigQuad deck inputs marked 5V. The CF should then start when you connect the big Li-Po.