Status in source: optional.
Names: sensorZoneOutputSequenced
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"sensorZoneOutputSequenced",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"(",
"0",
".",
".",
"255",
")",
"ACCESS",
"read-write",
"STATUS",
"optional",
"DESCRIPTION",
"\"<Definition> This parameter identifies a zone that is required to have a detection before the zone associated with this output has a detection for this output to become active. This parameter can be used to create directional detection. If the zone associated with this output has a detection before the zone identified in this parameter, this output cannot be activated and the detection ceases before it can start watching the zone identified in this parameter. If the zone identified in this parameter has a detection and remains in detection, every time the zone associated with the output has a detection, its output is activated. The intent is that the two zones are in close enough proximity that a vehicle is able to be detected by both zones and that the last zone to detect the vehicle is the one that activates its output. <Object Identifier> 1.3.6.1.4.1.1206.4.2.4.1.12.1.9\"",
"::=",
"{",
"outputConditioningEntry",
"9",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"integerSubType",
[
[
0,
255
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"optional"
],
[
"DESCRIPTION",
"<Definition> This parameter identifies a zone that is required to have a detection before the zone associated with this output has a detection for this output to become active. This parameter can be used to create directional detection. If the zone associated with this output has a detection before the zone identified in this parameter, this output cannot be activated and the detection ceases before it can start watching the zone identified in this parameter. If the zone identified in this parameter has a detection and remains in detection, every time the zone associated with the output has a detection, its output is activated. The intent is that the two zones are in close enough proximity that a vehicle is able to be detected by both zones and that the last zone to detect the vehicle is the one that activates its output. <Object Identifier> 1.3.6.1.4.1.1206.4.2.4.1.12.1.9"
],
null,
null,
null,
null
]
}
- ITE public NTCIP working repository MIBs
· Publisher's source file: NTCIP-1209 — ntcip1209-Tss.mib
Module: NTCIP1209v02-MIB1
See published definition above
Module imports
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['IpAddress', 'Counter'], 'RFC1213-MIB': ['DisplayString'], 'NTCIP8004-2008': ['OwnerString', 'BITMAP8', 'BITMAP16', 'BITMAP32', 'tss']}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: Potentially inaccurate interpretation of historical NTCIP imports: the original references NTCIP8004-2008, which is absent from the public repository snapshot. 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-1209 — ntcip1209-Tss.mib
Related source files and packages:
- NTCIP published standard MIB annexes (reviewed modules)
· Publisher's source file: NTCIP 1209 v02, Object Definitions for Transportation Sensor Systems (TSS) Published May 2014 — original PDF
· Official record
Module: NTCIP1209v02-MIB1
See published definition above
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: missing or unreadable imports of tss. 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 NTCIP1209v0218jp.pdf — NTCIP1209v02-MIB1 (MIB transcription)
Related source files and packages: