Bitcraze Forums

Hi Arnaud, my anchors were freshly purchased and I hadn't done anything but flash the latest firmware on them and configuring their IDs following your tutorial. Anyway, now that their radio settings are configured correctly, I don't encounter many connection problems anymore. My position estimation ...

Hi, all parts of the system are updated to the latest firmware version. In the meantime, I found the error and would like to share my solution for others: I connected each node to the computer via USB. I then used "sudo picocom /dev/ttyACM0" for serial access to the node (picocom can be in...

Hi Arnaud, I have a very similar problem to teihoshi, the anchor position fields stay white no matter what I do and the anchors do not show in the graphic. Depending on which Crazyflie I use, I can sometimes also not connect to all anchors. Do you know how I can fix these issues? Regards, Andy Scree...

Maybe a bit more precise, where in the firmware does the type of setpoint sent to the Crazyflie get classified and how are the setpoints processed differently according to the setpoint type?

I would like to try my own high-level controller on the Crazyflie. This controller outputs reference values for (roll, pitch, yaw rate, thrust) that should be sent to the Crazyflie as a setpoint. I saw that in the Commander.py class in the crazyflie_lib there are functions for sending setpoints of t...

Small update: My mistake was to assume that the script would scan for available cfs, check for their addresses and connect to them automatically. Once I found out that there were actually two addresses hard-coded in the scripts, it was easy to adapt them to my system and get it working, even with on...

Hey guys, I'm getting started with controlling Crazyflies via the python library. When I switch on one cf and execute the basiclog.py or ramp.py, everything works perfectly. However, when a second cf is switched on nearby, after running one of the scripts the client detects several radios and connec...