Bitcraze Forums

Hello Arnaud than you for your answer. Some of them restart and others lose connection. Another possibility may be a lack of feertos heap memory, because I decrease the assignment to 36000kb, (making room for the trajectory in flash memory) But I don't see how the quantity of CFs can be related and ...

We are experimenting a similar situation: We flew a swarm of 16 CF2.0 with the trajectory in flash and suddenly some of them just fall with no reason, seems like they lose power, but we check all batteries and all were charged.(4CFs Fall down). All CFs are numerated from 1 to 16 When we flew from 1 ...

We are fliying 16 CF in swarm but when one falls upside down the laser from deck, alters the sensors of the others when they fly above.
Can we change the behavior of the crash/tumble detection?

Thank you Kristoffer for all your valuable help, I finally have success preloading the trajectory. I have a new problem because the trajectory is to big, so if i assign a lot memory to the trajectory the firmware halts reporting that lack of memory for the app.c, but if i assign less the firmware bu...

Im now trying to preload the trajectory in memory following this branch
https://github.com/bitcraze/crazyflie-f ... e/lth-2019
but the LPS deck hangs on boot
Is the firmware hardcoded to CF2.1?
How can i modify this?

Yes, i will atach it to the post, i am following this commit
https://github.com/bitcraze/crazyflie-f ... dd716c74c8

I make another changes following it, but i am still getting error messages

OS is Ubuntu 18.04, we have a local version of the firmware but is the last version with a few changes in the size of the trajectories memory in the high level commander module. this is a transcription of the message in terminal: CLEAN_VERSION VTMPL version.c CC version.o CC app.o src/modules/src/ap...

We are trying to load a trajectory in the CF via a firmware using the app.c functionality you used in IROS demo but get some errors in the compilation of the firmware.

Can you please explain us how to expose the functions globally. The error refers most to all the highlevel comander functions.

I had the same issue but only in TWR mode, when i change to TDMO2 or TDMO3 the deck have a normal behavior, so i discard that the cause was a bad connection.

I used a flow deck but deactivating the flow information and only using z distance information in the test, with the same results.

I recently read in your blog a short description of the roadrunner device and is described as a CF2.1 and it acts as an anchor. Can i use a CF2.0 as an anchor in a LPS using TDOA3 . I like to evaluate how the use of more anchors improves the precision of the location especially in z axis, currently ...