Replies: 1 comment
-
Hi, thanks for the detailed report. There are known issues with the communication (lost packets), which explain the behavior of a drone not executing a command. Possible solutions (in order of preference):
If you want to use two radios, make sure that you change the second URI to radio://1/90/2M/E7E7E7E705, otherwise you use a single radio that constantly has to change channels. If you want to use a single radio, make sure to use the same channel. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We made a test with two crazyflies but it shows that the control is unstable. The commands sent to crazyflies are like that:
cf4: (1,0,0) takeoff (1,0,0.5) goTo (1, 1,0.5) goTo (1,0,0.5) goTo (1, 1,0.5) goTo (1,0,0.5) ...... land
cf5: (0,0,0) takeoff (0,0,0.5) goTo (0,-1,0.5) goTo (0,0,0.5) goTo (0,-1,0.5) goTo (0,0,0.5) ...... land
However, some crazyflie may keep hovering after
goTo
command was sent.We have noticed some warnings in terminal log like:
but we don't know how to fix it. What problem could it be related to?
Other informations:
Mocap system: Qualisys, running at 100Hz
Radio: 2x Crazyradio 2.0
URI: cf4: radio://0/80/2M/E7E7E7E704, cf5 radio://0/90/2M/E7E7E7E705
terminal log:
cfclient debug tab:
cfclient console tab:
SUP: Ready to fly
Beta Was this translation helpful? Give feedback.
All reactions