Status in source: mandatory.
Names: vehicleDetectorOptions2
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"vehicleDetectorOptions2",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"(",
"0",
".",
".",
"255",
")",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"<Definition> A bit-mapped value as defined below for configuring detector options. <Format> bits 7-3 Reserved. bit 2 0=CUSTOM, 1=NTCIP Default Detector Speed Mode Option. For a vehicle detector operating in pairs, this option is used when there is an error on one of the paired detectors. It identifies how the controller should calculate speed without the other detector. CUSTOM indicates a manufacturer specific calculation. NTCIP indicates the use of the calculation Speed = (Average Vehicle Length + Detector Length) / Detect Time. bit 1 0=TRAIL, 1=LEAD Detector Placement Option. For a vehicle detector operating in pairs, this option indicates the leading and trailing detectors. LEAD indicates that the detector is the leading detector of the pair. TRAIL indicates that the detector is a trailing detector in the pair. bit 0 0=DISABLED, 1=ENABLED Speed Detector. If enabled, the detector is used to collect speed data (See volumeOccupancyTable and detectorAvgSpeed). This capability may not be supported on all detector inputs to a device. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.2.2.1.16\"",
"::=",
"{",
"vehicleDetectorEntry",
"16",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"integerSubType",
[
[
0,
255
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"<Definition> A bit-mapped value as defined below for configuring detector options. <Format> bits 7-3 Reserved. bit 2 0=CUSTOM, 1=NTCIP Default Detector Speed Mode Option. For a vehicle detector operating in pairs, this option is used when there is an error on one of the paired detectors. It identifies how the controller should calculate speed without the other detector. CUSTOM indicates a manufacturer specific calculation. NTCIP indicates the use of the calculation Speed = (Average Vehicle Length + Detector Length) / Detect Time. bit 1 0=TRAIL, 1=LEAD Detector Placement Option. For a vehicle detector operating in pairs, this option indicates the leading and trailing detectors. LEAD indicates that the detector is the leading detector of the pair. TRAIL indicates that the detector is a trailing detector in the pair. bit 0 0=DISABLED, 1=ENABLED Speed Detector. If enabled, the detector is used to collect speed data (See volumeOccupancyTable and detectorAvgSpeed). This capability may not be supported on all detector inputs to a device. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.2.2.1.16"
],
null,
null,
null,
null
]
}
- NTCIP published standard MIB annexes (reviewed modules)
· Publisher's source file: NTCIP 1202 v03A, Object Definitions for Actuated Signal Controllers (ASC) Interface Published May 2019 — original PDF
· Official record
Module: NTCIP1202-v03
See published definition above
Module imports
{'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: