Updating crazyflie firmware to silence warning #491
-
Hey guys, As mentioned in some other issues/discussions, I get the following warning on startup of the CS2 server:
I then get the following repeat warning:
I just have a singular crazyflie with unique marker arrangements, tracking with Optitrack and Motive, for one crazyradio2. My Motive version is old (2.2.0), so I use optitrack_closed_source. I am also working through the best settings: do I define an asset in Motive, do I not, do I use libRigidBodyTracker, et c. Any additional thoughts on that would also be appreciated. Thanks, |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
Firmware: The latest would require you to compile it yourself (master branch from bitcraze). You can also adjust the receive rate thresholds in server.yaml to silence the warnings. Config: My personal favorite is to use a single marker, and not defining an asset in Motive. If you do need the external pose information, I would use Tracker for Vicon, but no asset in Motive (because it doesn't have a motion filter and tends to produce axis flips). |
Beta Was this translation helpful? Give feedback.
Firmware: The latest would require you to compile it yourself (master branch from bitcraze). You can also adjust the receive rate thresholds in server.yaml to silence the warnings.
Config: My personal favorite is to use a single marker, and not defining an asset in Motive. If you do need the external pose information, I would use Tracker for Vicon, but no asset in Motive (because it doesn't have a motion filter and tends to produce axis flips).