Status in source: mandatory.
Names: spatPortMapActivationCode
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"spatPortMapActivationCode",
"OBJECT-TYPE",
"SYNTAX",
"MapActivationCode",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"<Definition> Represents the current mapActivationCode for this RSU port that the signal patterns on the CU are programmed for. The spatPortMapActivationCode value in this row should match the mapActivatePlan value for the RSU on this RSU port. This object allows the CU to compare and confirm that the signal phase and timing data matches the MAP data that may be broadcast by the RSU. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.16.5.1.3 <Object Type> P\"",
"::=",
"{",
"spatPortEntry",
"3",
"}"
],
"syntax_tree": [
[
"row",
"MapActivationCode"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"<Definition> Represents the current mapActivationCode for this RSU port that the signal patterns on the CU are programmed for. The spatPortMapActivationCode value in this row should match the mapActivatePlan value for the RSU on this RSU port. This object allows the CU to compare and confirm that the signal phase and timing data matches the MAP data that may be broadcast by the RSU. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.16.5.1.3 <Object Type> P"
],
null,
null,
null,
null
]
}
- 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: 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-1202v03.35e-aspublished.pdf — NTCIP1202-v03 (MIB transcription)
Related source files and packages: