Status in source: mandatory.
Names: phaseDynamicMaxStep
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"phaseDynamicMaxStep",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"(",
"0",
".",
".",
"255",
")",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"<Definition> This object shall determine the automatic adjustment to the running max in tenth seconds (0-25.5) When a phase maxes out twice in a row, and on each successive max out thereafter, one dynamic max step value shall be added to the running max until such addition would mean the running max was greater than the larger of normal max or dynamic max limit. When a phase gaps out twice in a row, and on each successive gap out thereafter, one dynamic max step value shall be subtracted from the running max until such subtraction would mean the running max was less than the smaller of the normal max or the dynamic max limit. If a phase gaps out in one cycle and maxes out in the next cycle, or vice versa, the running max will not change. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.1.2.1.19 <Unit> tenth second\"",
"::=",
"{",
"phaseEntry",
"19",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"integerSubType",
[
[
0,
255
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"<Definition> This object shall determine the automatic adjustment to the running max in tenth seconds (0-25.5) When a phase maxes out twice in a row, and on each successive max out thereafter, one dynamic max step value shall be added to the running max until such addition would mean the running max was greater than the larger of normal max or dynamic max limit. When a phase gaps out twice in a row, and on each successive gap out thereafter, one dynamic max step value shall be subtracted from the running max until such subtraction would mean the running max was less than the smaller of the normal max or the dynamic max limit. If a phase gaps out in one cycle and maxes out in the next cycle, or vice versa, the running max will not change. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.1.2.1.19 <Unit> tenth second"
],
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: