package apollo.monitor

Get desktop application:
View/edit binary Protocol Buffers messages

Used in: dreamview.HMIStatus, SystemStatus

• optional ComponentStatus summary = 1

  A summary of all detailed status.

• optional ComponentStatus process_status = 2

  Detailed status.

• optional ComponentStatus channel_status = 3

• optional ComponentStatus resource_status = 4

• optional ComponentStatus other_status = 5

• optional ComponentStatus module_status = 6

Status summary. The value order is important, because when we summarize, larger value will overwrite smaller value: FATAL > ERROR > WARN > OK > UNKNOWN

Used in: dreamview.HMIStatus, Component, SystemStatus

• optional ComponentStatus.Status status = 1

• optional string message = 2

Used in: ComponentStatus

• UNKNOWN = 0

• OK = 1

• WARN = 2

• ERROR = 3

• FATAL = 4

• optional common.Header header = 1

• map<string, ComponentStatus> hmi_modules = 7

• map<string, Component> components = 8

• optional string passenger_msg = 4

  Some critical message for passengers. HMI should highlight it or even read loudly.

• optional double safety_mode_trigger_time = 5

  If we have this field, safety_mode should be triggered. We'll check the system action and driver action continuously. If no proper action was taken in a specified period of time (such as 10 seconds), EStop will be sent to bring the vehicle into emergency full stop.

• optional bool require_emergency_stop = 6

• optional bool is_realtime_in_simulation = 9

  In simulation mode, the monitor will publish message with this field set, so subscribers could identify it from the recorded messages.

• map<string, ComponentStatus> other_components = 10

  In some modes, other processes besides modules and monitored components may need to be monitored

• map<string, Component> global_components = 11

  In all modes, needs to detect progress and resource space.

• optional bool detect_immediately = 12