Status in source: deprecated.
Names: signalStateMinEndTick
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"signalStateMinEndTick",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"(",
"0",
".",
".",
"36001",
")",
"ACCESS",
"read-only",
"STATUS",
"deprecated",
"DESCRIPTION",
"\"<Definition> The tick count representing the earliest future time point when the signalState is expected to change, excluding unexpected events such as a preempt request. This object is used with the ascCurrentTick object. The value of this object will remain constant if the predicted future time point of the event does not change. Valid values range from 0 to 35999. A value of 36000 indicates the time point is infinite or beyond the range that can be represented (e.g., the earliest time point is greater than 36000 ticks). A value of 36001 indicates the time point of the event is undefined or unknown. The maximum reportable time point in the future the event will occur is 35999 deciseconds. To calculate this future time point consumers of this object subtracts signalStateMinEndTick from ascCurrentTick. If this result is negative add 36000 to the result (rollover). <Object Identifier> 1.3.6.1.4.1.1206.4.2.17.1.7.1.2 <Unit> tick\"",
"DEFVAL",
"{",
"36001",
"}",
"::=",
"{",
"signalStatusEntry",
"2",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"integerSubType",
[
[
0,
36001
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"deprecated"
],
[
"DESCRIPTION",
"<Definition> The tick count representing the earliest future time point when the signalState is expected to change, excluding unexpected events such as a preempt request. This object is used with the ascCurrentTick object. The value of this object will remain constant if the predicted future time point of the event does not change. Valid values range from 0 to 35999. A value of 36000 indicates the time point is infinite or beyond the range that can be represented (e.g., the earliest time point is greater than 36000 ticks). A value of 36001 indicates the time point of the event is undefined or unknown. The maximum reportable time point in the future the event will occur is 35999 deciseconds. To calculate this future time point consumers of this object subtracts signalStateMinEndTick from ascCurrentTick. If this result is negative add 36000 to the result (rollover). <Object Identifier> 1.3.6.1.4.1.1206.4.2.17.1.7.1.2 <Unit> tick"
],
null,
null,
null,
[
"DEFVAL",
36001
]
]
}
- NTCIP published standard MIB annexes (reviewed modules)
· Publisher's source file: NTCIP 1202 v03b NTCIP 1202 v02, Object Definitions for Actuated Traffic Signal Controller (ASC) Units – version 03b Published October 2023 — original PDF
· Official record
Module: NTCIP1217-v01
See published definition above
Module imports
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1213-MIB': ['DisplayString', 'ifIndex'], 'NTCIP8004v02': ['devices', 'OerString'], 'NTCIP1202-v03': ['channelNumber', 'signalGroupEntryNumber']}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: The mapSpeedLimitType DESCRIPTION starts with a duplicated malformed prefix. Mask only the extra DESCRIPTION prefix in an equal-length parsing copy, retaining the complete following native DESCRIPTION, original definition and unchanged OID assignment.
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 — NTCIP1217-v01 (MIB transcription)
Related source files and packages: