Closed ddwy closed 1 month ago
Could you share the content of your crazyflie.yaml file? it seems there is an error in there.
Could you share the content of your crazyflie.yaml file? it seems there is an error in there.
The following is the content of the crazyflie.yaml file:
# named list of all robots
robots:
cf231:
enabled: true
uri: radio://0/80/2M/E7E7E7E7E7
initial_position: [0.0, 0.0, 0.0]
type: cf21 # see robot_types
# firmware_params:
# kalman:
# pNAcc_xy: 1.0 # default 0.5
# firmware_logging:
# enabled: true
# custom_topics:
# topic_name3:
# frequency: 1
# vars: ["acc.x", "acc.y"]
cf5:
enabled: false
uri: radio://0/80/2M/E7E7E7E705
initial_position: [0.0, -0.5, 0.0]
type: cf21 # see robot_types
# firmware_params:
# kalman:
# pNAcc_xy: 1.0 # default 0.5
#firmware_logging:
# custom_topics:
# topic_name3:
# frequency: 1
# vars: ["acc.x", "acc.y", "acc.z"]
# Definition of the various robot types
robot_types:
cf21:
motion_capture:
enabled: true
# only if enabled; see motion_capture.yaml
marker: default_single_marker
dynamics: default
big_quad: false
battery:
voltage_warning: 3.8 # V
voltage_critical: 3.7 # V
# firmware_params:
# kalman:
# pNAcc_xy: 1.0 # default 0.5
#firmware_logging:
# enabled: true
# default_topics:
# pose:
# frequency: 1 # Hz
# custom_topics:
# topic_name3:
# frequency: 1
# vars: ["acc.x", "acc.y", "acc.z"]
cf21_mocap_deck:
motion_capture:
enabled: true
# only if enabled; see motion_capture.yaml
marker: mocap_deck
dynamics: default
big_quad: false
battery:
voltage_warning: 3.8 # V
voltage_critical: 3.7 # V
# firmware_params:
# kalman:
# pNAcc_xy: 1.0 # default 0.5
# 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: true
default_topics:
# remove to disable default topic
pose:
frequency: 10 # Hz
status:
frequency: 1 # Hz
#custom_topics:
# topic_name1:
# frequency: 10 # Hz
# vars: ["stateEstimateZ.x", "stateEstimateZ.y", "stateEstimateZ.z", "pm.vbat"]
# topic_name2:
# frequency: 1 # Hz
# vars: ["stabilizer.roll", "stabilizer.pitch", "stabilizer.yaw"]
# 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:
# effect: 16 # 6: double spinner, 7: solid color, 16: packetRate
# solidBlue: 255 # if set to solid color
# solidGreen: 0 # if set to solid color
# solidRed: 0 # if set to solid color
# headlightEnable: 0
locSrv:
extPosStdDev: 1e-3
extQuatStdDev: 0.5e-1
# kalman:
# resetEstimation: 1
broadcasts:
num_repeats: 15 # number of times broadcast commands are repeated
delay_between_repeats_ms: 1 # delay in milliseconds between individual repeats
Ah yes that is a bug! I'll look into it right away and notify you if I have a PR out.
Could you try out the branch of this PR https://github.com/IMRCLab/crazyswarm2/pull/574 @ddwy ?
When I run the crazyswarm keyboard control command, the following error appears:
ros2 launch crazyflie_examples keyboard_velmux_launch.py