Bitcraze Forums

Hi! The code looks good to me. The x/y/z should contain the position of the "anchor" and the distance should contain the measured distance to the point. It is possible that an outlier filter would help, but be careful. A kalman filter is essentially designed to use all samples but an outli...

With one LPS anchor the only information that will be available is the distance to the anchor, but you would not know the direction. Essentially you would know that you are somewhere on a sphere around the anchor positions and this would not be enough to understand where you are. You would need more...

If you are using the lighthouse system you need a lighthouse deck (https://store.bitcraze.io/collections/decks/products/lighthouse-positioning-deck) and preferably 2 lighthouse base stations. In this case you would know the position all the time and returning to the starting point would be as simple...

Unfortunately no date but we are working on it continuously. Most of the functionality in the Crazyflie is finished except a mechanism to update the binary in the deck. Apart from that it is mainly client work that remains.

This is a known issue we are working on, let me explain why it happens. The rotor in a lh2 base station spins at 50 revolutions/s but with a slight shift in frequency based on the channel it is configured for. The reason is that base stations interfere with each other when the light sweeps hit a sen...

Hi!

Yes, the Swarm class is not as easy to use as one would like...

I improved the error reporting a bit, https://github.com/bitcraze/crazyflie-l ... issues/179
Pull in the latest version of the lib and run your code again. Hopefully you will get the call stack of the original exception

I'm not a windows expert, but I think you can pipe in windows as well. I don't have a windows machine to test on, but try something like this: from your normal command prompt (not in python), cd to the root of the repository Then run the scripts python tools\sniffer\sniffer_binary.py | python tools\...

Hi!

The general idea is to pipe the output from the sniffer into the decoder
Assuming you are using a unix shell you should do something like this

Hi! I'm not sure what the problem is, but will take a closer look. We are currently changing a lot for the lighthouse as we are trying to reach a first stable release. We are trying to keep it fairly clean and functional during the process but it is not unlikely that we break something temporarily. ...

The in just means that no callback is registered to tell you that the write was actually successful. In the trajectory example we did add a callback (_upload_done()) if you want to check out how to do that.