OID reference
1.3.6.1.4.1.1206.4.2.9.1.32
The time expressed in 1000th of a second (milliseconds). This object is only used when a higher resolution than 1 sec is required for a vehicle time tag. This value is used in conjunction with the ‘controller-localTime’ object in that this counter rolls over every second. The DCM device shall record this value with it…
Identification
{1 3 6 1 4 1 1206 4 2 9 1 32}
At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.
A query example is omitted because the source variants do not establish compatible read access.
Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.
The displayed source records contain one distinct definition. Compare its source records.
dcmVehicleTimeTag1000 OBJECT-TYPE
SYNTAX INTEGER (0..999)
ACCESS not-accessible
STATUS optional
DESCRIPTION
"The time expressed in 1000th of a second (milliseconds). This object is only
used when a higher resolution than 1 sec is required for a vehicle time tag.
This value is used in conjunction with the ‘controller-localTime’ object in
that this counter rolls over every second. The DCM device shall record this
value with its highest resolution which may be less than 100th of a second."
::= {dcmVehCriteria 32}
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
The time expressed in 1000th of a second (milliseconds). This object is only used when a higher resolution than 1 sec is required for a vehicle time tag. This value is used in conjunction with the ‘controller-localTime’ object in that this counter rolls over every second. The DCM device shall record this value with its highest resolution which may be less than 100th of a second.
NTCIP published standard MIB annexes (reviewed modules)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: optional.
Names: dcmVehicleTimeTag1000
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"dcmVehicleTimeTag1000",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"(",
"0",
".",
".",
"999",
")",
"ACCESS",
"not-accessible",
"STATUS",
"optional",
"DESCRIPTION",
"\"The time expressed in 1000th of a second (milliseconds). This object is only used when a higher resolution than 1 sec is required for a vehicle time tag. This value is used in conjunction with the ‘controller-localTime’ object in that this counter rolls over every second. The DCM device shall record this value with its highest resolution which may be less than 100th of a second.\"",
"::=",
"{",
"dcmVehCriteria",
"32",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"integerSubType",
[
[
0,
999
]
]
]
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"optional"
],
[
"DESCRIPTION",
"The time expressed in 1000th of a second (milliseconds). This object is only used when a higher resolution than 1 sec is required for a vehicle time tag. This value is used in conjunction with the ‘controller-localTime’ object in that this counter rolls over every second. The DCM device shall record this value with its highest resolution which may be less than 100th of a second."
],
null,
null,
null,
null
]
}Module: DCM-MIB1
See published definition above
{'TMIB-II': ['devices'], 'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['Counter']}Source data warning: Recovered from a file whose complete MIB does not parse. The original assignment and definition are preserved. Registration and implementation details may be inaccurate; consult the original file. Other damaged or unresolved declarations are not established registrations.
Source data warning: This record is transcribed from a published NTCIP MIB annex. The downloadable text is a derived transcription with page furniture and section headings masked; the unmodified original PDF is authoritative. Native definitions, DESCRIPTION and STATUS are retained. A published object definition does not establish support by any particular device.
Source data warning: A typographic closing DESCRIPTION quotation delimiter occurs immediately at a native SMI field boundary. Normalize this delimiter only in the derived transcription; retain the literal published definition, full description and unchanged numeric assignments.
Source data warning: A typographic closing quotation mark terminates a DESCRIPTION in this PDF. Normalize that delimiter only in the derived MIB transcription; preserve the literal published definition and unmodified PDF. No numeric assignment changes.
Source data warning: A typographic opening DESCRIPTION quotation delimiter occurs immediately at a native SMI field boundary. Normalize this delimiter only in the derived transcription; retain the literal published definition, full description and unchanged numeric assignments.
Source data warning: Potentially inaccurate interpretation of historical NTCIP namespace references: TMIB-II. These exact source files require the reviewed bindings shown below. The numeric roots used here are the explicit assignments in normative Annex A.2 of published NTCIP 8004 v02 (2010), physical pages 43–44. This does not establish that every historical module revision is identical. The annex also prints enterprise instead of RFC 1155 enterprises and declares Protocols while referencing protocols; those spelling interpretations are disclosed. The original IMPORTS, numeric suffixes and definitions remain unchanged. Verify both originals before implementation.
· Download NTCIP1206v0123f.pdf — DCM-MIB1 (MIB transcription)Related source files and packages:
Module: DCM-MIB1
{'TMIB-II': ['devices'], 'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['Counter']}Source data warning: Recovered from a file whose complete MIB does not parse. The original assignment and definition are preserved. Registration and implementation details may be inaccurate; consult the original file. Other damaged or unresolved declarations are not established registrations.
Source data warning: This record is transcribed from a published NTCIP MIB annex. The downloadable text is a derived transcription with page furniture and section headings masked; the unmodified original PDF is authoritative. Native definitions, DESCRIPTION and STATUS are retained. A published object definition does not establish support by any particular device.
Source data warning: A typographic closing DESCRIPTION quotation delimiter occurs immediately at a native SMI field boundary. Normalize this delimiter only in the derived transcription; retain the literal published definition, full description and unchanged numeric assignments.
Source data warning: A typographic closing quotation mark terminates a DESCRIPTION in this PDF. Normalize that delimiter only in the derived MIB transcription; preserve the literal published definition and unmodified PDF. No numeric assignment changes.
Source data warning: A typographic opening DESCRIPTION quotation delimiter occurs immediately at a native SMI field boundary. Normalize this delimiter only in the derived transcription; retain the literal published definition, full description and unchanged numeric assignments.
Source data warning: Potentially inaccurate interpretation of historical NTCIP namespace references: TMIB-II. These exact source files require the reviewed bindings shown below. The numeric roots used here are the explicit assignments in normative Annex A.2 of published NTCIP 8004 v02 (2010), physical pages 43–44. This does not establish that every historical module revision is identical. The annex also prints enterprise instead of RFC 1155 enterprises and declares Protocols while referencing protocols; those spelling interpretations are disclosed. The original IMPORTS, numeric suffixes and definitions remain unchanged. Verify both originals before implementation.
· Download NTCIP1206v0123f-1.pdf — DCM-MIB1 (MIB transcription)Registration