Status in source: mandatory.
Names: defaultForegroundRGB
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"defaultForegroundRGB",
"OBJECT-TYPE",
"SYNTAX",
"OCTET",
"STRING",
"(",
"SIZE",
"(",
"1",
"|",
"3",
")",
")",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"<Definition> Indicates the color of the foreground shown on the sign unless changed by the 'Color Foreground' MULTI tag. This is the color used to illuminate the 'ON' pixels of displayed characters. The values are expressed in values appropriate to the color scheme indicated by the dmsColorScheme object. When the 'color24bit' scheme is used, then this object contains three octets (first octet = red, second = green, third = blue). When 'monochrome1bit' is used, the value of this octet shall be either 0 or 1. When 'monochrome8bit' is used, the value of this octet shall be 0 to 255. In either the 'monochrome1bit' or 'monochrome8bit' scheme, the actual color is indicated in the monochromeColor object. When 'colorClassic' is used, the value of this octet shall be the value of the classic color. If the 'colorClassic' value (see dmsColorScheme object) is used, both defaultForegroundColor and defaultForegroundRGB objects shall return the same value if queried by a central system. Each of the foreground colors on a sign shall map to one of the colors in the color scheme of the sign. If a color is requested that is not supported, then a genErr shall be returned. This object may be sub-ranged by an implementation; see Section 3.5.2.3.2.2 for more information. <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.4.13\"",
"::=",
"{",
"multiCfg",
"13",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"OCTET STRING",
[
"octetStringSubType",
[
[
1
],
[
3
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"<Definition> Indicates the color of the foreground shown on the sign unless changed by the 'Color Foreground' MULTI tag. This is the color used to illuminate the 'ON' pixels of displayed characters. The values are expressed in values appropriate to the color scheme indicated by the dmsColorScheme object. When the 'color24bit' scheme is used, then this object contains three octets (first octet = red, second = green, third = blue). When 'monochrome1bit' is used, the value of this octet shall be either 0 or 1. When 'monochrome8bit' is used, the value of this octet shall be 0 to 255. In either the 'monochrome1bit' or 'monochrome8bit' scheme, the actual color is indicated in the monochromeColor object. When 'colorClassic' is used, the value of this octet shall be the value of the classic color. If the 'colorClassic' value (see dmsColorScheme object) is used, both defaultForegroundColor and defaultForegroundRGB objects shall return the same value if queried by a central system. Each of the foreground colors on a sign shall map to one of the colors in the color scheme of the sign. If a color is requested that is not supported, then a genErr shall be returned. This object may be sub-ranged by an implementation; see Section 3.5.2.3.2.2 for more information. <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.4.13"
],
null,
null,
null,
null
]
}
- ITE public NTCIP working repository MIBs
· Publisher's source file: NTCIP_1203 — v03/1203v03A-06g.mib
Module: NTCIP1203-v0305
See published definition above
Module imports
{'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.mib