<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
OID reference
dmsActivateMessageState
1.3.6.1.4.1.1206.4.2.6.6.25
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 t…
Identification
Identifier and names
- Parent
- 1.3.6.1.4.1.1206.4.2.6.6 (signControl)
- Node code
- 25
- Node name
- dmsActivateMessageState
- Category
- SNMP management object
- Numeric OID
- 1.3.6.1.4.1.1206.4.2.6.6.25
- URN notation
- urn:oid:1.3.6.1.4.1.1206.4.2.6.6.25
ASN.1, OID-IRI and named path variants
- ASN.1 notation
-
{1 3 6 1 4 1 1206 4 2 6 6 25}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) global(6) signControl(6) dmsActivateMessageState(25)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dms(6) signControl(6) dmsActivateMessageState(25)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) global(6) signControl(6) dmsActivateMessageState(25)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dms(6) signControl(6) dmsActivateMessageState(25)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) global(6) signControl(6) dmsActivateMessageState(25)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) dms(6) signControl(6) dmsActivateMessageState(25)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) global(6) signControl(6) dmsActivateMessageState(25)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) dms(6) signControl(6) dmsActivateMessageState(25)}
- {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) global(6) signControl(6) dmsActivateMessageState(25)}
- {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dms(6) signControl(6) dmsActivateMessageState(25)}
- {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) global(6) signControl(6) dmsActivateMessageState(25)}
- {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dms(6) signControl(6) dmsActivateMessageState(25)}
- {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) global(6) signControl(6) dmsActivateMessageState(25)}
- {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) dms(6) signControl(6) dmsActivateMessageState(25)}
- {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) global(6) signControl(6) dmsActivateMessageState(25)}
- {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) dms(6) signControl(6) dmsActivateMessageState(25)}
- Additional combinations skipped.
- OID-IRI notation
- /1/3/6/1/4/1/1206/4/2/6/6/25
- /ISO/Identified-Organization/6/1/4/1/1206/4/2/6/6/25
- /ISO/3/6/1/4/1/1206/4/2/6/6/25
- Named path variants
- /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/global/signControl/dmsActivateMessageState
- /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/dms/signControl/dmsActivateMessageState
- /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/global/signControl/dmsActivateMessageState
- /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/dms/signControl/dmsActivateMessageState
- /iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/global/signControl/dmsActivateMessageState
- /iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/dms/signControl/dmsActivateMessageState
- /iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/global/signControl/dmsActivateMessageState
- /iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/dms/signControl/dmsActivateMessageState
- /iso/identified-organization/dod/internet/private/ldap-enterprise/1206/transportation/devices/global/signControl/dmsActivateMessageState
- /iso/identified-organization/dod/internet/private/ldap-enterprise/1206/transportation/devices/dms/signControl/dmsActivateMessageState
- /iso/identified-organization/dod/internet/private/ldap-enterprise/nema/transportation/devices/global/signControl/dmsActivateMessageState
- /iso/identified-organization/dod/internet/private/ldap-enterprise/nema/transportation/devices/dms/signControl/dmsActivateMessageState
- /iso/identified-organization/dod/internet/private/vendor-objects/1206/transportation/devices/global/signControl/dmsActivateMessageState
- /iso/identified-organization/dod/internet/private/vendor-objects/1206/transportation/devices/dms/signControl/dmsActivateMessageState
- /iso/identified-organization/dod/internet/private/vendor-objects/nema/transportation/devices/global/signControl/dmsActivateMessageState
- /iso/identified-organization/dod/internet/private/vendor-objects/nema/transportation/devices/dms/signControl/dmsActivateMessageState
- Additional combinations skipped.
SNMP properties
- Value type
- INTEGER
- Maximum access defined by MIB
- read-only
- Status in MIB
- current
Enumerated values
| Value | Name |
|---|---|
| 1 | fastActivationSign |
| 2 | slowActivatedOK |
| 3 | slowActivatedError |
| 4 | slowActivating |
Using this OID with SNMP
At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.
snmpget [connection options] DEVICE .1.3.6.1.4.1.1206.4.2.6.6.25.0
Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.
Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.
Published definition
The displayed source records contain one distinct definition. Compare its source records.
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 }
Meaning
Descriptions
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Evidence
Source records
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Records for description 1ITE public NTCIP working repository MIBs
dmsActivateMessageState · unconfirmedITE public NTCIP working repository MIBs
Status in source: unconfirmed.
Names: dmsActivateMessageState
Technical details
{
"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
]
}- ITE public NTCIP working repository MIBs
· Publisher's source file: NTCIP-1203 — NTCIP1203-Dms.mib
Module: NTCIP1203-Dms
See published definition above
Module imports
{'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'DisplayString', 'StorageType', 'RowStatus'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'Unsigned32', 'Counter32', 'IpAddress'], 'SNMPv2-CONF': ['OBJECT-GROUP'], 'ISO26048-1-Srsa': ['fdSrsaTypeCode', 'fdSrsaPortIndex'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString'], 'ISO26048-1-Global-TC': ['ITSDirection', 'ITSInteger8', 'ITSLatitude84', 'ITSLongitude84', 'ITSBitmap'], 'TRANSPORT-ADDRESS-MIB': ['TransportAddressType', 'TransportAddress'], 'NTCIP8004-Transportation': ['NtcipOwnerString', 'NtcipIntegerBitmap8', 'NtcipIntegerBitmap16', 'NtcipTwoColors', 'devices']}Source data warning: This original is published in an ITE NTCIP working repository. Repository publication does not establish that this particular revision is an adopted standard. Consult its native revision history and the NTCIP published standards catalog before implementation. Copyright and distribution notices are retained in the downloadable original.
Source data warning: Published module-root disagreement: dms has an SMI assignment resolving to 1.3.6.1.4.1.1206.4.2.6, while its DESCRIPTION explicitly prints 1.3.6.1.4.1.1206.4.2.3. All dependent assignments from this module require verification. No root number has been silently corrected.
Source data warning: Published source disagreement: this literal SMI assignment resolves to 1.3.6.1.4.1.1206.4.2.6.6.25, but its DESCRIPTION explicitly lists 1.3.6.1.4.1.1206.4.2.3.6.25. Both published numeric claims are retained as unconfirmed evidence. Neither value is presented as a verified correction or an independently confirmed registration; consult the original file and the applicable standard edition.
· Download NTCIP-1203 — NTCIP1203-Dms.mib
Registration