Crazyfly gets communicated the wrong position #800
-
Hi! Our current setup:
My investigations so far found the following:
The message about the incompatible QoS appears even after a full restart of the system.
Can this be a setup problem? If you have an idea of what is wrong, I would be very grateful. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
I think the server is hardcoded to a deadline of 100Hz, see https://github.com/IMRCLab/crazyswarm2/blob/a68652755af4e17735556643cf10e2d20c600fe3/crazyflie/scripts/crazyflie_server.py#L340. in motion_capture_tracking.yaml, change the deadline setting accordingly. The issue you are seeing is that the server can't receive /poses and thus it doesn't send the qualisys information to the drone. The on-board Kalman filter detects divergence and resets itself every 25s. |
Beta Was this translation helpful? Give feedback.
I think the server is hardcoded to a deadline of 100Hz, see https://github.com/IMRCLab/crazyswarm2/blob/a68652755af4e17735556643cf10e2d20c600fe3/crazyflie/scripts/crazyflie_server.py#L340. in motion_capture_tracking.yaml, change the deadline setting accordingly.
The issue you are seeing is that the server can't receive /poses and thus it doesn't send the qualisys information to the drone. The on-board Kalman filter detects divergence and resets itself every 25s.