OID reference
1.3.6.1.4.1.1206.4.2.1.2.2.1.9
Detector No Activity diagnostic Parameter in minutes (0–255 min.) . If an active detector does not exhibit an actuation in the specified period, it is considered a fault by the diagnostics and the detector is classified as Failed. A value of 0 for this object shall disable this diagnostic for this detector.
Identification
{1 3 6 1 4 1 1206 4 2 1 2 2 1 9}
Definitions may combine these properties differently.
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.9.<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.9
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 4 distinct definitions; some records may not include a definition.
vehicleDetectorNoActivity OBJECT-TYPE
SYNTAX INTEGER (0..255)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Detector No Activity diagnostic Parameter in minutes (0–255 min.) . If an active detector
does not exhibit an actuation in the specified period, it is considered a fault by the
diagnostics and the detector is classified as Failed. A value of 0 for this object shall disable
this diagnostic for this detector."
REFERENCE
"NEMA TS 2 Clause 3.9.3.1.4.1"
::= { vehicleDetectorEntry 9 }vehicleDetectorNoActivity OBJECT-TYPE
SYNTAX INTEGER (0..255)
ACCESS read-write
STATUS optional
DESCRIPTION
"<Definition> Detector No Activity diagnostic
Parameter in minutes (0–255 min.) . If an active
detector does not exhibit an actuation in the
specified period, it is considered a fault by the
diagnostics and the detector is classified as Failed.
A value of 0 for this object shall disable this
diagnostic for this detector.
<DescriptiveName> NTCIP-1202::ASC.vehicleDetectorNoActivity
<DataConceptType> Data Element
<Unit> minute"
REFERENCE
"NEMA TS 2 Clause 3.9.3.1.4.1"
::= { vehicleDetectorEntry 9 }vehicleDetectorNoActivity OBJECT-TYPE
SYNTAX INTEGER (0..255)
ACCESS read-write
STATUS mandatory
DESCRIPTION "<Definition> Detector No Activity diagnostic Parameter in
minutes (0-255 min.). If an active detector does not exhibit an
actuation in the specified period, it is considered a fault by
the diagnostics and the detector is classified as Failed. A value
of 0 for this object shall disable this diagnostic for this
detector.
<Object Identifier> 1.3.6.1.4.1.1206.4.2.1.2.2.1.9
<Object Type> P
<Unit> minute"
REFERENCE "NEMA TS 2 Clause 3.9.3.1.4.1"
::= { vehicleDetectorEntry 9 }vehicleDetectorNoActivity OBJECT-TYPE
SYNTAX INTEGER (0..255)
ACCESS read-write
STATUS mandatory
DESCRIPTION "<Definition> Detector No Activity diagnostic Parameter in
minutes (0–255 min.). If an active detector does not exhibit an
actuation in the specified period, it is considered a fault by
the diagnostics and the detector is classified as Failed. A value
of 0 for this object shall disable this diagnostic for this
detector.
<Object Identifier> 1.3.6.1.4.1.1206.4.2.1.2.2.1.9
<Unit> minute"
REFERENCE "NEMA TS 2 Clause 3.9.3.1.4.1"
::= { vehicleDetectorEntry 9 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Description 1
Detector No Activity diagnostic Parameter in minutes (0–255 min.) . If an active detector does not exhibit an actuation in the specified period, it is considered a fault by the diagnostics and the detector is classified as Failed. A value of 0 for this object shall disable this diagnostic for this detector.
NTCIP published standard MIB annexes (reviewed modules)
Description 2
<Definition> Detector No Activity diagnostic Parameter in minutes (0–255 min.) . If an active detector does not exhibit an actuation in the specified period, it is considered a fault by the diagnostics and the detector is classified as Failed. A value of 0 for this object shall disable this diagnostic for this detector. <DescriptiveName> NTCIP-1202::ASC.vehicleDetectorNoActivity <DataConceptType> Data Element <Unit> minute
NTCIP published standard MIB annexes (reviewed modules)
Description 3
<Definition> Detector No Activity diagnostic Parameter in minutes (0-255 min.). If an active detector does not exhibit an actuation in the specified period, it is considered a fault by the diagnostics and the detector is classified as Failed. A value of 0 for this object shall disable this diagnostic for this detector. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.2.2.1.9 <Object Type> P <Unit> minute
NTCIP published standard MIB annexes (reviewed modules)
Description 4
<Definition> Detector No Activity diagnostic Parameter in minutes (0–255 min.). If an active detector does not exhibit an actuation in the specified period, it is considered a fault by the diagnostics and the detector is classified as Failed. A value of 0 for this object shall disable this diagnostic for this detector. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.2.2.1.9 <Unit> minute
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: vehicleDetectorNoActivity
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"vehicleDetectorNoActivity",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"(",
"0",
".",
".",
"255",
")",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"Detector No Activity diagnostic Parameter in minutes (0–255 min.) . If an active detector does not exhibit an actuation in the specified period, it is considered a fault by the diagnostics and the detector is classified as Failed. A value of 0 for this object shall disable this diagnostic for this detector.\"",
"REFERENCE",
"\"NEMA TS 2 Clause 3.9.3.1.4.1\"",
"::=",
"{",
"vehicleDetectorEntry",
"9",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"integerSubType",
[
[
0,
255
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"Detector No Activity diagnostic Parameter in minutes (0–255 min.) . If an active detector does not exhibit an actuation in the specified period, it is considered a fault by the diagnostics and the detector is classified as Failed. A value of 0 for this object shall disable this diagnostic for this detector."
],
[
"REFERENCE",
"NEMA TS 2 Clause 3.9.3.1.4.1"
],
null,
null,
null
]
}Module: ASC_MIB1
See published definition above
{'TMIB': ['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: TMIB. 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 NTCIP1202v0107d.pdf — ASC_MIB1 (MIB transcription)Related source files and packages:
Status in source: optional.
Names: vehicleDetectorNoActivity
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"vehicleDetectorNoActivity",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"(",
"0",
".",
".",
"255",
")",
"ACCESS",
"read-write",
"STATUS",
"optional",
"DESCRIPTION",
"\"<Definition> Detector No Activity diagnostic Parameter in minutes (0–255 min.) . If an active detector does not exhibit an actuation in the specified period, it is considered a fault by the diagnostics and the detector is classified as Failed. A value of 0 for this object shall disable this diagnostic for this detector. <DescriptiveName> NTCIP-1202::ASC.vehicleDetectorNoActivity <DataConceptType> Data Element <Unit> minute\"",
"REFERENCE",
"\"NEMA TS 2 Clause 3.9.3.1.4.1\"",
"::=",
"{",
"vehicleDetectorEntry",
"9",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"integerSubType",
[
[
0,
255
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"optional"
],
[
"DESCRIPTION",
"<Definition> Detector No Activity diagnostic Parameter in minutes (0–255 min.) . If an active detector does not exhibit an actuation in the specified period, it is considered a fault by the diagnostics and the detector is classified as Failed. A value of 0 for this object shall disable this diagnostic for this detector. <DescriptiveName> NTCIP-1202::ASC.vehicleDetectorNoActivity <DataConceptType> Data Element <Unit> minute"
],
[
"REFERENCE",
"NEMA TS 2 Clause 3.9.3.1.4.1"
],
null,
null,
null
]
}Module: NTCIP1202-200x
See published definition above
{'TMIB-II': ['OwnerString', 'devices'], 'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['Counter']}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: 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 NTCIP1202v0219f.pdf — NTCIP1202-200x (MIB transcription)Related source files and packages:
Status in source: mandatory.
Names: vehicleDetectorNoActivity
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"vehicleDetectorNoActivity",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"(",
"0",
".",
".",
"255",
")",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"<Definition> Detector No Activity diagnostic Parameter in minutes (0-255 min.). If an active detector does not exhibit an actuation in the specified period, it is considered a fault by the diagnostics and the detector is classified as Failed. A value of 0 for this object shall disable this diagnostic for this detector. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.2.2.1.9 <Object Type> P <Unit> minute\"",
"REFERENCE",
"\"NEMA TS 2 Clause 3.9.3.1.4.1\"",
"::=",
"{",
"vehicleDetectorEntry",
"9",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"integerSubType",
[
[
0,
255
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"<Definition> Detector No Activity diagnostic Parameter in minutes (0-255 min.). If an active detector does not exhibit an actuation in the specified period, it is considered a fault by the diagnostics and the detector is classified as Failed. A value of 0 for this object shall disable this diagnostic for this detector. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.2.2.1.9 <Object Type> P <Unit> minute"
],
[
"REFERENCE",
"NEMA TS 2 Clause 3.9.3.1.4.1"
],
null,
null,
null
]
}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)Status in source: mandatory.
Names: vehicleDetectorNoActivity
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"vehicleDetectorNoActivity",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"(",
"0",
".",
".",
"255",
")",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"<Definition> Detector No Activity diagnostic Parameter in minutes (0–255 min.). If an active detector does not exhibit an actuation in the specified period, it is considered a fault by the diagnostics and the detector is classified as Failed. A value of 0 for this object shall disable this diagnostic for this detector. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.2.2.1.9 <Unit> minute\"",
"REFERENCE",
"\"NEMA TS 2 Clause 3.9.3.1.4.1\"",
"::=",
"{",
"vehicleDetectorEntry",
"9",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"integerSubType",
[
[
0,
255
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"<Definition> Detector No Activity diagnostic Parameter in minutes (0–255 min.). If an active detector does not exhibit an actuation in the specified period, it is considered a fault by the diagnostics and the detector is classified as Failed. A value of 0 for this object shall disable this diagnostic for this detector. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.2.2.1.9 <Unit> minute"
],
[
"REFERENCE",
"NEMA TS 2 Clause 3.9.3.1.4.1"
],
null,
null,
null
]
}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:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.1206.4.2.1.2.2.1.1 | vehicleDetectorNumber | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.1.2.2.1.2 | vehicleDetectorOptions | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.1.2.2.1.4 | vehicleDetectorCallPhase | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.1.2.2.1.5 | vehicleDetectorSwitchPhase | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.1.2.2.1.6 | vehicleDetectorDelay | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.1.2.2.1.7 | vehicleDetectorExtend | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.1.2.2.1.8 | vehicleDetectorQueueLimit | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.1.2.2.1.10 | vehicleDetectorMaxPresence | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.1.2.2.1.11 | vehicleDetectorErraticCounts | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.1.2.2.1.12 | vehicleDetectorFailTime | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.1.2.2.1.13 | vehicleDetectorAlarms | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.1.2.2.1.14 | vehicleDetectorReportedAlarms | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.1.2.2.1.15 | vehicleDetectorReset | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.1.2.2.1.16 | vehicleDetectorOptions2 | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.1.2.2.1.17 | vehicleDetectorPairedDetector | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.1.2.2.1.18 | vehicleDetectorPairedDetectorSpacing | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.1.2.2.1.19 | vehicleDetectorAvgVehicleLength | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.1.2.2.1.20 | vehicleDetectorLength | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.1.2.2.1.21 | vehicleDetectorTravelMode | 0 | 0 |