Status in source: mandatory.
Names: pedestrianDetectorAlarms
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"pedestrianDetectorAlarms",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"(",
"0",
".",
".",
"255",
")",
"ACCESS",
"read-only",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"<Definition> This object shall return indications of detector alarms. Detector Alarms are indicated as follows (0 = False, 1 = True): Bit 7: Other Fault - The detector has failed due to some other cause. Bit 6: Reserved. Bit 5: Reserved. Bit 4: Configuration Fault - Detector is assigned but is not supported. Bit 3: Communications Fault - Communications to the device (if present) have failed. Bit 2: Erratic Output Fault - This detector has been flagged as non-operational due to erratic outputs (excessive counts) by the CU detector diagnostic. Bit 1: Max Presence Fault - This detector has been flagged as non-operational due to a presence indicator that exceeded the maximum expected time by the CU detector diagnostic. Bit 0: No Activity Fault - This detector has been flagged as non- operational due to lower than expected activity by the CU detector diagnostic Once set a bit shall maintain its state as long as the condition exists. The bit shall clear when the condition no longer exists. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.2.7.1.6\"",
"::=",
"{",
"pedestrianDetectorEntry",
"6",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"integerSubType",
[
[
0,
255
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"<Definition> This object shall return indications of detector alarms. Detector Alarms are indicated as follows (0 = False, 1 = True): Bit 7: Other Fault - The detector has failed due to some other cause. Bit 6: Reserved. Bit 5: Reserved. Bit 4: Configuration Fault - Detector is assigned but is not supported. Bit 3: Communications Fault - Communications to the device (if present) have failed. Bit 2: Erratic Output Fault - This detector has been flagged as non-operational due to erratic outputs (excessive counts) by the CU detector diagnostic. Bit 1: Max Presence Fault - This detector has been flagged as non-operational due to a presence indicator that exceeded the maximum expected time by the CU detector diagnostic. Bit 0: No Activity Fault - This detector has been flagged as non- operational due to lower than expected activity by the CU detector diagnostic Once set a bit shall maintain its state as long as the condition exists. The bit shall clear when the condition no longer exists. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.2.7.1.6"
],
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: