px4-firmware/msg/GeofenceResult.msg

uint64 timestamp                        # time since system start (microseconds)
uint8 GF_ACTION_NONE = 0                # no action on geofence violation
uint8 GF_ACTION_WARN = 1                # critical mavlink message
uint8 GF_ACTION_LOITER = 2              # switch to AUTO|LOITER
uint8 GF_ACTION_RTL = 3                 # switch to AUTO|RTL
uint8 GF_ACTION_TERMINATE = 4           # flight termination
uint8 GF_ACTION_LAND = 5                # switch to AUTO|LAND

bool geofence_max_dist_triggered	# true the check for max distance from Home is triggered
bool geofence_max_alt_triggered		# true the check for max altitude above Home is triggered
bool geofence_custom_fence_triggered	# true the check for custom inclusion/exclusion geofence(s) is triggered

uint8 geofence_action           	# action to take when the geofence is breached
Apply Google Style to Commander Private methods, rename geofence message geofence_violation to primary_geofence_breached. 2022-09-05 21:17:24 -03:00			`uint64 timestamp # time since system start (microseconds)`
			`uint8 GF_ACTION_NONE = 0 # no action on geofence violation`
			`uint8 GF_ACTION_WARN = 1 # critical mavlink message`
			`uint8 GF_ACTION_LOITER = 2 # switch to AUTO\|LOITER`
			`uint8 GF_ACTION_RTL = 3 # switch to AUTO\|RTL`
			`uint8 GF_ACTION_TERMINATE = 4 # flight termination`
			`uint8 GF_ACTION_LAND = 5 # switch to AUTO\|LAND`
geofence violation actions 2015-09-27 20:49:01 -03:00
Geofence: rework messaging and notification - do reporting of breaching in-air only in geofenceCheck - remove geofence_violation_reason_t - replace geofence_breached field in GeofenceResult.msg with 3 fields (one for each GF type: max dist, max alt, custom geofence) - the warning message after breaching a GF is only done by Commander, and it's specific to the GF type failure Signed-off-by: Silvan Fuhrer <silvan@auterion.com> 2023-11-16 09:33:44 -04:00			`bool geofence_max_dist_triggered # true the check for max distance from Home is triggered`
			`bool geofence_max_alt_triggered # true the check for max altitude above Home is triggered`
			`bool geofence_custom_fence_triggered # true the check for custom inclusion/exclusion geofence(s) is triggered`
mission require valid landing after DO_LAND_START 2017-04-16 22:16:47 -03:00
Geofence: rework messaging and notification - do reporting of breaching in-air only in geofenceCheck - remove geofence_violation_reason_t - replace geofence_breached field in GeofenceResult.msg with 3 fields (one for each GF type: max dist, max alt, custom geofence) - the warning message after breaching a GF is only done by Commander, and it's specific to the GF type failure Signed-off-by: Silvan Fuhrer <silvan@auterion.com> 2023-11-16 09:33:44 -04:00			`uint8 geofence_action # action to take when the geofence is breached`