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
Currently a waypoint in PX4 consists of the following fields
latitude (WGS84)
longitude (WGS84)
relative_altitude
The problem is that given the same mission file, a mission execution would be different depending on where the vehicle starts. Even worse, when the vehicle is started from the same position, the vehicle will fly different altitudes depending on where the EKF origin is initialized.
This can become even worse when the local origin resets, changing the mission locations depending on where the origin is.
Mavlink also seems to not specify what the altitude field means for the MAV_CMD_DO_REPOSITION
To Reproduce
Fly a mission
Restart the vehicle in a different altitude
Fly another mission
Expected behavior
With a same mission file, the vehicle flies the same sequence of positions.
Screenshot / Media
No response
Flight Log
No flight log
Software Version
Latest main
Flight controller
All
Vehicle type
None
How are the different components wired up (including port information)
Describe the bug
Currently a waypoint in PX4 consists of the following fields
The problem is that given the same mission file, a mission execution would be different depending on where the vehicle starts. Even worse, when the vehicle is started from the same position, the vehicle will fly different altitudes depending on where the EKF origin is initialized.
This can become even worse when the local origin resets, changing the mission locations depending on where the origin is.
Mavlink also seems to not specify what the altitude field means for the
MAV_CMD_DO_REPOSITION
To Reproduce
Expected behavior
With a same mission file, the vehicle flies the same sequence of positions.
Screenshot / Media
No response
Flight Log
No flight log
Software Version
Latest
main
Flight controller
All
Vehicle type
None
How are the different components wired up (including port information)
No response
Additional context
The text was updated successfully, but these errors were encountered: