Event types
Note
As of Dash v3.4.0 (2019-03-29), a general event type renaming and reorganization began to be implemented. This page already reflects the changes as approved by the LRAUV team.
Event types¶
ArgoReceive¶
-
Generated by: Argos
-
Description: Report Latitude/Longitude.
Command Request¶
-
Generated by: Operator
-
Description: Execute particular command.
Critical¶
-
Generated by: Vehicle
-
Description: Critical failure leading vehicle to stop the existing mission and returning to default.
DataProcessed¶
-
Generated by: TethysDash backend
-
Description: Datasets have been generated/updated.
-
Note: Events of this type are not displayed in the Log table of the Dash UI.
Deployment¶
-
Generated by: Operator
-
Description: This event indicates the start or end of a vehicle deployment.
Direct Comms ACK¶
-
Generated by: TethysDash backend
-
Description: Vehicle has received the command via cell/wire.
Direct Comms Received¶
-
Generated by: TethysDash backend
-
Description: Message received from vehicle via cell/wire.
Emergency¶
-
Generated by: Vehicle
-
Description: Vehicle is not under command and the Iridium radio is actively transmitting in SOS mode. The weight has been commanded to be dropped and the light is turned on.
Fault¶
-
Generated by: Vehicle
-
Description: A subsystem has encountered a fault. Attempts are being made to restore the subsystem.
GPS Fix¶
-
Generated by: Vehicle
-
Description: Current location.
Important¶
-
Generated by: Vehicle
-
Description: A routine message from vehicle.
Launch¶
-
Generated by: Operator
-
Description: Vehicle put in the water.
Log¶
-
Generated by: Vehicle
-
Description: A new set of logs has been generated on vehicle.
Mission Request¶
-
Generated by: Operator
-
Description: Request to execute a mission.
Note¶
-
Generated by: Operator
-
Description: A collaboration note.
Patch¶
-
Generated by: Operator
-
Description: Changes in edited mission or config file are sent to vehicle. These are normally followed by SbdSend events, which send pieces of the patch to the vehicle for processing.
Recover¶
-
Generated by: Operator
-
Description: Vehicle has been recovered.
SAT Comms Request¶
-
Generated by: TethysDash backend
-
Description: Command has been sent to the GSS (via SBD Iridium).
SAT Comms Queued¶
-
Generated by: Ground station (Iridium)
-
Description: Acknowledgement of command sent. The GSS has queued the SBD.
SAT Comms Received¶
-
Generated by: TethysDash backend
-
Description: Message received from vehicle via SBD (when
mtmsn == 0).
SAT Comms Received (Vehicle ACK)¶
-
Generated by: TethysDash backend
-
Description: Message received from vehicle via SBD (when
mtmsn != 0).
Tracking¶
-
Generated by: Vehicle
-
Description: Generated by the SBD modem on the vehicle, in a manner similar to emergency events. Normally they only occur during system power-up, and rarely at that, but we track them in case the modem cannot be initialized and the vehicle cannot tell us its position normally.