dmsActivateMessageState

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dmsActivateMessageState",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "fastActivationSign",
    "(",
    "1",
    ")",
    ",",
    "slowActivatedOK",
    "(",
    "2",
    ")",
    ",",
    "slowActivatedError",
    "(",
    "3",
    ")",
    ",",
    "slowActivating",
    "(",
    "4",
    ")",
    "}",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"<Definition> Signs that are able to reliably activate a message in less than the maximum response time should always return 'fastActivationSign(1)'. This allows a central to use this object to determine whether or not the sign does fast activation (that is, whether the sign can immediately change the display). Signs that may require more than the maximum response time to activate a message (such as a rotary drum sign) shall set this object to 'slowActivating(4)' during the changing of the display and when the message change has completed shall change it to 'slowActivatedOK(2)' if successful or 'slowActivatedError(3)' if an error occurred during the display change. A sign with fast activation uses this object only to indicate that it is a fast activation sign. Such a sign provides an immediate response to a SET of dmsActivateMessageV4 (or dmsActivateMessage). With a slow activation sign there are two opportunities to detect an error. The first comes when the SET of dmsActivateMessageV4 is performed, just as in the fast activation sign. It could be a bad message number or other error. If such an error is received, the message change does not occur and therefore this object can be ignored. If the SET of dmsActivateMessageV4 succeeds, then the central must wait for either slowActivatedOK or slowActivatedError in this object. If the sign detects an error, it shall set this object to slowActivatedError and set the 'message error' bit in the shortErrorStatus object. When a central receives slowActivatedError, it shall examine other status objects specific to the sign, such as the rotary drum status objects, to determine the precise error. <Parameter Type> Status <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.6.25\"",
    "::=",
    "{",
    "signControl",
    "25",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "fastActivationSign",
            1
          ],
          [
            "slowActivatedOK",
            2
          ],
          [
            "slowActivatedError",
            3
          ],
          [
            "slowActivating",
            4
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "<Definition> Signs that are able to reliably activate a message in less than the maximum response time should always return 'fastActivationSign(1)'. This allows a central to use this object to determine whether or not the sign does fast activation (that is, whether the sign can immediately change the display). Signs that may require more than the maximum response time to activate a message (such as a rotary drum sign) shall set this object to 'slowActivating(4)' during the changing of the display and when the message change has completed shall change it to 'slowActivatedOK(2)' if successful or 'slowActivatedError(3)' if an error occurred during the display change. A sign with fast activation uses this object only to indicate that it is a fast activation sign. Such a sign provides an immediate response to a SET of dmsActivateMessageV4 (or dmsActivateMessage). With a slow activation sign there are two opportunities to detect an error. The first comes when the SET of dmsActivateMessageV4 is performed, just as in the fast activation sign. It could be a bad message number or other error. If such an error is received, the message change does not occur and therefore this object can be ignored. If the SET of dmsActivateMessageV4 succeeds, then the central must wait for either slowActivatedOK or slowActivatedError in this object. If the sign detects an error, it shall set this object to slowActivatedError and set the 'message error' bit in the shortErrorStatus object. When a central receives slowActivatedError, it shall examine other status objects specific to the sign, such as the rotary drum status objects, to determine the precise error. <Parameter Type> Status <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.6.25"
    ],
    null,
    null,
    null,
    null
  ]
}

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dmsActivateMessageState",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "fastActivationSign",
    "(",
    "1",
    ")",
    ",",
    "slowActivatedOK",
    "(",
    "2",
    ")",
    ",",
    "slowActivatedError",
    "(",
    "3",
    ")",
    ",",
    "slowActivating",
    "(",
    "4",
    ")",
    "}",
    "ACCESS",
    "read-only",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition> Signs that are able to change their message with fast activation always return 'fastActivationSign(1)'. This allows a central to use this object to determine whether or not the sign does fast activation (that is, whether the sign can immediately change the display). Signs that do slow activation (such as a rotary drum sign) shall set this object to 'slowActivating(4)' during the changing of the display and when the message change has completed shall change it to 'slowActivatedOK(2)' if successful or 'slowActivatedError(3)' if an error occurred during the display change. A sign with fast activation uses this object only to indicate that it is a fast activation sign. Such a sign shows an immediate response to a SET of dmsActivateMessage that is either noError or a genErr. In the case of a genErr the specific error is found in dmsActivateMsgError. With a slow activation sign there are two opportunities to detect an error. The first comes when the SET of dmsActivateMessage is performed, just as in the fast activation sign. It could be a bad message number or other error. If such an error is received, it should be assumed that the message change does not occur and therefore this object can be ignored. If the SET of dmsActivateMessage succeeds, then the central must wait for either slowActivatedOK or slowActivatedError in this object. If the sign detects an error, it should set this object to slowActivatedError and set the ‘message error’ bit in the shortErrorStatus object. When a central receives slowActivatedError, it should examine other status objects specific to the sign, such as the rotary drum status objects, to determine the precise error. <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.6.25\"",
    "::=",
    "{",
    "signControl",
    "25",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "fastActivationSign",
            1
          ],
          [
            "slowActivatedOK",
            2
          ],
          [
            "slowActivatedError",
            3
          ],
          [
            "slowActivating",
            4
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition> Signs that are able to change their message with fast activation always return 'fastActivationSign(1)'. This allows a central to use this object to determine whether or not the sign does fast activation (that is, whether the sign can immediately change the display). Signs that do slow activation (such as a rotary drum sign) shall set this object to 'slowActivating(4)' during the changing of the display and when the message change has completed shall change it to 'slowActivatedOK(2)' if successful or 'slowActivatedError(3)' if an error occurred during the display change. A sign with fast activation uses this object only to indicate that it is a fast activation sign. Such a sign shows an immediate response to a SET of dmsActivateMessage that is either noError or a genErr. In the case of a genErr the specific error is found in dmsActivateMsgError. With a slow activation sign there are two opportunities to detect an error. The first comes when the SET of dmsActivateMessage is performed, just as in the fast activation sign. It could be a bad message number or other error. If such an error is received, it should be assumed that the message change does not occur and therefore this object can be ignored. If the SET of dmsActivateMessage succeeds, then the central must wait for either slowActivatedOK or slowActivatedError in this object. If the sign detects an error, it should set this object to slowActivatedError and set the ‘message error’ bit in the shortErrorStatus object. When a central receives slowActivatedError, it should examine other status objects specific to the sign, such as the rotary drum status objects, to determine the precise error. <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.6.25"
    ],
    null,
    null,
    null,
    null
  ]
}

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dmsActivateMessageState",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "fastActivationSign",
    "(",
    "1",
    ")",
    ",",
    "slowActivatedOK",
    "(",
    "2",
    ")",
    ",",
    "slowActivatedError",
    "(",
    "3",
    ")",
    ",",
    "slowActivating",
    "(",
    "4",
    ")",
    "}",
    "ACCESS",
    "read-only",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition> Signs that are able to change their message with fast activation always return 'fastActivationSign(1)'. This allows a central to use this object to determine whether or not the sign does fast activation (that is, whether the sign can immediately change the display). Signs that do slow activation (such as a rotary drum sign) shall set this object to 'slowActivating(4)' during the changing of the display and when the message change has completed shall change it to 'slowActivatedOK(2)' if successful or 'slowActivatedError(3)' if an error occurred during the display change. A sign with fast activation uses this object only to indicate that it is a fast activation sign. Such a sign shows an immediate response to a SET of dmsActivateMessage that is either noError or a genErr. In the case of a genErr the specific error is found in dmsActivateMsgError. With a slow activation sign there are two opportunities to detect an error. The first comes when the SET of dmsActivateMessage is performed, just as in the fast activation sign. It could be a bad message number or other error. If such an error is received, the message change does not occur and therefore this object can be ignored. If the SET of dmsActivateMessage succeeds, then the central must wait for either slowActivatedOK or slowActivatedError in this object. If the sign detects an error, it shall set this object to slowActivatedError and set the 'message error' bit in the shortErrorStatus object. When a central receives slowActivatedError, it shall examine other status objects specific to the sign, such as the rotary drum status objects, to determine the precise error. <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.6.25\"",
    "::=",
    "{",
    "signControl",
    "25",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "fastActivationSign",
            1
          ],
          [
            "slowActivatedOK",
            2
          ],
          [
            "slowActivatedError",
            3
          ],
          [
            "slowActivating",
            4
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition> Signs that are able to change their message with fast activation always return 'fastActivationSign(1)'. This allows a central to use this object to determine whether or not the sign does fast activation (that is, whether the sign can immediately change the display). Signs that do slow activation (such as a rotary drum sign) shall set this object to 'slowActivating(4)' during the changing of the display and when the message change has completed shall change it to 'slowActivatedOK(2)' if successful or 'slowActivatedError(3)' if an error occurred during the display change. A sign with fast activation uses this object only to indicate that it is a fast activation sign. Such a sign shows an immediate response to a SET of dmsActivateMessage that is either noError or a genErr. In the case of a genErr the specific error is found in dmsActivateMsgError. With a slow activation sign there are two opportunities to detect an error. The first comes when the SET of dmsActivateMessage is performed, just as in the fast activation sign. It could be a bad message number or other error. If such an error is received, the message change does not occur and therefore this object can be ignored. If the SET of dmsActivateMessage succeeds, then the central must wait for either slowActivatedOK or slowActivatedError in this object. If the sign detects an error, it shall set this object to slowActivatedError and set the 'message error' bit in the shortErrorStatus object. When a central receives slowActivatedError, it shall examine other status objects specific to the sign, such as the rotary drum status objects, to determine the precise error. <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.6.25"
    ],
    null,
    null,
    null,
    null
  ]
}

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dmsActivateMessageState",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "fastActivationSign",
    "(",
    "1",
    ")",
    ",",
    "slowActivatedOK",
    "(",
    "2",
    ")",
    ",",
    "slowActivatedError",
    "(",
    "3",
    ")",
    ",",
    "slowActivating",
    "(",
    "4",
    ")",
    "}",
    "ACCESS",
    "read-only",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition> Signs that are able to change their message with fast activation always return 'fastActivationSign(1)'. This allows a central to use this object to determine whether or not the sign does fast activation (that is, whether the sign can immediately change the display). Signs that do slow activation (such as a rotary drum sign) shall set this object to 'slowActivating(4)' during the changing of the display and when the message change has completed shall change it to 'slowActivatedOK(2)' if successful or 'slowActivatedError(3)' if an error occurred during the display change. A sign with fast activation uses this object only to indicate that it is a fast activation sign. Such a sign shows an immediate response to a SET of dmsActivateMessage that is either noError or a genErr. In the case of a genErr the specific error is found in dmsActivateMsgError. With a slow activation sign there are two opportunities to detect an error. The first comes when the SET of dmsActivateMessage is performed, just as in the fast activation sign. It could be a bad message number or other error. If such an error is received, the message change does not occur and therefore this object can be ignored. If the SET of dmsActivateMessage succeeds, then the central must wait for either slowActivatedOK or slowActivatedError in this object. If the sign detects an error, it shall set this object to slowActivatedError and set the ‘message error’ bit in the shortErrorStatus object. When a central receives slowActivatedError, it shall examine other status objects specific to the sign, such as the rotary drum status objects, to determine the precise error. <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.6.25\"",
    "::=",
    "{",
    "signControl",
    "25",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "fastActivationSign",
            1
          ],
          [
            "slowActivatedOK",
            2
          ],
          [
            "slowActivatedError",
            3
          ],
          [
            "slowActivating",
            4
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition> Signs that are able to change their message with fast activation always return 'fastActivationSign(1)'. This allows a central to use this object to determine whether or not the sign does fast activation (that is, whether the sign can immediately change the display). Signs that do slow activation (such as a rotary drum sign) shall set this object to 'slowActivating(4)' during the changing of the display and when the message change has completed shall change it to 'slowActivatedOK(2)' if successful or 'slowActivatedError(3)' if an error occurred during the display change. A sign with fast activation uses this object only to indicate that it is a fast activation sign. Such a sign shows an immediate response to a SET of dmsActivateMessage that is either noError or a genErr. In the case of a genErr the specific error is found in dmsActivateMsgError. With a slow activation sign there are two opportunities to detect an error. The first comes when the SET of dmsActivateMessage is performed, just as in the fast activation sign. It could be a bad message number or other error. If such an error is received, the message change does not occur and therefore this object can be ignored. If the SET of dmsActivateMessage succeeds, then the central must wait for either slowActivatedOK or slowActivatedError in this object. If the sign detects an error, it shall set this object to slowActivatedError and set the ‘message error’ bit in the shortErrorStatus object. When a central receives slowActivatedError, it shall examine other status objects specific to the sign, such as the rotary drum status objects, to determine the precise error. <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.6.25"
    ],
    null,
    null,
    null,
    null
  ]
}