Closed AnassQach closed 1 year ago
You can connect to your drone, but your setting is to track it using a motion capture system. However, you do not receive data from your motion capture. Perhaps check your setting in motion_capture.yaml, or provide some background on how you want to track your drone so we can give some more guidance on what parameters to adjust.
Thank you for the response, i'm not using a motion capture system. Only Drone, Flowdeck and Radio dongle. But i fixed the problem. my firmware logging was disabled. Now it works, i can see the cf in rviz.
Great - thanks for your feedback.
Thank you for the response, i'm not using a motion capture system. Only Drone, Flowdeck and Radio dongle. But i fixed the problem. my firmware logging was disabled. Now it works, i can see the cf in rviz.
Hi Whoening, I currently meet the same problem. Can you explain more details? Thank you very much
@HWMathSEU since this issue is already closed, could you ask your question on https://github.com/IMRCLab/crazyswarm2/discussions ? That is the right place for support
I'm using ROS2-Galactic, Crazyswarm2 on Ubuntu 20.04. The Cfclient has no problem connecting to the crazyflie. See Screenshot:
But when i launch the Crazyswarm sim, the cf doesn't seem to appear on rviz.
Any help or tipp will be much appreciated. I'm kinda new to this.
my crazyflies.yaml:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
named list of all robots
robots: cf231: enabled: false uri: radio://0/80/2M/E7E7E7E7E7 initial_position: [0, 0, 0] type: cf21 # see robot_types
firmware_params:
cf5: enabled: true uri: radio://0/80/2M/E7E7E7E705 initial_position: [0, 0, 0] type: cf21 # see robot_types
firmware_params:
Definition of the various robot types
robot_types: cf21: motion_capture: enabled: true
only if enabled; see motion_capture.yaml
cf21_mocap_deck: motion_capture: enabled: true
only if enabled; see motion_capture.yaml
global settings for all robots
all:
firmware logging for all drones (use robot_types/type_name to set per type, or
robots/drone_name to set per drone)
firmware_logging: enabled: false default_topics:
remove to disable default topic
firmware parameters for all drones (use robot_types/type_name to set per type, or
robots/drone_name to set per drone)
firmware_params: commander: enHighLevel: 1 stabilizer: estimator: 2 # 1: complementary, 2: kalman controller: 2 # 1: PID, 2: mellinger
ring:
broadcasts: num_repeats: 15 # number of times broadcast commands are repeated delay_between_repeats_ms: 1 # delay in milliseconds between individual repeats
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++