This is an old revision of the document!
C2MS
Table 8-9: Log message SEVERITY of 0=Debug, 1=Nominal, 2=Medium, 3=High, 4=Critical
Change to DEBUG, INFO, WARN, ERROR, FATAL [NEED C2MS issue]
Table 8-11: RED/YEL/NORM
Table 8-26: RESPONSE-STATUS enum 1=Ack, 2=Working/keep alive, 3=Successful completion, 4=Failed completion, 5=Invalid Request, 6=Final Response
Table 8-53: DEVICE.n.STATUS enum 0=Debug, 1=Normal/Green, 2=Yellow, 3=Orange, 4=Red
Table 8-58: COMPONENT-STATUS enum 0=Debug, 1=Normal/Green, 2=Yellow, 3=Orange, 4=Red
Table 8-84: MNEMONIC.n.STATUS enum 1=Valid, 2=Valid/No data, 3=Invalid
Table 8-104: Attributes: RED-HIGH, RED-LOW, YELLOW-HIGH, YELLOW-LOW
Table 8-109: Attributes: RED-HIGH, RED-LOW, YELLOW-HIGH, YELLOW-LOW
Table 8-126: Attributes: RED-HIGH, RED-LOW, YELLOW-HIGH, YELLOW-LOW
Table 8-136: XTCE-STATUS enum Astro defines just: 2=Invalid, 9=Complete, 10=Failed
Table 8-141: CMD-ECHO-RESULT: NOTC=Not compared, GOOD=Good compare, MISC=Miscompare, TOUT=Timed out waiting for echo, UEX=Unexpected echo received
Table 8-160: PRIORITY enum 1=Nominal, 2=Medium, 3=High
Table 8-171: DATA-QUALITY: RAW, VALIDATED, DEGRADED
CSRM
Alarms are not defined in this specification
GEMS
Alarms are not defined in this specification
SOLM
Based on review, there is no common mechanism in the SOLM specification for alarm/limit levels being defined.
Alarms are not defined in this specification (no mention of alarm, warning, yellow, etc.)
Limits are mentioned in <Parameter>_<Attribute> / Restriction of SOLM Python mapping, page 59
XTCE
Alarm levels of: normal, watch, warning, distress, critical, and severe
Significance levels of: normal, vital, critical, forbidden, user1, user2
None is similar to “in limits” or “normal”
XUSP
Alarm levels of: normal, warning, and severe (XUSP 1.0 CSV)
Significance levels of: none, critical, severe (XUSP 1.0 PDF)
None is not a type in XTCE, nor is severe.
For XUSP 1.1/XTCE 1.2: Change to normal, critical, forbidden [NEED XUSP issue]