Bitcraze Forums

Hi, There is unfortunatly no easy way to do that generically and, as you noticed, all "deck.*" parameters are read-only. They are only indicator of the current deck initialized, not a control. What makes this hard is that the decks are initialized at startup, before the system has reached ...

Hi Leopardopt, This is odd, we have not observed such a crash for quite some time (my experience with LHv1 in faires is that I got Crazyflies going up and down (Qi charging) for 8 hours without crash). I will run some test on Monday in our flight lab to try to reproduce the problem. It is possible t...

Hi, just looking at the script I cannot see anything obviously wrong. One nit pick is that you will get better performance by putting both your Crazyflies on the same channel but different address. So for example by setting URI2 to radio://0/80/2M/E7E7E7E7E7. What print-out do you get from your scri...

Hi,

What positioning system are you using when that happen and what estimator/controller are you using? Can you maybe send a minimal python script where the problem happens so that we can test it here as well?

Hi, Are you getting problem with both the 2 new flow deck or only one of them?

In any way, it does look like a hardware problem, please send a mail to contact _at_ bitcraze.io and we will fix a replacement.

Hi,
We have been using the "Manfrotto 035 Superclamp" on our truss to setup the lighthouse basestation and they work quite fine. We have a Global Truss F23 so it is a bit thinner, but the clamp is documented to work with up to 55mm tubes.

Great that you fixed your problem! Thanks for posting the solution. This definitely looks like a bug in the pulse-processing part of the lighthouse deck driver. I created a ticker and we will investigate if we can reproduce and isolate the crash: https://github.com/bitcraze/crazyflie-firmware/issues...

This is odd. On the hardware side, you should check that the lighthouse deck is actually well started. Then the Crazyflie is fully started, the deck's Blue LED should be ON and the Red LED should be OFF. Then the green LED will be lit when everything goes well and there is good signals coming into t...

No worry, good that it worked! About merging: we have been working at making that easier by allowing out-of-tree app and deck drivers. The intent it to allow keeping the very custom code separated from the core code. When you get around to look at merging, might be a good way to go. Tell us if there...

Hi,
The bug is now fixed. If you launch the "update all" script in the VM you should now be able to load the system config you have previously saved.
Thanks for reporting the problem!