<Definition> Defines the maximum time (inclusive), in minutes, between successive Application Layer messages that can occur before a communication loss is assumed. If this object is set to zero (0), communications loss shall be ignored. The countdown timer associated with this parameter shall be suspended while the sign control parameter has a value of 'local (2)', e.g., the sign is in local control. The countdown timer shall be restarted (reset and started again) once the sign control parameter value is switched to 'central (4)' or 'centralOverride (5)'. <Informative> This timer differs from the Data Link Layer timers (T1 to T4). A dial-up circuit may have short time-outs at the DL Layer, but central might only dial up once a month to confirm operation, in which case this object would be set to ~ 35 days. <Parameter Type> Configuration <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.6.13
OID reference
dmsTimeCommLoss
1.3.6.1.4.1.1206.4.2.6.6.13
Description
<Definition> Defines the maximum time (inclusive), in minutes, between successive Application Layer messages that can occur before a communication loss is assumed. If this object is set to zero (0), communications loss shall be ignored. The countdown timer associated with this parameter shall be suspended while the si…
Identification
Identifier and names
- Parent
- 1.3.6.1.4.1.1206.4.2.6.6 (signControl)
- Node code
- 13
- Node name
- dmsTimeCommLoss
- Category
- SNMP management object
- Numeric OID
- 1.3.6.1.4.1.1206.4.2.6.6.13
- URN notation
- urn:oid:1.3.6.1.4.1.1206.4.2.6.6.13
ASN.1, OID-IRI and named path variants
- ASN.1 notation
-
{1 3 6 1 4 1 1206 4 2 6 6 13}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) global(6) signControl(6) dmsTimeCommLoss(13)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dms(6) signControl(6) dmsTimeCommLoss(13)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) global(6) signControl(6) dmsTimeCommLoss(13)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dms(6) signControl(6) dmsTimeCommLoss(13)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) global(6) signControl(6) dmsTimeCommLoss(13)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) dms(6) signControl(6) dmsTimeCommLoss(13)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) global(6) signControl(6) dmsTimeCommLoss(13)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) dms(6) signControl(6) dmsTimeCommLoss(13)}
- {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) global(6) signControl(6) dmsTimeCommLoss(13)}
- {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dms(6) signControl(6) dmsTimeCommLoss(13)}
- {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) global(6) signControl(6) dmsTimeCommLoss(13)}
- {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dms(6) signControl(6) dmsTimeCommLoss(13)}
- {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) global(6) signControl(6) dmsTimeCommLoss(13)}
- {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) dms(6) signControl(6) dmsTimeCommLoss(13)}
- {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) global(6) signControl(6) dmsTimeCommLoss(13)}
- {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) dms(6) signControl(6) dmsTimeCommLoss(13)}
- Additional combinations skipped.
- OID-IRI notation
- /1/3/6/1/4/1/1206/4/2/6/6/13
- /ISO/Identified-Organization/6/1/4/1/1206/4/2/6/6/13
- /ISO/3/6/1/4/1/1206/4/2/6/6/13
- Named path variants
- /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/global/signControl/dmsTimeCommLoss
- /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/dms/signControl/dmsTimeCommLoss
- /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/global/signControl/dmsTimeCommLoss
- /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/dms/signControl/dmsTimeCommLoss
- /iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/global/signControl/dmsTimeCommLoss
- /iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/dms/signControl/dmsTimeCommLoss
- /iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/global/signControl/dmsTimeCommLoss
- /iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/dms/signControl/dmsTimeCommLoss
- /iso/identified-organization/dod/internet/private/ldap-enterprise/1206/transportation/devices/global/signControl/dmsTimeCommLoss
- /iso/identified-organization/dod/internet/private/ldap-enterprise/1206/transportation/devices/dms/signControl/dmsTimeCommLoss
- /iso/identified-organization/dod/internet/private/ldap-enterprise/nema/transportation/devices/global/signControl/dmsTimeCommLoss
- /iso/identified-organization/dod/internet/private/ldap-enterprise/nema/transportation/devices/dms/signControl/dmsTimeCommLoss
- /iso/identified-organization/dod/internet/private/vendor-objects/1206/transportation/devices/global/signControl/dmsTimeCommLoss
- /iso/identified-organization/dod/internet/private/vendor-objects/1206/transportation/devices/dms/signControl/dmsTimeCommLoss
- /iso/identified-organization/dod/internet/private/vendor-objects/nema/transportation/devices/global/signControl/dmsTimeCommLoss
- /iso/identified-organization/dod/internet/private/vendor-objects/nema/transportation/devices/dms/signControl/dmsTimeCommLoss
- Additional combinations skipped.
SNMP properties
- Value type
- Integer32
- Units
- minutes
- Maximum access defined by MIB
- read-write
- Status in MIB
- current
- Allowed ranges
- 0–65535
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.13.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.
dmsTimeCommLoss OBJECT-TYPE
SYNTAX Integer32 (0..65535)
UNITS "minutes"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"<Definition> Defines the maximum time (inclusive), in minutes, between
successive Application Layer messages that can occur before a communication
loss is assumed. If this object is set to zero (0), communications loss shall
be ignored.
The countdown timer associated with this parameter shall be suspended while
the sign control parameter has a value of 'local (2)', e.g., the sign is in
local control. The countdown timer shall be restarted (reset and started
again) once the sign control parameter value is switched to 'central (4)' or
'centralOverride (5)'.
<Informative> This timer differs from the Data Link Layer timers (T1 to T4).
A dial-up circuit may have short time-outs at the DL Layer, but central might
only dial up once a month to confirm operation, in which case this object
would be set to ~ 35 days.
<Parameter Type> Configuration
<Object Identifier> 1.3.6.1.4.1.1206.4.2.3.6.13"::= { signControl 13 }
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
dmsTimeCommLoss · unconfirmedITE public NTCIP working repository MIBs
Status in source: unconfirmed.
Names: dmsTimeCommLoss
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"dmsTimeCommLoss",
"OBJECT-TYPE",
"SYNTAX",
"Integer32",
"(",
"0",
".",
".",
"65535",
")",
"UNITS",
[
"literal",
"226d696e7574657322"
],
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"<Definition> Defines the maximum time (inclusive), in minutes, between successive Application Layer messages that can occur before a communication loss is assumed. If this object is set to zero (0), communications loss shall be ignored. The countdown timer associated with this parameter shall be suspended while the sign control parameter has a value of 'local (2)', e.g., the sign is in local control. The countdown timer shall be restarted (reset and started again) once the sign control parameter value is switched to 'central (4)' or 'centralOverride (5)'. <Informative> This timer differs from the Data Link Layer timers (T1 to T4). A dial-up circuit may have short time-outs at the DL Layer, but central might only dial up once a month to confirm operation, in which case this object would be set to ~ 35 days. <Parameter Type> Configuration <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.6.13\"",
"::=",
"{",
"signControl",
"13",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"Integer32",
[
"integerSubType",
[
[
0,
65535
]
]
]
],
[
"UNITS",
"minutes"
],
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"<Definition> Defines the maximum time (inclusive), in minutes, between successive Application Layer messages that can occur before a communication loss is assumed. If this object is set to zero (0), communications loss shall be ignored. The countdown timer associated with this parameter shall be suspended while the sign control parameter has a value of 'local (2)', e.g., the sign is in local control. The countdown timer shall be restarted (reset and started again) once the sign control parameter value is switched to 'central (4)' or 'centralOverride (5)'. <Informative> This timer differs from the Data Link Layer timers (T1 to T4). A dial-up circuit may have short time-outs at the DL Layer, but central might only dial up once a month to confirm operation, in which case this object would be set to ~ 35 days. <Parameter Type> Configuration <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.6.13"
],
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.13, but its DESCRIPTION explicitly lists 1.3.6.1.4.1.1206.4.2.3.6.13. 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
Registration authorities
First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1206)
Siblings (30)
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.1206.4.2.6.6.1 | dmsControlMode | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.6.2 | dmsSWReset | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.6.3 | dmsActivateMessage | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.6.4 | dmsMessageTimeRemaining | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.6.5 | dmsMsgTableSource | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.6.6 | dmsMsgRequesterID | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.6.7 | dmsMsgSourceMode | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.6.8 | dmsShortPowerRecoveryMessage | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.6.9 | dmsLongPowerRecoveryMessage | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.6.10 | dmsShortPowerLossTime | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.6.11 | dmsResetMessage | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.6.12 | dmsCommunicationsLossMessage | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.6.14 | dmsPowerLossMessage | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.6.15 | dmsEndDurationMessage | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.6.16 | dmsMemoryMgmt | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.6.17 | dmsActivateMsgError | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.6.18 | dmsMultiSyntaxError | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.6.19 | dmsMultiSyntaxErrorPosition | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.6.20 | dmsMultiOtherErrorDescription | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.6.21 | vmsPixelServiceDuration | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.6.22 | vmsPixelServiceFrequency | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.6.23 | vmsPixelServiceTime | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.6.24 | dmsActivateErrorMsgCode | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.6.25 | dmsActivateMessageState | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.6.26 | dmsActivateMessageV4 | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.6.27 | dmsActivateErrorMsgCodeV4 | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.6.28 | dmsMsgRequesterAddressType | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.6.29 | dmsMsgRequesterAddress | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.6.30 | dmsMsgRequesterSecurityName | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.6.31 | vmsPixelServiceDurationV4 | 0 | 0 |