<Definition> A code indicating the active message or message to be activated. The value of this object may be SET by a management station or modified by logic internal to the DMS (e.g., activation of the end duration message, etc.). When modified by internal logic with a reference to a message ID code, the duration indicates 65535 (infinite) and the activate priority indicates 255. If a GET is performed on this object, the DMS shall respond with the value for the last message that was successfully activated. Upon any attempt to update the value of this object, whether from an internal or external source, the following objects shall be updated appropriately: - dmsActivateMsgError, - dmsActivateErrorMsgCodeV4, - dmsMultiSyntaxError, - dmsMultiSyntaxErrorPosition (if supported), - dmsMultiOtherErrorDescription (if supported), - dmsDrumStatus (if supported) If a message activation error occurs (e.g., dmsActivateMsgError is updated to a value other than 'none'), the new message shall not be activated and, if the activation request originated from a SET request, the appropriate error code (NTCIP 1203 v04, Clause 4.3.5) shall be returned. A management station should then GET the dmsActivateMsgError object as soon as possible to minimize the chance of additional activation attempts from overwriting the dmsActivateMsgError. A 'criticalTemperature' alarm shall have no effect on the 'activation' of a message, it will only affect the display of the active message. Thus, a message activation may occur during a 'criticalTemperature' alarm and the sign controller will behave as if the message is displayed. However, the shortErrorStatus will indicate a criticalTemperature alarm and the sign face illumination will be 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> Control <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.6.26
OID reference
dmsActivateMessageV4
1.3.6.1.4.1.1206.4.2.6.6.26
Description
<Definition> A code indicating the active message or message to be activated. The value of this object may be SET by a management station or modified by logic internal to the DMS (e.g., activation of the end duration message, etc.). When modified by internal logic with a reference to a message ID code, the duration in…
Identification
Identifier and names
- Parent
- 1.3.6.1.4.1.1206.4.2.6.6 (signControl)
- Node code
- 26
- Node name
- dmsActivateMessageV4
- Category
- SNMP management object
- Numeric OID
- 1.3.6.1.4.1.1206.4.2.6.6.26
- URN notation
- urn:oid:1.3.6.1.4.1.1206.4.2.6.6.26
ASN.1, OID-IRI and named path variants
- ASN.1 notation
-
{1 3 6 1 4 1 1206 4 2 6 6 26}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) global(6) signControl(6) dmsActivateMessageV4(26)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dms(6) signControl(6) dmsActivateMessageV4(26)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) global(6) signControl(6) dmsActivateMessageV4(26)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dms(6) signControl(6) dmsActivateMessageV4(26)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) global(6) signControl(6) dmsActivateMessageV4(26)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) dms(6) signControl(6) dmsActivateMessageV4(26)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) global(6) signControl(6) dmsActivateMessageV4(26)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) dms(6) signControl(6) dmsActivateMessageV4(26)}
- {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) global(6) signControl(6) dmsActivateMessageV4(26)}
- {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dms(6) signControl(6) dmsActivateMessageV4(26)}
- {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) global(6) signControl(6) dmsActivateMessageV4(26)}
- {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dms(6) signControl(6) dmsActivateMessageV4(26)}
- {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) global(6) signControl(6) dmsActivateMessageV4(26)}
- {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) dms(6) signControl(6) dmsActivateMessageV4(26)}
- {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) global(6) signControl(6) dmsActivateMessageV4(26)}
- {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) dms(6) signControl(6) dmsActivateMessageV4(26)}
- Additional combinations skipped.
- OID-IRI notation
- /1/3/6/1/4/1/1206/4/2/6/6/26
- /ISO/Identified-Organization/6/1/4/1/1206/4/2/6/6/26
- /ISO/3/6/1/4/1/1206/4/2/6/6/26
- Named path variants
- /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/global/signControl/dmsActivateMessageV4
- /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/dms/signControl/dmsActivateMessageV4
- /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/global/signControl/dmsActivateMessageV4
- /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/dms/signControl/dmsActivateMessageV4
- /iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/global/signControl/dmsActivateMessageV4
- /iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/dms/signControl/dmsActivateMessageV4
- /iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/global/signControl/dmsActivateMessageV4
- /iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/dms/signControl/dmsActivateMessageV4
- /iso/identified-organization/dod/internet/private/ldap-enterprise/1206/transportation/devices/global/signControl/dmsActivateMessageV4
- /iso/identified-organization/dod/internet/private/ldap-enterprise/1206/transportation/devices/dms/signControl/dmsActivateMessageV4
- /iso/identified-organization/dod/internet/private/ldap-enterprise/nema/transportation/devices/global/signControl/dmsActivateMessageV4
- /iso/identified-organization/dod/internet/private/ldap-enterprise/nema/transportation/devices/dms/signControl/dmsActivateMessageV4
- /iso/identified-organization/dod/internet/private/vendor-objects/1206/transportation/devices/global/signControl/dmsActivateMessageV4
- /iso/identified-organization/dod/internet/private/vendor-objects/1206/transportation/devices/dms/signControl/dmsActivateMessageV4
- /iso/identified-organization/dod/internet/private/vendor-objects/nema/transportation/devices/global/signControl/dmsActivateMessageV4
- /iso/identified-organization/dod/internet/private/vendor-objects/nema/transportation/devices/dms/signControl/dmsActivateMessageV4
- Additional combinations skipped.
SNMP properties
- Value type
- MessageActivationCodeV4
- Maximum access defined by MIB
- read-write
- Status in MIB
- current
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.
dmsActivateMessageV4 OBJECT-TYPE
SYNTAX MessageActivationCodeV4
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"<Definition> A code indicating the active message or message to be
activated. The value of this object may be SET by a management station or
modified by logic internal to the DMS (e.g., activation of the end duration
message, etc.).
When modified by internal logic with a reference to a message ID code, the
duration indicates 65535 (infinite) and the activate priority indicates 255.
If a GET is performed on this object, the DMS shall respond with the value
for the last message that was successfully activated.
Upon any attempt to update the value of this object, whether from an internal
or external source, the following objects shall be updated appropriately:
- dmsActivateMsgError,
- dmsActivateErrorMsgCodeV4,
- dmsMultiSyntaxError,
- dmsMultiSyntaxErrorPosition (if supported),
- dmsMultiOtherErrorDescription (if supported),
- dmsDrumStatus (if supported)
If a message activation error occurs (e.g., dmsActivateMsgError is updated to
a value other than 'none'), the new message shall not be activated and, if
the activation request originated from a SET request, the appropriate error
code (NTCIP 1203 v04, Clause 4.3.5) shall be returned. A management station
should then GET the dmsActivateMsgError object as soon as possible to
minimize the chance of additional activation attempts from overwriting the
dmsActivateMsgError.
A 'criticalTemperature' alarm shall have no effect on the 'activation' of a
message, it will only affect the display of the active message. Thus, a
message activation may occur during a 'criticalTemperature' alarm and the
sign controller will behave as if the message is displayed. However, the
shortErrorStatus will indicate a criticalTemperature alarm and the sign face
illumination will be 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> Control
<Object Identifier> 1.3.6.1.4.1.1206.4.2.3.6.26"
::= { signControl 26 }
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
dmsActivateMessageV4 · unconfirmedITE public NTCIP working repository MIBs
Status in source: unconfirmed.
Names: dmsActivateMessageV4
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"dmsActivateMessageV4",
"OBJECT-TYPE",
"SYNTAX",
"MessageActivationCodeV4",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"<Definition> A code indicating the active message or message to be activated. The value of this object may be SET by a management station or modified by logic internal to the DMS (e.g., activation of the end duration message, etc.). When modified by internal logic with a reference to a message ID code, the duration indicates 65535 (infinite) and the activate priority indicates 255. If a GET is performed on this object, the DMS shall respond with the value for the last message that was successfully activated. Upon any attempt to update the value of this object, whether from an internal or external source, the following objects shall be updated appropriately: - dmsActivateMsgError, - dmsActivateErrorMsgCodeV4, - dmsMultiSyntaxError, - dmsMultiSyntaxErrorPosition (if supported), - dmsMultiOtherErrorDescription (if supported), - dmsDrumStatus (if supported) If a message activation error occurs (e.g., dmsActivateMsgError is updated to a value other than 'none'), the new message shall not be activated and, if the activation request originated from a SET request, the appropriate error code (NTCIP 1203 v04, Clause 4.3.5) shall be returned. A management station should then GET the dmsActivateMsgError object as soon as possible to minimize the chance of additional activation attempts from overwriting the dmsActivateMsgError. A 'criticalTemperature' alarm shall have no effect on the 'activation' of a message, it will only affect the display of the active message. Thus, a message activation may occur during a 'criticalTemperature' alarm and the sign controller will behave as if the message is displayed. However, the shortErrorStatus will indicate a criticalTemperature alarm and the sign face illumination will be 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> Control <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.6.26\"",
"::=",
"{",
"signControl",
"26",
"}"
],
"syntax_tree": [
[
"row",
"MessageActivationCodeV4"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"<Definition> A code indicating the active message or message to be activated. The value of this object may be SET by a management station or modified by logic internal to the DMS (e.g., activation of the end duration message, etc.). When modified by internal logic with a reference to a message ID code, the duration indicates 65535 (infinite) and the activate priority indicates 255. If a GET is performed on this object, the DMS shall respond with the value for the last message that was successfully activated. Upon any attempt to update the value of this object, whether from an internal or external source, the following objects shall be updated appropriately: - dmsActivateMsgError, - dmsActivateErrorMsgCodeV4, - dmsMultiSyntaxError, - dmsMultiSyntaxErrorPosition (if supported), - dmsMultiOtherErrorDescription (if supported), - dmsDrumStatus (if supported) If a message activation error occurs (e.g., dmsActivateMsgError is updated to a value other than 'none'), the new message shall not be activated and, if the activation request originated from a SET request, the appropriate error code (NTCIP 1203 v04, Clause 4.3.5) shall be returned. A management station should then GET the dmsActivateMsgError object as soon as possible to minimize the chance of additional activation attempts from overwriting the dmsActivateMsgError. A 'criticalTemperature' alarm shall have no effect on the 'activation' of a message, it will only affect the display of the active message. Thus, a message activation may occur during a 'criticalTemperature' alarm and the sign controller will behave as if the message is displayed. However, the shortErrorStatus will indicate a criticalTemperature alarm and the sign face illumination will be 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> Control <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.6.26"
],
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.26, but its DESCRIPTION explicitly lists 1.3.6.1.4.1.1206.4.2.3.6.26. 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