dmsActivateMsgError

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dmsActivateMsgError",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "other",
    "(",
    "1",
    ")",
    ",",
    "none",
    "(",
    "2",
    ")",
    ",",
    "priority",
    "(",
    "3",
    ")",
    ",",
    "messageStatus",
    "(",
    "4",
    ")",
    ",",
    "messageMemoryType",
    "(",
    "5",
    ")",
    ",",
    "messageNumber",
    "(",
    "6",
    ")",
    ",",
    "messageCRC",
    "(",
    "7",
    ")",
    ",",
    "syntaxMULTI",
    "(",
    "8",
    ")",
    ",",
    "localMode",
    "(",
    "9",
    ")",
    ",",
    "centralMode",
    "(",
    "10",
    ")",
    ",",
    "centralOverrideMode",
    "(",
    "11",
    ")",
    ",",
    "defaultFont",
    "(",
    "12",
    ")",
    ",",
    "beaconPlan",
    "(",
    "13",
    ")",
    "}",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"<Definition> This is an error code used to identify why a message was not displayed. Even if multiple errors occur, only one error is indicated. <Format> other (1): any error not defined below. none (2): no error. priority(3): the activation priority in the MessageActivationCodeV4 is less than the run time priority of the currently displayed message. If this error occurs, the corresponding bit (message error) within the 'shortErrorStatus' object shall be set. messageStatus(4): the 'dmsMessageStatus' of the message to be activated is not 'valid'. If this error occurs, the corresponding bit (message error) within the 'shortErrorStatus' object shall be set. Note: In the 1997 version of NTCIP 1203, this bit was assigned the name of 'underValidation'. It has been renamed to better reflect the fact that this bit can be set due to the message being in a number of different states, not just the 'validating' state. messageMemoryType(5): the message memory type in the MessageActivationCodeV4 is not supported by the device. If this error occurs, the corresponding bit (message error) within the 'shortErrorStatus' object shall be set. messageNumber(6): the message number in the MessageActivationCodeV4 is not supported or is not defined (populated) by the device. If this error occurs, the corresponding bit (message error) within the 'shortErrorStatus' object shall be set. messageCRC(7): the checksum in the MessageActivationCodeV4 is different than the CRC value contained in the 'dmsMessageCRC'. If this error occurs, the corresponding bit (message error) within the 'shortErrorStatus' object shall be set. syntaxMULTI(8): a MULTI syntax error was detected during message activation. The error is further detailed in the 'dmsMultiSyntaxError', 'dmsMultiSyntaxErrorPosition', and 'dmsMultiOtherErrorDescription' objects. If this error occurs, the corresponding bit (message error) within the 'shortErrorStatus' object shall be set. localMode(9): the central system attempted to activate a message while the 'dmsControlMode' object is 'local'. This error shall NOT be set if the value of the 'dmsControlMode' is set to 'central', or 'centralOverride'. If this error occurs, the corresponding bit (message error) within the 'shortErrorStatus' object shall be set. centralMode (10): a locally connected system attempted to activate a message while the 'dmsControlMode' object is 'central'. This error shall NOT be set if the value of the 'dmsControlMode' is set to 'local'. If this error occurs, the corresponding bit (message error) within the 'shortErrorStatus' object shall be set. centralOverrideMode (11): a locally connected system attempted to activate a message while the 'dmsControlMode' object is 'centralOverride', even though the local switch is set to local control. If this error occurs, the corresponding bit (message error) within the 'shortErrorStatus' object shall be set. defaultFont (12): The font referenced by defaultFont has a fontStatus other than readyForUse or inUse. beaconPlan (13): The beacon plan referenced by dmsMessageBeacon has a dmsBeaconPlanRowStatus other than active. A 'criticalTemperature' alarm shall have no effect on the 'activation' of a message, it only effects the display of the active message. Thus, a message activation may occur during a 'criticalTemperature' alarm and the sign controller behaves as if the message is displayed. However, the shortErrorStatus indicates a criticalTemperature alarm and the sign face illumination is off. As soon as the DMS determines that the 'criticalTemperature' alarm is no longer present, the DMS shall display the message stored in the currentBuffer. <Parameter Type> Status <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.6.17\"",
    "::=",
    "{",
    "signControl",
    "17",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "other",
            1
          ],
          [
            "none",
            2
          ],
          [
            "priority",
            3
          ],
          [
            "messageStatus",
            4
          ],
          [
            "messageMemoryType",
            5
          ],
          [
            "messageNumber",
            6
          ],
          [
            "messageCRC",
            7
          ],
          [
            "syntaxMULTI",
            8
          ],
          [
            "localMode",
            9
          ],
          [
            "centralMode",
            10
          ],
          [
            "centralOverrideMode",
            11
          ],
          [
            "defaultFont",
            12
          ],
          [
            "beaconPlan",
            13
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "<Definition> This is an error code used to identify why a message was not displayed. Even if multiple errors occur, only one error is indicated. <Format> other (1): any error not defined below. none (2): no error. priority(3): the activation priority in the MessageActivationCodeV4 is less than the run time priority of the currently displayed message. If this error occurs, the corresponding bit (message error) within the 'shortErrorStatus' object shall be set. messageStatus(4): the 'dmsMessageStatus' of the message to be activated is not 'valid'. If this error occurs, the corresponding bit (message error) within the 'shortErrorStatus' object shall be set. Note: In the 1997 version of NTCIP 1203, this bit was assigned the name of 'underValidation'. It has been renamed to better reflect the fact that this bit can be set due to the message being in a number of different states, not just the 'validating' state. messageMemoryType(5): the message memory type in the MessageActivationCodeV4 is not supported by the device. If this error occurs, the corresponding bit (message error) within the 'shortErrorStatus' object shall be set. messageNumber(6): the message number in the MessageActivationCodeV4 is not supported or is not defined (populated) by the device. If this error occurs, the corresponding bit (message error) within the 'shortErrorStatus' object shall be set. messageCRC(7): the checksum in the MessageActivationCodeV4 is different than the CRC value contained in the 'dmsMessageCRC'. If this error occurs, the corresponding bit (message error) within the 'shortErrorStatus' object shall be set. syntaxMULTI(8): a MULTI syntax error was detected during message activation. The error is further detailed in the 'dmsMultiSyntaxError', 'dmsMultiSyntaxErrorPosition', and 'dmsMultiOtherErrorDescription' objects. If this error occurs, the corresponding bit (message error) within the 'shortErrorStatus' object shall be set. localMode(9): the central system attempted to activate a message while the 'dmsControlMode' object is 'local'. This error shall NOT be set if the value of the 'dmsControlMode' is set to 'central', or 'centralOverride'. If this error occurs, the corresponding bit (message error) within the 'shortErrorStatus' object shall be set. centralMode (10): a locally connected system attempted to activate a message while the 'dmsControlMode' object is 'central'. This error shall NOT be set if the value of the 'dmsControlMode' is set to 'local'. If this error occurs, the corresponding bit (message error) within the 'shortErrorStatus' object shall be set. centralOverrideMode (11): a locally connected system attempted to activate a message while the 'dmsControlMode' object is 'centralOverride', even though the local switch is set to local control. If this error occurs, the corresponding bit (message error) within the 'shortErrorStatus' object shall be set. defaultFont (12): The font referenced by defaultFont has a fontStatus other than readyForUse or inUse. beaconPlan (13): The beacon plan referenced by dmsMessageBeacon has a dmsBeaconPlanRowStatus other than active. A 'criticalTemperature' alarm shall have no effect on the 'activation' of a message, it only effects the display of the active message. Thus, a message activation may occur during a 'criticalTemperature' alarm and the sign controller behaves as if the message is displayed. However, the shortErrorStatus indicates a criticalTemperature alarm and the sign face illumination is off. As soon as the DMS determines that the 'criticalTemperature' alarm is no longer present, the DMS shall display the message stored in the currentBuffer. <Parameter Type> Status <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.6.17"
    ],
    null,
    null,
    null,
    null
  ]
}