Bitcraze Forums

For your first question, it seems that you are trying to run 2 scripts at the same time? If so, this is not possible, a script will take control of a Crazyradio and of the Crazyflie connection (there should be only one client connected to the Crazyflie at once). As for the logging, you need to add i...

This is odd, you should be able to go down to 10ms. There might be a problem with the way you update the UI: I do not remember the details now, but UI and the crazyflie code runs in different threads. The UI update must pass though a signal, this way Qt will automatically put the update in a queue t...

Hi, Sounds like a nice project. For your problems: 1. I think you should look at this ticket: https://github.com/bitcraze/crazyflie-clients-python/issues/334. To be able to control the Crazyflie from a tab you need to disable the gamepad control, I added a function to do that in the ticket. Once the...

Hi, the 16bit number to RPM is fairly linear (since this is a DC motor and the bit number represents the voltage). However the thrust is not linear with the RPM. We have made an investigation about that a while ago: https://wiki.bitcraze.io/misc:investigations:thrust, in it we did devise some formul...

Hi Hubert, The node has an integrated tag mode. It shows up as an USB serial port so if you open the serial port with a terminal and type "t", the node switches in tag mode and starts ranging. You can press "h" to get some help about all the commands available. If you want to use a real serial port ...

Yes this is right. The format is radio://<radio_dongle_id>/<channel>/<datarate>[/<address>]. radio_dongle_id allows to use more than one radio on the same system to get more bandwidth. For example radio://1/42/2M would open a link on channel 42, 2Mbit/s using a second radio.

The likely cause is that you are not using the same channel in the Crazyflie configuration and in the script. Your address "radio://00/08/2M" looks a bit suspicious (the channel 08 with a leading 0), maybe you meant to use "radio://00/80/2M (channel 80)? Otherwise, the way to check the Crazyflie rad...

Hi, The factory firmware is a lighthouse V1 only firmware and the line protocol is different, this is why you had to wait a lot for a sync: the sync is not the same. The bitstream from factory should be version 2: https://github.com/bitcraze/lighthouse-fpga/tree/V2. The tools from the git V2 tag sho...

FYI, I just pushed a fix for the printing problem, it was a buffer overflow when printing the message on the console. The printout is now as expected.

The main problem is indeed that there is a conflict between the P2P communication and the communication to the PC. This is a fundamental limitation with the current implementation and the real fix would be to have the PC part of the P2P network, in your case the easiest way to achieve that is to con...