{
"SettingsVersion": 2.0,
"SimMode": "Multirotor",
"ClockType": "",
"ClockSpeed": 1,
"ViewMode": "NoDisplay",
"CameraDirector": {
"FollowDistance": -1.5,
"Position": {
"X": -1.5,
"Y": 0,
"Z": -1
}
},
"Vehicles": {
"Drone1": {
"VehicleType": "SimpleFlight",
"AutoCreate": true,
"DefaultVehicleState": "Disarmed",
"Cameras": {
"bottom_center": {
"X": 0.15, "Y": 0, "Z": 0.15,
"Pitch": 0, "Roll": 0, "Yaw": 0,
"CaptureSettings": [
{
"ImageType": 0,
"Width": 1280,
"Height": 720,
"FOV_Degrees": 69.0,
"TargetGamma": 2.2,
"MotionBlurAmount": 0
},
{
"ImageType": 1,
"Width": 1280,
"Height": 720,
"FOV_Degrees": 87.0,
"AutoExposureMaxBrightness": 0.64,
"AutoExposureMinBrightness": 0.03
}
]
}
}
}
},
"SubWindows": [
{
"WindowID": 0,
"ImageType": 0,
"CameraName": "bottom_center",
"VehicleName": "",
"Visible": false
},
{
"WindowID": 2,
"ImageType": 3,
"CameraName": "bottom_center",
"VehicleName": "",
"Visible": false
}
]
}
Description
Hi there!
I am experiencing an issue with the ROS2 wrapper for CoSysAirSim where my PID controller node is unable to proceed, likely due to a discrepancy in the odometry frame conventions.
Steps to Reproduce
ros2 launch airsim_ros_pkgs airsim_node.launch.pyros2 launch airsim_ros_pkgs position_controller_simple.launch.pyObserved Behavior
The PID node starts but hangs at the following point:
Analysis & Attempts to Fix
I noticed a mismatch in the published/subscribed topics:
airsim_node publishes to:
/airsim_node/drone_1/odom_localpid_controller expects:
/airsim_node/drone_1/odom_local_nedI attempted to resolve this by remapping the topics in the launch file or using
ros2 run --remapping, but the issue persists. It seems that simply changing the topic name isn't enough, suggesting there might be a deeper issue with how the frames are handled or how the tf2 transform tree is being broadcasted between the NED and ENU conventions.Environment
Thank you for your help!