This was already done before the refactor and was assumed to not be necessary.
The problem is that these mission items result in a strang looking vertical slow down directly followed
by an acceleration during the landing phase.
* fixes to restart the state machine if sensor does not init correctly
Signed-off-by: dirksavage88 <dirksavage88@gmail.com>
* fixes
Signed-off-by: dirksavage88 <dirksavage88@gmail.com>
* increase fail count
Signed-off-by: dirksavage88 <dirksavage88@gmail.com>
* remove extra flush, switch from warn to debug, add enum states for sensor bring-up
Signed-off-by: dirksavage88 <dirksavage88@gmail.com>
* remove dead code, decrease restart fail count metric, break out of loop with consec errors if over the fail count and not init
Signed-off-by: dirksavage88 <dirksavage88@gmail.com>
---------
Signed-off-by: dirksavage88 <dirksavage88@gmail.com>
* Added AUAV absolute pressure sensing
* Moved func to abstract base class
* Probe and params
* Fixed arg parsing and added auto start
* refactorings
* Added sample perf
* Fixed CI findings
* Simplified rc.sensors condition
* Added Addition and Subtraction to Slices
* MatrixSliceTest: refactor Addition/Substraction checks
* Slice: replace operations returning a Matrix with calling the existing Matrix function
---------
Co-authored-by: Matthias Grob <maetugr@gmail.com>
removed thresholds for closed loop setpoints and added minimum thresholds for yaw rate and speed measurements instead to avoid moving due to measurement noise
* introduced altitude acceptance radius in position setpoint for fixed
wing guidance
- allows navigator to explicitly set the altitude acceptance radius
- needed for staright line landing support
* added ignore_alt_acceptance to position setpoint message to allow guidance
logic to ignore altitude error on waypoint
- can be useful to prevent loitering at a waypoint within a mission landing sequence
* only set altitude acceptance radius to infinity for a waypoint inside a mission landing
for fixed wing vehicles
* navigator: return altitude acceptance radius from triplet if it's valid
* FixedWingPositionControl: check if alt acceptance radius provided in position setpoint
is larger 0
---------
Signed-off-by: RomanBapst <bapstroman@gmail.com>
Co-authored-by: Alvaro Fernandez <alvaro@auterion.com>
The RTL sequence from the navigator requires the vehicle to land. This is now handled for rovers by setting its state to landed if it is within the acceptance radius of the home position when in return mode.
Special handling for LAND mode: always allow to switch into it such that if used
as emergency mode it is always available. When triggering it the user generally wants
the vehicle to descend immediately, and if that means to switch to DESCEND it is fine.
Signed-off-by: Silvan Fuhrer <silvan@auterion.com>
I could not extract the open_drone_id helpers to a separate lib because
it would require the mavlink headers while the mavlink library would
also depend on it, so it ended up being a circular dependency.
Instead, I'm now just using the headers from within the mavlink module
as well as from the uavcan driver.
