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
It only sets the flag if the param COM_ARM_WO_GPS is set to 0 meaning "Require GPS to arm".
I can see that by setting this param to 0 we make sure to only fly with GPS, however, I would argue, that whenever you switch to a mode which requires GPS, and relies on it, you essentially have the GPS "enabled". Or you could go as far as that if you run the GPS drivers, then clearly the GPS is "enabled.
For context: I've stumbled on this when implementing this flag in MAVSDK: mavlink/MAVSDK#1794
I can work around the oddity for now but - in my opinion - it is not really according to how I'd interpret the spec.
PX4 does - by default - not set the flag SYS_STATUS.onboard_control_sensors_enabled for GPS.
https://mavlink.io/en/messages/common.html#SYS_STATUS
It only sets the flag if the param COM_ARM_WO_GPS is set to 0 meaning "Require GPS to arm".
I can see that by setting this param to 0 we make sure to only fly with GPS, however, I would argue, that whenever you switch to a mode which requires GPS, and relies on it, you essentially have the GPS "enabled". Or you could go as far as that if you run the GPS drivers, then clearly the GPS is "enabled.
For context: I've stumbled on this when implementing this flag in MAVSDK: mavlink/MAVSDK#1794
I can work around the oddity for now but - in my opinion - it is not really according to how I'd interpret the spec.
Here is where the flag is set:
PX4-Autopilot/src/modules/commander/Arming/PreFlightCheck/checks/ekf2Check.cpp
Line 241 in 5e1f62e
The text was updated successfully, but these errors were encountered: