OID reference
1.3.6.1.4.1.1206.4.2.1.2.2.1.18
<Definition> This parameter allows the user to set the spacing, in 0.01 meters, between paired detectors for use in calculating vehicle speeds. This parameter is measured from the leading edge of one detector to the leading edge of the paired detector. A value of 0 indicates there is no paired detector. <Object Identi…
Identification
{1 3 6 1 4 1 1206 4 2 1 2 2 1 18}
At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition.
In NTCIP1202-v03, the row index vehicleDetectorNumber is declared as INTEGER. A non-negative index value is encoded as one numeric subidentifier. An instance has the form .1.3.6.1.4.1.1206.4.2.1.2.2.1.18.<vehicleDetectorNumber>. Use an index value actually present on the device and permitted by its MIB. Other definitions can differ.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.1206.4.2.1.2.2.1.18
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.
Available source records contain 2 distinct definitions; some records may not include a definition.
vehicleDetectorPairedDetectorSpacing OBJECT-TYPE
SYNTAX INTEGER (0..65535)
ACCESS read-write
STATUS mandatory
DESCRIPTION "<Definition> This parameter allows the user to set the
spacing, in 0.01 meters, between paired detectors for use in
calculating vehicle speeds. This parameter is measured from the
leading edge of one detector to the leading edge of the paired
detector. A value of 0 indicates there is no paired detector.
<Object Identifier> 1.3.6.1.4.1.1206.4.2.1.2.2.1.18
<unit> one-hundredth of a meter"
DEFVAL { 0 }
::= { vehicleDetectorEntry 18 }vehicleDetectorPairedDetectorSpacing OBJECT-TYPE
SYNTAX INTEGER (0..65535)
ACCESS read-write
STATUS mandatory
DESCRIPTION "<Definition> This parameter allows the user to set the
spacing, in 0.01 meters, between paired detectors for use in
calculating vehicle speeds. This parameter is measured from the
leading edge of one detector to the leading edge of the paired
detector. A value of 0 indicates there is no paired detector.
<Object Identifier> 1.3.6.1.4.1.1206.4.2.1.2.2.1.18
<Object Type> P
<Unit> one-hundredth of a meter"
DEFVAL { 0 }
::= { vehicleDetectorEntry 18 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Description 1
<Definition> This parameter allows the user to set the spacing, in 0.01 meters, between paired detectors for use in calculating vehicle speeds. This parameter is measured from the leading edge of one detector to the leading edge of the paired detector. A value of 0 indicates there is no paired detector. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.2.2.1.18 <unit> one-hundredth of a meter
NTCIP published standard MIB annexes (reviewed modules)
Description 2
<Definition> This parameter allows the user to set the spacing, in 0.01 meters, between paired detectors for use in calculating vehicle speeds. This parameter is measured from the leading edge of one detector to the leading edge of the paired detector. A value of 0 indicates there is no paired detector. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.2.2.1.18 <Object Type> P <Unit> one-hundredth of a meter
NTCIP published standard MIB annexes (reviewed modules)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: mandatory.
Names: vehicleDetectorPairedDetectorSpacing
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"vehicleDetectorPairedDetectorSpacing",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"(",
"0",
".",
".",
"65535",
")",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"<Definition> This parameter allows the user to set the spacing, in 0.01 meters, between paired detectors for use in calculating vehicle speeds. This parameter is measured from the leading edge of one detector to the leading edge of the paired detector. A value of 0 indicates there is no paired detector. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.2.2.1.18 <unit> one-hundredth of a meter\"",
"DEFVAL",
"{",
"0",
"}",
"::=",
"{",
"vehicleDetectorEntry",
"18",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"integerSubType",
[
[
0,
65535
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"<Definition> This parameter allows the user to set the spacing, in 0.01 meters, between paired detectors for use in calculating vehicle speeds. This parameter is measured from the leading edge of one detector to the leading edge of the paired detector. A value of 0 indicates there is no paired detector. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.2.2.1.18 <unit> one-hundredth of a meter"
],
null,
null,
null,
[
"DEFVAL",
0
]
]
}Module: NTCIP1202-v03
See published definition above
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['IpAddress', 'Counter', 'null'], 'RFC1213-MIB': ['DisplayString', 'ifIndex'], 'NTCIP8004v02': ['OwnerString', 'OerString', 'devices']}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: Potentially inaccurate interpretation of historical NTCIP namespace references: NTCIP8004v02. 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 NTCIP-1202v0328A.pdf — NTCIP1202-v03 (MIB transcription)Related source files and packages:
Status in source: mandatory.
Names: vehicleDetectorPairedDetectorSpacing
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"vehicleDetectorPairedDetectorSpacing",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"(",
"0",
".",
".",
"65535",
")",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"<Definition> This parameter allows the user to set the spacing, in 0.01 meters, between paired detectors for use in calculating vehicle speeds. This parameter is measured from the leading edge of one detector to the leading edge of the paired detector. A value of 0 indicates there is no paired detector. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.2.2.1.18 <Object Type> P <Unit> one-hundredth of a meter\"",
"DEFVAL",
"{",
"0",
"}",
"::=",
"{",
"vehicleDetectorEntry",
"18",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"integerSubType",
[
[
0,
65535
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"<Definition> This parameter allows the user to set the spacing, in 0.01 meters, between paired detectors for use in calculating vehicle speeds. This parameter is measured from the leading edge of one detector to the leading edge of the paired detector. A value of 0 indicates there is no paired detector. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.2.2.1.18 <Object Type> P <Unit> one-hundredth of a meter"
],
null,
null,
null,
[
"DEFVAL",
0
]
]
}Module: NTCIP1202-v03
See published definition above
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['IpAddress', 'Counter', 'null'], 'RFC1213-MIB': ['DisplayString', 'ifIndex'], 'NTCIP8004v02': ['OwnerString', 'OerString', 'devices']}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: Potentially inaccurate interpretation of historical NTCIP namespace references: NTCIP8004v02. 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 NTCIP-1202v03.35e-aspublished.pdf — NTCIP1202-v03 (MIB transcription)Registration