You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm writing a offboard controller in c++. It's based on examples found in the px4_ros_com repository. The program can fly a quadcopter perfectly fine in simulator (gazebo + QGroundControl). But on real Pixhawk hardware it fails to switch to offboard randomly maybe 90% of tries. I'm looking for method of figuring out what's the cause. QGroundControl just says offboard was rejected, but doesn't provide any detail on actual reason.
I should be outputting the correct topics (trajectorysetpoint in position and velocity control modes) and the fact that it works always on simulator and sometimes on hardware also suggests this. Of course there is a chance of a bug but I'm stuck trying to find it.
The hardware itself seems healthy and flies fine using non-offboard control modes.
Any help is appreciated.
The text was updated successfully, but these errors were encountered:
On real drone we have a transmitter switch to go to offboard mode, so it's not possible to control it from QGC. In simulator switching to offboard from QGC works always. I'll try subscribing to VehicleCommandAck and see if it gives any useful hints.
I'm writing a offboard controller in c++. It's based on examples found in the px4_ros_com repository. The program can fly a quadcopter perfectly fine in simulator (gazebo + QGroundControl). But on real Pixhawk hardware it fails to switch to offboard randomly maybe 90% of tries. I'm looking for method of figuring out what's the cause. QGroundControl just says offboard was rejected, but doesn't provide any detail on actual reason.
I should be outputting the correct topics (trajectorysetpoint in position and velocity control modes) and the fact that it works always on simulator and sometimes on hardware also suggests this. Of course there is a chance of a bug but I'm stuck trying to find it.
The hardware itself seems healthy and flies fine using non-offboard control modes.
Any help is appreciated.
The text was updated successfully, but these errors were encountered: