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
Hi everyone!
I am running px4 in sitl mode in a virtualbox environment, hooked up with jMAVSim.
Mavros is running correctly, receives the heartbeats from the simulated px4.
QGC is even connected to px4 using mavros' proxy port.
QGC works correctly, i can arm the px4 or do whatever I want.
When trying to arm the px4 with mavros by running: rosrun mavros mavsafety arm
I get the error Request failed. Check mavros logs
If I try rosservice call /mavros/cmd/arming "value: true"
I get success: false result 4
Nothing happens in the px4 terminal when those commands are issued.
I am using the latest git version of everything.
mavros is launched using roslaunch mavros px4.launch
I have exactly the same problem as in #283 except I am running a simulated px4 (software in the loop).
Please check console output from px4.launch (mavros log).
Usually when arm is failing there some messages FCU: which describe problem (coming from autopilot).
Especially look at prearm messages.
Hi everyone!
I am running px4 in sitl mode in a virtualbox environment, hooked up with jMAVSim.
Mavros is running correctly, receives the heartbeats from the simulated px4.
QGC is even connected to px4 using mavros' proxy port.
QGC works correctly, i can arm the px4 or do whatever I want.
When trying to arm the px4 with mavros by running:
rosrun mavros mavsafety arm
I get the error
Request failed. Check mavros logs
If I try
rosservice call /mavros/cmd/arming "value: true"
I get success:
false result 4
Nothing happens in the px4 terminal when those commands are issued.
I am using the latest git version of everything.
mavros is launched using
roslaunch mavros px4.launch
I have exactly the same problem as in #283 except I am running a simulated px4 (software in the loop).
Thank you for your help!
The text was updated successfully, but these errors were encountered: