Bitcraze Forums

Hi, This is a very interesting project, I have been thinking of playing with that but never had the time or a use-case for it. Using multiple radio to communicate with one Crazyflie is not implemented but it is technically possible and depending of your requirements it might not be too hard to imple...

I just tried RTT and it does work with OpenOCD and with ST-Link V2/V3! The crazyflie firmware needs to be built with "DEBUG_PRINT_ON_SEGGER_RTT=1" in config.mk or on the command line. I added a "make rtt" target to the makefile to enable it: https://github.com/bitcraze/crazyflie-...

It may be that the split packet is bugged somehow. this is not impossible. One way to check would be to make a parameter with a smaller name that makes the packet fit in a single BLE packet (or rename the parameter you want to set) and seeing if this solves your problem. If it does, we have a bug in...

I could not find anything wrong with your function. Have you looked for the answer from the Crazflie? The Crazyflie should set a packet back with an error code indicating success (0) or failure (non 0). How are you testing the alt-hold? The way alt-hold is implemented in the Crazyflie, it should be ...

There is a radio packet implemented exactly for this usecase: param set by name: https://www.bitcraze.io/documentation/repository/crazyflie-firmware/master/functional-areas/crtp/crtp_parameters/#set-by-name. This allows to set a parameter by sending its group and name in the packet. So it would allo...

Hi, This should technically work but the limitation is mostly with the Firmware of the Crazyradio. What you want in that case is a "sniffer" mode that listens to one channel/address and prints all received packets. Unfortunately the Crazyradio does not have such a mode implemented. There i...

The velocity is available as log variable in the variables "stateEstimate.vx", "stateEstimate.vy" and "stateEstimate.vz". crazyflie_ros allows to setup logblocks to log variables at regular interval and make them available as a topic. As an extra note: a lot of informat...

Hi, What connection problems are you having? There should be no need to reprogram the radio except in very specific cases (ie. when using Crazyswarm). So, if you use Crazyswarm you should follow their doc on a real Linux machine to reprogram the radio, otherwise tell us what problems you are having ...

Hi, Sorry for the delayed answer, I can answer in order: 1. Yes just a reset is enough 2. It can the the Linux modem detection code that is affecting your node. This is odd since we actually designed the node menu to not be affected by it. In any way, you can disable the modem selection by running: ...

You are likely hitting a hard-fault very early in the boot. The best would be to connect a debugger to the Crazyflie and to use gdb to find the source of the hardfault. One lead could be to check the memory usage: are you doing anything that uses a lot of stack or try to allocate a lot of memory usi...