Open Ahmad-Drak opened 5 years ago
Even when running a mavsdk example and the drone is moving in gazebo, the /diagnostics topic shows this
level: 1
name: "uav/mavros: FCU connection"
message: "not connected"
hardware_id: "udp://:14541@localhost:14580"
values:
and the rostopic echo /uav/mavros/state
shows
header:
seq: 0
stamp:
secs: 0
nsecs: 0
frame_id: ''
connected: False
armed: False
guided: False
mode: ''
system_status: 0
Alternatively, gave it a takeoff command from qgroundcontrol, the drone takes off but the rostopic echo /uav/mavros/state
still reports its not connected
How can that be if the drone is actually moving?
Issue details
Running a uav and rover in one gazebo environment. I was able to control the uav via the MAVSDK FollowMe example. However, when trying to arm, or change params or mode it doesnt work (rover and/or uav)
for example,
rosrun mavros mavsys -n rover/mavros mode -c OFFBOARD
returns 'Request failed. Check mavros logs' and on the mavros node output '[ERROR] [1563869754.992496434, 27.980000000]: MODE: Unsupported FCU'MAVROS version and platform
Mavros: 0.29.2 ROS: Melodic Ubuntu: 18.04
Autopilot type and version
[ x ] PX4
Version: 1.0.0
Node logs
Diagnostics
Check ID