Status in source: mandatory.
Names: ascBlockGetControl
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"ascBlockGetControl",
"OBJECT-TYPE",
"SYNTAX",
"OCTET",
"STRING",
"(",
"SIZE",
"(",
"4",
".",
".",
"12",
")",
")",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"<Definition> An OER encoded string of reference parameters for ASC Block Uploads. The parameter values in this string are: ascBlockDataType INTEGER (0..255) ascBlockDataID INTEGER (0..255) ascBlockIndex1 INTEGER (0..255) if needed ascBlockQuantity1 INTEGER (0..255) if needed ascBlockIndex2 INTEGER (0..255) if needed ascBlockQuantity2 INTEGER (0..255) if needed ascBlockIndex3 INTEGER (0..255) if needed ascBlockQuantity3 INTEGER (0..255) if needed ascBlockIndex4 INTEGER (0..255) if needed ascBlockQuantity4 INTEGER (0..255) if needed ascBlockIndex5 INTEGER (0..255) if needed ascBlockQuantity5 INTEGER (0..255) if needed A GET of ascBlockData shall utilize values currently in this object to define the data to be returned. A SET of this object shall be evaluated for validity and Error Status of badValue(3) be returned for the following conditions: 1) ascBlockDataType is not supported 2) ascBlockDataID is not supported 3) ascBlockIndex1 is zero or not supported 4) ascBlockQuantity1 is zero or ascBlockIndex1 + ascBlockQuantity1 - 1 is not supported 5) ascBlockIndex2 is zero or not supported 6) ascBlockQuantity2 is zero or ascBlockIndex2 + ascBlockQuantity2) - 1 is not supported 7) ascBlockIndex3 is zero or not supported 8) ascBlockQuantity3 is zero or ascBlockIndex3 + scBlockQuantity3) - 1 is not supported 9) ascBlockIndex4 is zero or not supported 10) ascBlockQuantity4 is zero or ascBlockIndex4 + ascBlockQuantity4) - 1 is not supported 11) ascBlockIndex5 is zero or not supported 12) ascBlockQuantity5 is zero or ascBlockIndex5 + scBlockQuantity5) - 1 is not supported 13) if the SET length is zero or incorrect for ascBlockDataType & ascBlockDataID 14) if the GetResponse length for a GET on ascBlockData using maximum data field sizes would exceed a local limitation When this validity check fails, ascBlockErrorStatus shall be set equal to the Bullet Value above that generated the error. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.11.1 <Unit> \"",
"::=",
"{",
"ascBlock",
"1",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"OCTET STRING",
[
"octetStringSubType",
[
[
4,
12
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"<Definition> An OER encoded string of reference parameters for ASC Block Uploads. The parameter values in this string are: ascBlockDataType INTEGER (0..255) ascBlockDataID INTEGER (0..255) ascBlockIndex1 INTEGER (0..255) if needed ascBlockQuantity1 INTEGER (0..255) if needed ascBlockIndex2 INTEGER (0..255) if needed ascBlockQuantity2 INTEGER (0..255) if needed ascBlockIndex3 INTEGER (0..255) if needed ascBlockQuantity3 INTEGER (0..255) if needed ascBlockIndex4 INTEGER (0..255) if needed ascBlockQuantity4 INTEGER (0..255) if needed ascBlockIndex5 INTEGER (0..255) if needed ascBlockQuantity5 INTEGER (0..255) if needed A GET of ascBlockData shall utilize values currently in this object to define the data to be returned. A SET of this object shall be evaluated for validity and Error Status of badValue(3) be returned for the following conditions: 1) ascBlockDataType is not supported 2) ascBlockDataID is not supported 3) ascBlockIndex1 is zero or not supported 4) ascBlockQuantity1 is zero or ascBlockIndex1 + ascBlockQuantity1 - 1 is not supported 5) ascBlockIndex2 is zero or not supported 6) ascBlockQuantity2 is zero or ascBlockIndex2 + ascBlockQuantity2) - 1 is not supported 7) ascBlockIndex3 is zero or not supported 8) ascBlockQuantity3 is zero or ascBlockIndex3 + scBlockQuantity3) - 1 is not supported 9) ascBlockIndex4 is zero or not supported 10) ascBlockQuantity4 is zero or ascBlockIndex4 + ascBlockQuantity4) - 1 is not supported 11) ascBlockIndex5 is zero or not supported 12) ascBlockQuantity5 is zero or ascBlockIndex5 + scBlockQuantity5) - 1 is not supported 13) if the SET length is zero or incorrect for ascBlockDataType & ascBlockDataID 14) if the GetResponse length for a GET on ascBlockData using maximum data field sizes would exceed a local limitation When this validity check fails, ascBlockErrorStatus shall be set equal to the Bullet Value above that generated the error. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.11.1 <Unit>"
],
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: