Status in source: unconfirmed.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"rmcHistQueueStatus",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"(",
"0",
".",
".",
"65535",
")",
"ACCESS",
"read-only",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"Indicates the cumulative status of the queue detector. The values are: <Format> Bit Number Name Description Bit 15: reserved. Bit 14: reserved. Bit 13: reserved. Bit 12: reserved. Bit 11: reserved. Bit 10: reserved. Bit 09: reserved. Bit 08: Dependent Max Presence – the rmcQueueStatus-object has or had a value of ‘depNoActivity’ since reset. Bit 07: Dependent No Activity – the rmcQueueStatus-object has or had a value of ‘depNoActivity’ since reset. Bit 06: Error At Sensor – the rmcQueueStatus-object has or had a value of ‘Disabled’ since reset. Bit 05: No Activity – the rmcQueueStatus-object has or had a value of ‘noActivity’ since reset. Bit 04: Max Presence – the rmcQueueStatus-object has or had a value of ‘maxPresence’ since reset. Bit 03: Erratic Count – the rmcQueueStatus-object has or had a value of ‘erraticCount’ since reset. Bit 02: Other Error – the rmcQueueStatus-object has or had a value of ‘otherError’ since reset. Bit 01: Working – the rmcQueueStatus-object has or had a value of ‘Working’ since reset. Bit 00: Disabled – the rmcQueueStatus-object has or had a value of ‘Disabled’ since reset. In the context of this object, ‘reset’ means either an initialization of the RMC or a successful SET of the rmcHistDetectorReset-object. When a ‘reset’ occurs, all bits shall be set to 0. All reserved bits shall always be set to zero (0). A bad value error shall be returned, if a management application writes a one (1) to any of the reserved bits. <Object Identifier> 1.3.6.1.4.1.1206.4.2.2.3.3.3.10.1.3” REFERENCE \"",
"See",
"Clause",
"A",
".",
"2",
".",
"2",
".",
"3",
[
"literal",
"22"
],
"::=",
"{",
"rmcQueueStatEntry",
"3",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"integerSubType",
[
[
0,
65535
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"Indicates the cumulative status of the queue detector. The values are: <Format> Bit Number Name Description Bit 15: reserved. Bit 14: reserved. Bit 13: reserved. Bit 12: reserved. Bit 11: reserved. Bit 10: reserved. Bit 09: reserved. Bit 08: Dependent Max Presence – the rmcQueueStatus-object has or had a value of ‘depNoActivity’ since reset. Bit 07: Dependent No Activity – the rmcQueueStatus-object has or had a value of ‘depNoActivity’ since reset. Bit 06: Error At Sensor – the rmcQueueStatus-object has or had a value of ‘Disabled’ since reset. Bit 05: No Activity – the rmcQueueStatus-object has or had a value of ‘noActivity’ since reset. Bit 04: Max Presence – the rmcQueueStatus-object has or had a value of ‘maxPresence’ since reset. Bit 03: Erratic Count – the rmcQueueStatus-object has or had a value of ‘erraticCount’ since reset. Bit 02: Other Error – the rmcQueueStatus-object has or had a value of ‘otherError’ since reset. Bit 01: Working – the rmcQueueStatus-object has or had a value of ‘Working’ since reset. Bit 00: Disabled – the rmcQueueStatus-object has or had a value of ‘Disabled’ since reset. In the context of this object, ‘reset’ means either an initialization of the RMC or a successful SET of the rmcHistDetectorReset-object. When a ‘reset’ occurs, all bits shall be set to 0. All reserved bits shall always be set to zero (0). A bad value error shall be returned, if a management application writes a one (1) to any of the reserved bits. <Object Identifier> 1.3.6.1.4.1.1206.4.2.2.3.3.3.10.1.3"
],
[
"REFERENCE",
"See Clause A.2.2.3"
],
null,
null,
null
]
}
- NTCIP published standard MIB annexes (reviewed modules)
· Publisher's source file: NTCIP 1207 v02, Object Definitions for Ramp Meter Control (RMC) Units Published September 2014 — original PDF
· Official record
Module: N207v0214-MIB
See published definition above
Module imports
{'NTCIP': ['ramp'], 'RFC-1212': ['OBJECT-TYPE']}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: A typographic closing DESCRIPTION quotation delimiter occurs immediately at a native SMI field boundary. Normalize this delimiter only in the derived transcription; retain the literal published definition, full description and unchanged numeric assignments.
Source data warning: The PDF prints an invalid ASN.1 module label (1207v0214-MIB). The derived transcription uses an equal-length internal parsing label; this is not an OID registration or an alteration of any numeric assignment. The original label and full PDF are retained.
Source data warning: Potentially inaccurate interpretation of historical NTCIP namespace references: NTCIP. 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.
Source data warning: Published source disagreement: this literal SMI assignment resolves to 1.3.6.1.4.1.1206.4.2.2.3.3.10.1.3, but its DESCRIPTION explicitly lists 1.3.6.1.4.1.1206.4.2.2.3.3.3.10.1.3. Both published numeric claims are retained as unconfirmed evidence. Neither value is presented as a verified correction or an independently confirmed registration; consult the original file and the applicable standard edition.
· Download NTCIP1207v0214hj.pdf — N207v0214-MIB (MIB transcription)
Related source files and packages:
Show more related files and packages