OID reference
1.3.6.1.4.1.1206.4.2.3.6.23
<Definition> Indicates the base time at which the first pixel service shall occur. Time is expressed in minutes from the epoch of midnight of each day. Midnight shall be determined by local time, if the local clock feature (i.e., ISO 26048-1, 8.3.2) is supported; otherwise, it shall be based on UTC time. <Parameter Ty…
Identification
{1 3 6 1 4 1 1206 4 2 3 6 23}
Definitions may combine these properties differently.
At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.
snmpget [connection options] DEVICE .1.3.6.1.4.1.1206.4.2.3.6.23.0
Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.
Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.
Available source records contain 4 distinct definitions; some records may not include a definition.
vmsPixelServiceTime OBJECT-TYPE
SYNTAX Integer32 (0..1440)
UNITS "minutes"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"<Definition> Indicates the base time at which the first pixel service shall
occur. Time is expressed in minutes from the epoch of midnight of each day.
Midnight shall be determined by local time, if the local clock feature (i.e.,
ISO 26048-1, 8.3.2) is supported; otherwise, it shall be based on UTC time.
<Parameter Type> Configuration
<Object Identifier> 1.3.6.1.4.1.1206.4.2.3.6.23"
DEFVAL {1}
::= { signControl 23 }vmsPixelServiceTime OBJECT-TYPE
SYNTAX INTEGER (0..1440)
ACCESS read-write
STATUS optional
DESCRIPTION “Indicates the base time at which the first pixel service shall occur. Time is expressed in
minutes from the epoch of Midnight of each day.”
::= { signControl 23}vmsPixelServiceTime OBJECT-TYPE
SYNTAX INTEGER (0..1440)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"<Definition> Indicates the base time at which the first pixel service shall occur. Time is expressed in minutes from the epoch of Midnight of each day.
<Unit>minute
<Object Identifier> 1.3.6.1.4.1.1206.4.2.3.6.23"
DEFVAL {1}
::= { signControl 23 }vmsPixelServiceTime OBJECT-TYPE
SYNTAX INTEGER (0..1440)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"<Definition> Indicates the base time at which the first pixel service shall
occur. Time is expressed in minutes from the epoch of Midnight of each day.
<Unit>minute
<Object Identifier> 1.3.6.1.4.1.1206.4.2.3.6.23"
DEFVAL {1}
::= { signControl 23 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Description 1
<Definition> Indicates the base time at which the first pixel service shall occur. Time is expressed in minutes from the epoch of midnight of each day. Midnight shall be determined by local time, if the local clock feature (i.e., ISO 26048-1, 8.3.2) is supported; otherwise, it shall be based on UTC time. <Parameter Type> Configuration <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.6.23
Description 2
Indicates the base time at which the first pixel service shall occur. Time is expressed in minutes from the epoch of Midnight of each day.
NTCIP published standard MIB annexes (reviewed modules)
Description 3
<Definition> Indicates the base time at which the first pixel service shall occur. Time is expressed in minutes from the epoch of Midnight of each day. <Unit>minute <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.6.23
ITE public NTCIP working repository MIBsNTCIP published standard MIB annexes (reviewed modules)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: unconfirmed.
Names: vmsPixelServiceTime
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"vmsPixelServiceTime",
"OBJECT-TYPE",
"SYNTAX",
"Integer32",
"(",
"0",
".",
".",
"1440",
")",
"UNITS",
[
"literal",
"226d696e7574657322"
],
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"<Definition> Indicates the base time at which the first pixel service shall occur. Time is expressed in minutes from the epoch of midnight of each day. Midnight shall be determined by local time, if the local clock feature (i.e., ISO 26048-1, 8.3.2) is supported; otherwise, it shall be based on UTC time. <Parameter Type> Configuration <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.6.23\"",
"DEFVAL",
"{",
"1",
"}",
"::=",
"{",
"signControl",
"23",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"Integer32",
[
"integerSubType",
[
[
0,
1440
]
]
]
],
[
"UNITS",
"minutes"
],
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"<Definition> Indicates the base time at which the first pixel service shall occur. Time is expressed in minutes from the epoch of midnight of each day. Midnight shall be determined by local time, if the local clock feature (i.e., ISO 26048-1, 8.3.2) is supported; otherwise, it shall be based on UTC time. <Parameter Type> Configuration <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.6.23"
],
null,
null,
null,
[
"DEFVAL",
1
]
]
}Module: NTCIP1203-Dms
See published definition above
{'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'DisplayString', 'StorageType', 'RowStatus'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'Unsigned32', 'Counter32', 'IpAddress'], 'SNMPv2-CONF': ['OBJECT-GROUP'], 'ISO26048-1-Srsa': ['fdSrsaTypeCode', 'fdSrsaPortIndex'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString'], 'ISO26048-1-Global-TC': ['ITSDirection', 'ITSInteger8', 'ITSLatitude84', 'ITSLongitude84', 'ITSBitmap'], 'TRANSPORT-ADDRESS-MIB': ['TransportAddressType', 'TransportAddress'], 'NTCIP8004-Transportation': ['NtcipOwnerString', 'NtcipIntegerBitmap8', 'NtcipIntegerBitmap16', 'NtcipTwoColors', 'devices']}Source data warning: This original is published in an ITE NTCIP working repository. Repository publication does not establish that this particular revision is an adopted standard. Consult its native revision history and the NTCIP published standards catalog before implementation. Copyright and distribution notices are retained in the downloadable original.
Source data warning: Published module-root disagreement: dms has an SMI assignment resolving to 1.3.6.1.4.1.1206.4.2.6, while its DESCRIPTION explicitly prints 1.3.6.1.4.1.1206.4.2.3. All dependent assignments from this module require verification. No root number has been silently corrected.
Source data warning: Published source disagreement: this literal SMI assignment resolves to 1.3.6.1.4.1.1206.4.2.6.6.23, but its DESCRIPTION explicitly lists 1.3.6.1.4.1.1206.4.2.3.6.23. 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 NTCIP-1203 — NTCIP1203-Dms.mibStatus in source: optional.
Names: vmsPixelServiceTime
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"vmsPixelServiceTime",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"(",
"0",
".",
".",
"1440",
")",
"ACCESS",
"read-write",
"STATUS",
"optional",
"DESCRIPTION",
"“",
"Indicates",
"the",
"base",
"time",
"at",
"which",
"the",
"first",
"pixel",
"service",
"shall",
"occur",
".",
"Time",
"is",
"expressed",
"in",
"minutes",
"from",
"the",
"epoch",
"of",
"Midnight",
"of",
"each",
"day",
".",
"”",
"::=",
"{",
"signControl",
"23",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"integerSubType",
[
[
0,
1440
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"optional"
],
[
"DESCRIPTION",
"Indicates the base time at which the first pixel service shall occur. Time is expressed in minutes from the epoch of Midnight of each day."
],
null,
null,
null,
null
]
}Module: DMS-MIB
See published definition above
{'TMIB': ['OwnerString', 'devices'], 'NEMA_SMI': ['experimental'], 'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['IpAddress', 'Counter'], 'RFC1213-MIB': ['DisplayString']}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: A typographic opening 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: Potentially inaccurate interpretation of historical NTCIP namespace references: TMIB. 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: Unconfirmed interpretation of a historical NTCIP import: NTCIP 1203:1997 imports experimental from NEMA_SMI, but the retained original NEMA_SMI defines nemaExperimental instead. Section 2.10 explicitly locates these auxiliary I/O objects under the nema-experimental node. Here only that imported spelling is interpreted as the explicitly assigned nemaExperimental value. The original exp-global suffix 1 and all child numbers are retained. The later NTCIP 1201 v03 compatibility discussion also compares the old experimental spelling with nemaExperimental, but prints expGlobal suffix 2; that disagreement is not silently corrected or treated as proof that both historical branches are registered. These entries may be inaccurate; verify the linked original editions and your device. Native SMI STATUS is preserved separately.
nema OBJECT IDENTIFIER ::= { enterprises 1206 }nemaExperimental OBJECT IDENTIFIER ::= { nema 2 }
Related source files and packages:
Status in source: mandatory.
Names: vmsPixelServiceTime
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"vmsPixelServiceTime",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"(",
"0",
".",
".",
"1440",
")",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"<Definition> Indicates the base time at which the first pixel service shall occur. Time is expressed in minutes from the epoch of Midnight of each day. <Unit>minute <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.6.23\"",
"DEFVAL",
"{",
"1",
"}",
"::=",
"{",
"signControl",
"23",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"integerSubType",
[
[
0,
1440
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"<Definition> Indicates the base time at which the first pixel service shall occur. Time is expressed in minutes from the epoch of Midnight of each day. <Unit>minute <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.6.23"
],
null,
null,
null,
[
"DEFVAL",
1
]
]
}Module: NTCIP1203-v0305
See published definition above
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['IpAddress', 'Counter'], 'RFC1213-MIB': ['DisplayString'], 'NTCIP8004v02': ['OwnerString', 'dms']}Source data warning: This original is published in an ITE NTCIP working repository. Repository publication does not establish that this particular revision is an adopted standard. Consult its native revision history and the NTCIP published standards catalog before implementation. Copyright and distribution notices are retained in the downloadable original.
Source data warning: Potentially inaccurate interpretation of historical NTCIP imports: the original references NTCIP8004v02, which is absent from the public repository snapshot. 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_1203 — v03/1203v03A-06g.mibModule: NTCIP1203-v03-05
See published definition above
{'RFC-1212': ['OBJECT-TYPE'], 'NTCIP8004': ['OwnerString', 'dms'], 'RFC1155-SMI': ['IpAddress', 'Counter'], 'RFC1213-MIB': ['DisplayString']}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 PDF prints an invalid ASN.1 module label (NTCIP1203 v03.05). 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: NTCIP8004. 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 NTCIP1203v03f.pdf — NTCIP1203-v03-05 (MIB transcription)Related source files and packages:
Module: NTCIP1203-2005
Same published definition (formatting differs; exact original is in the source file)
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['IpAddress', 'Counter'], 'RFC1213-MIB': ['DisplayString'], 'NTCIP8004-A-2004': ['OwnerString', 'dms']}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: NTCIP8004-A-2004. 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 NTCIP1203v02-35a.pdf — NTCIP1203-2005 (MIB transcription)Registration