OID reference

dmsIllumBrightnessValues

1.3.6.1.4.1.1206.4.2.3.7.7

Description

<Definition> . An OCTET STRING describing the sign's light output in relationship to the Photocell(s) detection of ambient light. <Format> For each light output level, there is a corresponding range of photocell levels. The number of light output levels transmitted is defined by the first byte of the data packet, but …

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.1206.4.2.3.7 (illum)
Node code
7
Node name
dmsIllumBrightnessValues
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.1206.4.2.3.7.7
URN notation
urn:oid:1.3.6.1.4.1.1206.4.2.3.7.7
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 1206 4 2 3 7 7}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dms(3) illum(7) dmsIllumBrightnessValues(7)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) fontDefinition(3) illum(7) dmsIllumBrightnessValues(7)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dms(3) illum(7) dmsIllumBrightnessValues(7)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) fontDefinition(3) illum(7) dmsIllumBrightnessValues(7)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) dms(3) illum(7) dmsIllumBrightnessValues(7)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) fontDefinition(3) illum(7) dmsIllumBrightnessValues(7)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) dms(3) illum(7) dmsIllumBrightnessValues(7)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) fontDefinition(3) illum(7) dmsIllumBrightnessValues(7)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dms(3) illum(7) dmsIllumBrightnessValues(7)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) fontDefinition(3) illum(7) dmsIllumBrightnessValues(7)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dms(3) illum(7) dmsIllumBrightnessValues(7)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) fontDefinition(3) illum(7) dmsIllumBrightnessValues(7)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) dms(3) illum(7) dmsIllumBrightnessValues(7)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) fontDefinition(3) illum(7) dmsIllumBrightnessValues(7)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) dms(3) illum(7) dmsIllumBrightnessValues(7)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) fontDefinition(3) illum(7) dmsIllumBrightnessValues(7)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/1206/4/2/3/7/7
  • /ISO/Identified-Organization/6/1/4/1/1206/4/2/3/7/7
  • /ISO/3/6/1/4/1/1206/4/2/3/7/7
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/dms/illum/dmsIllumBrightnessValues
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/fontDefinition/illum/dmsIllumBrightnessValues
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/dms/illum/dmsIllumBrightnessValues
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/fontDefinition/illum/dmsIllumBrightnessValues
  • /iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/dms/illum/dmsIllumBrightnessValues
  • /iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/fontDefinition/illum/dmsIllumBrightnessValues
  • /iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/dms/illum/dmsIllumBrightnessValues
  • /iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/fontDefinition/illum/dmsIllumBrightnessValues
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/1206/transportation/devices/dms/illum/dmsIllumBrightnessValues
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/1206/transportation/devices/fontDefinition/illum/dmsIllumBrightnessValues
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/nema/transportation/devices/dms/illum/dmsIllumBrightnessValues
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/nema/transportation/devices/fontDefinition/illum/dmsIllumBrightnessValues
  • /iso/identified-organization/dod/internet/private/vendor-objects/1206/transportation/devices/dms/illum/dmsIllumBrightnessValues
  • /iso/identified-organization/dod/internet/private/vendor-objects/1206/transportation/devices/fontDefinition/illum/dmsIllumBrightnessValues
  • /iso/identified-organization/dod/internet/private/vendor-objects/nema/transportation/devices/dms/illum/dmsIllumBrightnessValues
  • /iso/identified-organization/dod/internet/private/vendor-objects/nema/transportation/devices/fontDefinition/illum/dmsIllumBrightnessValues
  • Additional combinations skipped.

SNMP properties

Value type
OCTET STRING
Maximum access defined by MIB
read-write
Status in MIB
current, mandatory

Definitions may combine these properties differently.

Compare 2 source variants

Variant 1 — ITE public NTCIP working repository MIBs

Value type
OCTET STRING
Maximum access defined by MIB
read-write
Status in MIB
current

Variant 2 — NTCIP published standard MIB annexes (reviewed modules), ITE public NTCIP working repository MIBs

Value type
OCTET STRING
Maximum access defined by MIB
read-write
Status in MIB
mandatory

Using this OID with SNMP

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.7.7.0

Replace the placeholders with your connection and authentication options. Some definitions do not specify a readable access value. 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 5 distinct definitions; some records may not include a definition.

Show 5 published definitions

dmsIllumBrightnessValues · unconfirmed

dmsIllumBrightnessValues  OBJECT-TYPE 
SYNTAX      OCTET STRING 
MAX-ACCESS  read-write 
STATUS      current  
DESCRIPTION  
"<Definition> . An OCTET STRING describing the sign's light output in 
relationship to the Photocell(s) detection of ambient light. 
<Format> For each light output level, there is a corresponding range of 
photocell levels. The number of light output levels transmitted is defined by 
the first byte of the data packet, but cannot exceed the value of the 
dmsIllumNumBrightLevels object. Setting the value of this object to a non-
supported or erroneous value shall lead to a wrongValue or inconsistentValue 
error, as appropriate. Cause of this error shall be denoted by the 
dmsIllumBrightnessValuesError object.
After a SET, an implementation may interpolate these entries to create a 
table with as many entries as needed, but the value of the object shall not 
be affected by such interpolations. 
For each light output level, there are three 16-bit values that occur in the 
following order: Light output level, Photocell level down, Photocell level 
up.
The light output level is a value between 0 (no light output) and 65535 
(maximum light output). Each step is 1/65535 of the maximum light output 
(linear scale).
The Photocell-level-down is the lowest photocell level allowed to maintain 
the light output level. If the photocell level goes below this point, the 
light output level goes down one light output level.
The Photocell-level-up is the highest photocell level for this light output 
level. If the photocell level goes above this point, the light output level 
goes up one light output level.
The photocell level (Up and Down) values may not exceed the value of the 
ISO26048-1-Srsa:fdSrsaPortMaxValue.FAL object.
The points transmitted should be selected so that there is no photocell level 
which does not have a light output level. Hysteresis is possible by defining 
the photocell-level-up at a level higher than the upper level's photocell-
level-down. 
The encoding of the structure shall consist of a one byte integer value 
indicating the number of rows in the table. This is followed by a series of 
OER encoded Strings of the following structure:
  SEQUENCE {
      lightOutput            INTEGER (0..65535),
      photocellLevelDown     INTEGER (0..65535),
      photocellLevelUp       INTEGER (0..65535) } 

If the sign does not support photocell and the dmsIllumControl object value 
is set to 'manualIndexed', then the values for the 'photocellLevelDown' and 
'photocellLevelUp' still need to be entered that the table does not cause any 
errors as defined in the dmsIllumBrightnessValuesError object. However, since 
no photocell is supported, the entered values for 'photocellLevelDown' and 
'photocellLevelUp' for the various 'lightOutputs' are meaningless.

<Parameter Type> Configuration
<Object Identifier> 1.3.6.1.4.1.1206.4.2.3.7.7"
::= { illum 7 }

dmsIllumBrightnessValues · mandatory

dmsIllumBrightnessValues OBJECT-TYPE
SYNTAX OCTET STRING
ACCESS read-write
STATUS mandatory
DESCRIPTION
"<Definition> . An OCTET STRING describing the sign's light output in
relationship to the Photocell(s) detection of ambient light. For each light
output level, there is a corresponding range of photocell levels. The number
of light output levels transmitted is defined by the first byte of the data
packet, but cannot exceed the value of the dmsIllumNumBrightLevels object.
Setting the value of this object to a non-supported or erroneous value shall
lead to a genErr. Cause of this error shall be denoted by the
dmsIllumBrightnessValuesError object.
After a SET, an implementation may interpolate these entries to create a
table with as many entries as needed, but the value of the object shall not
be affected by such interpolations.
For each light output level, there are three 16-bit values that occur in the
following order: Light output level, Photocell level down, Photocell level
up.
The light output level is a value between 0 (no light output) and 65535
(maximum light output). Each step is 1/65535 of the maximum light output
(linear scale).
The Photocell-level-down is the lowest photocell level allowed to maintain
the light output level. If the photocell level goes below this point, the
light output level goes down one light output level.
The Photocell-level-up is the highest photocell level for this light output
level. If the photocell level goes above this point, the light output level
goes up one light output level.
The photocell level (Up and Down) values may not exceed the value of the
dmsIllumMaxPhotocellLevel object.
The points transmitted should be selected so that there is no photocell level
which does not have a light output level. Hysteresis is possible by defining
the photocell-level-up at a level higher than the upper level's photocell-
level-down.
The encoding of the structure shall consist of a one byte integer value
indicating the number of rows in the table. This is followed by a series of
OER encoded Strings of the following structure:
   SEQUENCE {
       lightOutput                 INTEGER (0..65535),
       photocellLevelDown          INTEGER (0..65535),


                                                                                        

                 
        

        photocellLevelUp               INTEGER (0..65535) }

If the sign does not support photocell and the dmsIllumControl object value
is set to 'manualIndexed', then the values for the 'photocellLevelDown' and
'photocellLevelUp' still need to be entered that the table does not cause any
errors as defined in the dmsIllumBrightnessValuesError object. However, since
no photocell is supported, the entered values for 'photocellLevelDown' and
'photocellLevelUp' for the various 'lightOutputs' are meaningless.

<Object Identifier> 1.3.6.1.4.1.1206.4.2.3.7.7"
::= { illum 7 }

dmsIllumBrightnessValues · mandatory

dmsIllumBrightnessValues  OBJECT-TYPE
SYNTAX  OCTET STRING
ACCESS  read-write
STATUS  mandatory
DESCRIPTION 
"<Definition> . An OCTET STRING describing the sign's light output in relationship to the Photocell(s) detection of ambient light. For each light output level, there is a corresponding range of photocell levels. The number of light output levels transmitted is defined by the first byte of the data packet, but cannot exceed the value of the dmsIllumNumBrightLevels object. Setting the value of this object to a non-supported or erroneous value shall lead to a genErr. Cause of this error shall be denoted by the dmsIllumBrightnessValuesError object.
After a SET, an implementation may interpolate these entries to create a table with as many entries as needed, but the value of the object shall not be affected by such interpolations. 
For each light output level, there are three 16-bit values that occur in the following order: Light output level, Photocell level down, Photocell level up.
The light output level is a value between 0 (no light output) and 65535 (maximum light output). Each step is 1/65535 of the maximum light output (linear scale).
The Photocell-level-down is the lowest photocell level allowed to maintain the light output level. If the photocell level goes below this point, the light output level goes down one light output level.
The Photocell-level-up is the highest photocell level for this light output level. If the photocell level goes above this point, the light output level goes up one light output level.
The photocell level (Up and Down) values may not exceed the value of the dmsIllumMaxPhotocellLevel object.
The points transmitted should be selected so that there is no photocell level which does not have a light output level. Hysteresis is possible by defining the photocell-level-up at a level higher than the upper level's photocell-level-down. 
The encoding of the structure shall consist of a one byte integer value indicating the number of rows in the table. This is followed by a series of OER encoded Strings of the following structure:
  SEQUENCE {
      lightOutput            INTEGER (0..65535),
      photocellLevelDown     INTEGER (0..65535),
      photocellLevelUp       INTEGER (0..65535) }

If the sign does not support photocell and the dmsIllumControl object value is set to 'manualIndexed', then the values for the 'photocellLevelDown' and 'photocellLevelUp' still need to be entered that the table does not cause any errors as defined in the dmsIllumBrightnessValuesError object. However, since no photocell is supported, the entered values for 'photocellLevelDown' and 'photocellLevelUp' for the various 'lightOutputs' are meaningless.

<Object Identifier> 1.3.6.1.4.1.1206.4.2.3.7.7"
::= { illum 7 }

dmsIllumBrightnessValues · mandatory

dmsIllumBrightnessValues OBJECT-TYPE
SYNTAX           OCTET STRING
ACCESS           read-write
STATUS           mandatory
DESCRIPTION “An OCTET STRING describing the sign's Brightness Level in relationship to the
Photocell(s) detection of ambient light. For each brightness level, there is a corresponding range of
photocell levels. The number of levels transmitted is defined by the first byte of the datapacket, but
cannot exceed the value of the dmsIllumNumBrightLevels object. "
--After a SET, an implementation may interpolate these entries to create a table with as many


                                                                                                        

                                                                                                           
                                                                                                           



--entries as needed. For each level, there are three 16-bit values that occur in the following order:
--Brightness point, Photocell level down, Photocell level up.
--The Brightness point is a value between 0 (no light output) and 65535 (maximum light output).
--Each step is 1/65535 of the maximum light output (linear scale).
--The Photocell-level-down is the lowest photocell level for this brightness level. Should the
--photocell level go below this point, the automatic brightness level would go down one level.
--The Photocell-level-up is the highest photocell level for this brightness level. Should the
--photocell level go above this point, the automatic brightness level would go up one level.
--The photocell level (Up and Down) values may not exceed the value of the
--dmsIllumMaxPhotocellLevel object.”
::= {illum 7}

dmsIllumBrightnessValues · mandatory

dmsIllumBrightnessValues OBJECT-TYPE
SYNTAX OCTET STRING
ACCESS read-write



                                                                                        

Page 184                                                           NTCIP 1203 v02.35


STATUS mandatory
DESCRIPTION
"<Definition> For additional information see Annex E - Frequently Asked
Questions section, questions 8 and 9.
An OCTET STRING describing the sign's light output in relationship to the
Photocell(s) detection of ambient light. For each light output level, there
is a corresponding range of photocell levels. The number of light output
levels transmitted is defined by the first byte of the data packet, but
cannot exceed the value of the dmsIllumNumBrightLevels object. Setting the
value of this object to a non-supported or erroneous value shall lead to a
genErr. Cause of this error shall be denoted by the
dmsIllumBrightnessValuesError object.
After a SET, an implementation may interpolate these entries to create a
table with as many entries as needed, but the value of the object shall not
be affected by such interpolations.
For each light output level, there are three 16-bit values that occur in the
following order: Light output level, Photocell level down, Photocell level
up.
The light output level is a value between 0 (no light output) and 65535
(maximum light output). Each step is 1/65535 of the maximum light output
(linear scale).
The Photocell-level-down is the lowest photocell level allowed to maintain
the light output level. Should the photocell level go below this point, the
light output level would go down one light output level.
The Photocell-level-up is the highest photocell level for this light output
level. Should the photocell level go above this point, the light output
level would go up one light output level.
The photocell level (Up and Down) values may not exceed the value of the
dmsIllumMaxPhotocellLevel object.
The points transmitted should be selected so that there is no photocell level
which does not have a light output level. Hysteresis is possible by defining
the photocell-level-up at a level higher than the upper level's photocell-
level-down.
The encoding of the structure shall consist of a one byte integer value
indicating the number of rows in the table. This will be followed by a
series of OER encoded Strings of the following structure:
  SEQUENCE {
      lightOutput            INTEGER (0..65535),
      photocellLevelDown     INTEGER (0..65535),
      photocellLevelUp       INTEGER (0..65535) }

If the sign does not support photocell and the dmsIllumControl object value
is set to 'manualIndexed', then the values for the 'photocellLevelDown' and
'photocellLevelUp' still need to be entered that the table does not cause any
errors as defined in the dmsIllumBrightnessValuesError object. However,
since no photocell is supported, the entered values for 'photocellLevelDown'
and 'photocellLevelUp' for the various 'lightOutputs' are meaningless.

<Object Identifier> 1.3.6.1.4.1.1206.4.2.3.7.7"
::= { illum 7 }

Meaning

Descriptions

5 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

Description 1

<Definition> . An OCTET STRING describing the sign's light output in relationship to the Photocell(s) detection of ambient light. <Format> For each light output level, there is a corresponding range of photocell levels. The number of light output levels transmitted is defined by the first byte of the data packet, but cannot exceed the value of the dmsIllumNumBrightLevels object. Setting the value of this object to a non- supported or erroneous value shall lead to a wrongValue or inconsistentValue error, as appropriate. Cause of this error shall be denoted by the dmsIllumBrightnessValuesError object. After a SET, an implementation may interpolate these entries to create a table with as many entries as needed, but the value of the object shall not be affected by such interpolations. For each light output level, there are three 16-bit values that occur in the following order: Light output level, Photocell level down, Photocell level up. The light output level is a value between 0 (no light output) and 65535 (maximum light output). Each step is 1/65535 of the maximum light output (linear scale). The Photocell-level-down is the lowest photocell level allowed to maintain the light output level. If the photocell level goes below this point, the light output level goes down one light output level. The Photocell-level-up is the highest photocell level for this light output level. If the photocell level goes above this point, the light output level goes up one light output level. The photocell level (Up and Down) values may not exceed the value of the ISO26048-1-Srsa:fdSrsaPortMaxValue.FAL object. The points transmitted should be selected so that there is no photocell level which does not have a light output level. Hysteresis is possible by defining the photocell-level-up at a level higher than the upper level's photocell- level-down. The encoding of the structure shall consist of a one byte integer value indicating the number of rows in the table. This is followed by a series of OER encoded Strings of the following structure: SEQUENCE { lightOutput INTEGER (0..65535), photocellLevelDown INTEGER (0..65535), photocellLevelUp INTEGER (0..65535) } If the sign does not support photocell and the dmsIllumControl object value is set to 'manualIndexed', then the values for the 'photocellLevelDown' and 'photocellLevelUp' still need to be entered that the table does not cause any errors as defined in the dmsIllumBrightnessValuesError object. However, since no photocell is supported, the entered values for 'photocellLevelDown' and 'photocellLevelUp' for the various 'lightOutputs' are meaningless. <Parameter Type> Configuration <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.7.7

Sources for this description

ITE public NTCIP working repository MIBs

See 1 matching source record

Description 2

<Definition> . An OCTET STRING describing the sign's light output in relationship to the Photocell(s) detection of ambient light. For each light output level, there is a corresponding range of photocell levels. The number of light output levels transmitted is defined by the first byte of the data packet, but cannot exceed the value of the dmsIllumNumBrightLevels object. Setting the value of this object to a non-supported or erroneous value shall lead to a genErr. Cause of this error shall be denoted by the dmsIllumBrightnessValuesError object. After a SET, an implementation may interpolate these entries to create a table with as many entries as needed, but the value of the object shall not be affected by such interpolations. For each light output level, there are three 16-bit values that occur in the following order: Light output level, Photocell level down, Photocell level up. The light output level is a value between 0 (no light output) and 65535 (maximum light output). Each step is 1/65535 of the maximum light output (linear scale). The Photocell-level-down is the lowest photocell level allowed to maintain the light output level. If the photocell level goes below this point, the light output level goes down one light output level. The Photocell-level-up is the highest photocell level for this light output level. If the photocell level goes above this point, the light output level goes up one light output level. The photocell level (Up and Down) values may not exceed the value of the dmsIllumMaxPhotocellLevel object. The points transmitted should be selected so that there is no photocell level which does not have a light output level. Hysteresis is possible by defining the photocell-level-up at a level higher than the upper level's photocell- level-down. The encoding of the structure shall consist of a one byte integer value indicating the number of rows in the table. This is followed by a series of OER encoded Strings of the following structure: SEQUENCE { lightOutput INTEGER (0..65535), photocellLevelDown INTEGER (0..65535), photocellLevelUp INTEGER (0..65535) } If the sign does not support photocell and the dmsIllumControl object value is set to 'manualIndexed', then the values for the 'photocellLevelDown' and 'photocellLevelUp' still need to be entered that the table does not cause any errors as defined in the dmsIllumBrightnessValuesError object. However, since no photocell is supported, the entered values for 'photocellLevelDown' and 'photocellLevelUp' for the various 'lightOutputs' are meaningless. <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.7.7

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 3

<Definition> . An OCTET STRING describing the sign's light output in relationship to the Photocell(s) detection of ambient light. For each light output level, there is a corresponding range of photocell levels. The number of light output levels transmitted is defined by the first byte of the data packet, but cannot exceed the value of the dmsIllumNumBrightLevels object. Setting the value of this object to a non-supported or erroneous value shall lead to a genErr. Cause of this error shall be denoted by the dmsIllumBrightnessValuesError object. After a SET, an implementation may interpolate these entries to create a table with as many entries as needed, but the value of the object shall not be affected by such interpolations. For each light output level, there are three 16-bit values that occur in the following order: Light output level, Photocell level down, Photocell level up. The light output level is a value between 0 (no light output) and 65535 (maximum light output). Each step is 1/65535 of the maximum light output (linear scale). The Photocell-level-down is the lowest photocell level allowed to maintain the light output level. If the photocell level goes below this point, the light output level goes down one light output level. The Photocell-level-up is the highest photocell level for this light output level. If the photocell level goes above this point, the light output level goes up one light output level. The photocell level (Up and Down) values may not exceed the value of the dmsIllumMaxPhotocellLevel object. The points transmitted should be selected so that there is no photocell level which does not have a light output level. Hysteresis is possible by defining the photocell-level-up at a level higher than the upper level's photocell-level-down. The encoding of the structure shall consist of a one byte integer value indicating the number of rows in the table. This is followed by a series of OER encoded Strings of the following structure: SEQUENCE { lightOutput INTEGER (0..65535), photocellLevelDown INTEGER (0..65535), photocellLevelUp INTEGER (0..65535) } If the sign does not support photocell and the dmsIllumControl object value is set to 'manualIndexed', then the values for the 'photocellLevelDown' and 'photocellLevelUp' still need to be entered that the table does not cause any errors as defined in the dmsIllumBrightnessValuesError object. However, since no photocell is supported, the entered values for 'photocellLevelDown' and 'photocellLevelUp' for the various 'lightOutputs' are meaningless. <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.7.7

Sources for this description

ITE public NTCIP working repository MIBs

See 1 matching source record

Description 4

An OCTET STRING describing the sign's Brightness Level in relationship to the Photocell(s) detection of ambient light. For each brightness level, there is a corresponding range of photocell levels. The number of levels transmitted is defined by the first byte of the datapacket, but cannot exceed the value of the dmsIllumNumBrightLevels object.

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 5

<Definition> For additional information see Annex E - Frequently Asked Questions section, questions 8 and 9. An OCTET STRING describing the sign's light output in relationship to the Photocell(s) detection of ambient light. For each light output level, there is a corresponding range of photocell levels. The number of light output levels transmitted is defined by the first byte of the data packet, but cannot exceed the value of the dmsIllumNumBrightLevels object. Setting the value of this object to a non-supported or erroneous value shall lead to a genErr. Cause of this error shall be denoted by the dmsIllumBrightnessValuesError object. After a SET, an implementation may interpolate these entries to create a table with as many entries as needed, but the value of the object shall not be affected by such interpolations. For each light output level, there are three 16-bit values that occur in the following order: Light output level, Photocell level down, Photocell level up. The light output level is a value between 0 (no light output) and 65535 (maximum light output). Each step is 1/65535 of the maximum light output (linear scale). The Photocell-level-down is the lowest photocell level allowed to maintain the light output level. Should the photocell level go below this point, the light output level would go down one light output level. The Photocell-level-up is the highest photocell level for this light output level. Should the photocell level go above this point, the light output level would go up one light output level. The photocell level (Up and Down) values may not exceed the value of the dmsIllumMaxPhotocellLevel object. The points transmitted should be selected so that there is no photocell level which does not have a light output level. Hysteresis is possible by defining the photocell-level-up at a level higher than the upper level's photocell- level-down. The encoding of the structure shall consist of a one byte integer value indicating the number of rows in the table. This will be followed by a series of OER encoded Strings of the following structure: SEQUENCE { lightOutput INTEGER (0..65535), photocellLevelDown INTEGER (0..65535), photocellLevelUp INTEGER (0..65535) } If the sign does not support photocell and the dmsIllumControl object value is set to 'manualIndexed', then the values for the 'photocellLevelDown' and 'photocellLevelUp' still need to be entered that the table does not cause any errors as defined in the dmsIllumBrightnessValuesError object. However, since no photocell is supported, the entered values for 'photocellLevelDown' and 'photocellLevelUp' for the various 'lightOutputs' are meaningless. <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.7.7

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Evidence

Source records

5 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1ITE public NTCIP working repository MIBs1 record · 1 source

Description 1

dmsIllumBrightnessValues · unconfirmedITE public NTCIP working repository MIBs1 source

Status in source: unconfirmed.

Names: dmsIllumBrightnessValues

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dmsIllumBrightnessValues",
    "OBJECT-TYPE",
    "SYNTAX",
    "OCTET",
    "STRING",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"<Definition> . An OCTET STRING describing the sign's light output in relationship to the Photocell(s) detection of ambient light. <Format> For each light output level, there is a corresponding range of photocell levels. The number of light output levels transmitted is defined by the first byte of the data packet, but cannot exceed the value of the dmsIllumNumBrightLevels object. Setting the value of this object to a non- supported or erroneous value shall lead to a wrongValue or inconsistentValue error, as appropriate. Cause of this error shall be denoted by the dmsIllumBrightnessValuesError object. After a SET, an implementation may interpolate these entries to create a table with as many entries as needed, but the value of the object shall not be affected by such interpolations. For each light output level, there are three 16-bit values that occur in the following order: Light output level, Photocell level down, Photocell level up. The light output level is a value between 0 (no light output) and 65535 (maximum light output). Each step is 1/65535 of the maximum light output (linear scale). The Photocell-level-down is the lowest photocell level allowed to maintain the light output level. If the photocell level goes below this point, the light output level goes down one light output level. The Photocell-level-up is the highest photocell level for this light output level. If the photocell level goes above this point, the light output level goes up one light output level. The photocell level (Up and Down) values may not exceed the value of the ISO26048-1-Srsa:fdSrsaPortMaxValue.FAL object. The points transmitted should be selected so that there is no photocell level which does not have a light output level. Hysteresis is possible by defining the photocell-level-up at a level higher than the upper level's photocell- level-down. The encoding of the structure shall consist of a one byte integer value indicating the number of rows in the table. This is followed by a series of OER encoded Strings of the following structure: SEQUENCE { lightOutput INTEGER (0..65535), photocellLevelDown INTEGER (0..65535), photocellLevelUp INTEGER (0..65535) } If the sign does not support photocell and the dmsIllumControl object value is set to 'manualIndexed', then the values for the 'photocellLevelDown' and 'photocellLevelUp' still need to be entered that the table does not cause any errors as defined in the dmsIllumBrightnessValuesError object. However, since no photocell is supported, the entered values for 'photocellLevelDown' and 'photocellLevelUp' for the various 'lightOutputs' are meaningless. <Parameter Type> Configuration <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.7.7\"",
    "::=",
    "{",
    "illum",
    "7",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "OCTET STRING"
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "<Definition> . An OCTET STRING describing the sign's light output in relationship to the Photocell(s) detection of ambient light. <Format> For each light output level, there is a corresponding range of photocell levels. The number of light output levels transmitted is defined by the first byte of the data packet, but cannot exceed the value of the dmsIllumNumBrightLevels object. Setting the value of this object to a non- supported or erroneous value shall lead to a wrongValue or inconsistentValue error, as appropriate. Cause of this error shall be denoted by the dmsIllumBrightnessValuesError object. After a SET, an implementation may interpolate these entries to create a table with as many entries as needed, but the value of the object shall not be affected by such interpolations. For each light output level, there are three 16-bit values that occur in the following order: Light output level, Photocell level down, Photocell level up. The light output level is a value between 0 (no light output) and 65535 (maximum light output). Each step is 1/65535 of the maximum light output (linear scale). The Photocell-level-down is the lowest photocell level allowed to maintain the light output level. If the photocell level goes below this point, the light output level goes down one light output level. The Photocell-level-up is the highest photocell level for this light output level. If the photocell level goes above this point, the light output level goes up one light output level. The photocell level (Up and Down) values may not exceed the value of the ISO26048-1-Srsa:fdSrsaPortMaxValue.FAL object. The points transmitted should be selected so that there is no photocell level which does not have a light output level. Hysteresis is possible by defining the photocell-level-up at a level higher than the upper level's photocell- level-down. The encoding of the structure shall consist of a one byte integer value indicating the number of rows in the table. This is followed by a series of OER encoded Strings of the following structure: SEQUENCE { lightOutput INTEGER (0..65535), photocellLevelDown INTEGER (0..65535), photocellLevelUp INTEGER (0..65535) } If the sign does not support photocell and the dmsIllumControl object value is set to 'manualIndexed', then the values for the 'photocellLevelDown' and 'photocellLevelUp' still need to be entered that the table does not cause any errors as defined in the dmsIllumBrightnessValuesError object. However, since no photocell is supported, the entered values for 'photocellLevelDown' and 'photocellLevelUp' for the various 'lightOutputs' are meaningless. <Parameter Type> Configuration <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.7.7"
    ],
    null,
    null,
    null,
    null
  ]
}
  • ITE public NTCIP working repository MIBs · Publisher's source file: NTCIP-1203 — NTCIP1203-Dms.mib

    Module: NTCIP1203-Dms

    See published definition above

    Module imports
    {'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.7.7, but its DESCRIPTION explicitly lists 1.3.6.1.4.1.1206.4.2.3.7.7. 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.mib
Records for description 2NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 2

dmsIllumBrightnessValues · mandatoryNTCIP published standard MIB annexes (reviewed modules)1 source

Status in source: mandatory.

Names: dmsIllumBrightnessValues

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dmsIllumBrightnessValues",
    "OBJECT-TYPE",
    "SYNTAX",
    "OCTET",
    "STRING",
    "ACCESS",
    "read-write",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition> . An OCTET STRING describing the sign's light output in relationship to the Photocell(s) detection of ambient light. For each light output level, there is a corresponding range of photocell levels. The number of light output levels transmitted is defined by the first byte of the data packet, but cannot exceed the value of the dmsIllumNumBrightLevels object. Setting the value of this object to a non-supported or erroneous value shall lead to a genErr. Cause of this error shall be denoted by the dmsIllumBrightnessValuesError object. After a SET, an implementation may interpolate these entries to create a table with as many entries as needed, but the value of the object shall not be affected by such interpolations. For each light output level, there are three 16-bit values that occur in the following order: Light output level, Photocell level down, Photocell level up. The light output level is a value between 0 (no light output) and 65535 (maximum light output). Each step is 1/65535 of the maximum light output (linear scale). The Photocell-level-down is the lowest photocell level allowed to maintain the light output level. If the photocell level goes below this point, the light output level goes down one light output level. The Photocell-level-up is the highest photocell level for this light output level. If the photocell level goes above this point, the light output level goes up one light output level. The photocell level (Up and Down) values may not exceed the value of the dmsIllumMaxPhotocellLevel object. The points transmitted should be selected so that there is no photocell level which does not have a light output level. Hysteresis is possible by defining the photocell-level-up at a level higher than the upper level's photocell- level-down. The encoding of the structure shall consist of a one byte integer value indicating the number of rows in the table. This is followed by a series of OER encoded Strings of the following structure: SEQUENCE { lightOutput INTEGER (0..65535), photocellLevelDown INTEGER (0..65535), photocellLevelUp INTEGER (0..65535) } If the sign does not support photocell and the dmsIllumControl object value is set to 'manualIndexed', then the values for the 'photocellLevelDown' and 'photocellLevelUp' still need to be entered that the table does not cause any errors as defined in the dmsIllumBrightnessValuesError object. However, since no photocell is supported, the entered values for 'photocellLevelDown' and 'photocellLevelUp' for the various 'lightOutputs' are meaningless. <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.7.7\"",
    "::=",
    "{",
    "illum",
    "7",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "OCTET STRING"
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition> . An OCTET STRING describing the sign's light output in relationship to the Photocell(s) detection of ambient light. For each light output level, there is a corresponding range of photocell levels. The number of light output levels transmitted is defined by the first byte of the data packet, but cannot exceed the value of the dmsIllumNumBrightLevels object. Setting the value of this object to a non-supported or erroneous value shall lead to a genErr. Cause of this error shall be denoted by the dmsIllumBrightnessValuesError object. After a SET, an implementation may interpolate these entries to create a table with as many entries as needed, but the value of the object shall not be affected by such interpolations. For each light output level, there are three 16-bit values that occur in the following order: Light output level, Photocell level down, Photocell level up. The light output level is a value between 0 (no light output) and 65535 (maximum light output). Each step is 1/65535 of the maximum light output (linear scale). The Photocell-level-down is the lowest photocell level allowed to maintain the light output level. If the photocell level goes below this point, the light output level goes down one light output level. The Photocell-level-up is the highest photocell level for this light output level. If the photocell level goes above this point, the light output level goes up one light output level. The photocell level (Up and Down) values may not exceed the value of the dmsIllumMaxPhotocellLevel object. The points transmitted should be selected so that there is no photocell level which does not have a light output level. Hysteresis is possible by defining the photocell-level-up at a level higher than the upper level's photocell- level-down. The encoding of the structure shall consist of a one byte integer value indicating the number of rows in the table. This is followed by a series of OER encoded Strings of the following structure: SEQUENCE { lightOutput INTEGER (0..65535), photocellLevelDown INTEGER (0..65535), photocellLevelUp INTEGER (0..65535) } If the sign does not support photocell and the dmsIllumControl object value is set to 'manualIndexed', then the values for the 'photocellLevelDown' and 'photocellLevelUp' still need to be entered that the table does not cause any errors as defined in the dmsIllumBrightnessValuesError object. However, since no photocell is supported, the entered values for 'photocellLevelDown' and 'photocellLevelUp' for the various 'lightOutputs' are meaningless. <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.7.7"
    ],
    null,
    null,
    null,
    null
  ]
}
Records for description 3ITE public NTCIP working repository MIBs1 record · 1 source

Description 3

dmsIllumBrightnessValues · mandatoryITE public NTCIP working repository MIBs1 source

Status in source: mandatory.

Names: dmsIllumBrightnessValues

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dmsIllumBrightnessValues",
    "OBJECT-TYPE",
    "SYNTAX",
    "OCTET",
    "STRING",
    "ACCESS",
    "read-write",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition> . An OCTET STRING describing the sign's light output in relationship to the Photocell(s) detection of ambient light. For each light output level, there is a corresponding range of photocell levels. The number of light output levels transmitted is defined by the first byte of the data packet, but cannot exceed the value of the dmsIllumNumBrightLevels object. Setting the value of this object to a non-supported or erroneous value shall lead to a genErr. Cause of this error shall be denoted by the dmsIllumBrightnessValuesError object. After a SET, an implementation may interpolate these entries to create a table with as many entries as needed, but the value of the object shall not be affected by such interpolations. For each light output level, there are three 16-bit values that occur in the following order: Light output level, Photocell level down, Photocell level up. The light output level is a value between 0 (no light output) and 65535 (maximum light output). Each step is 1/65535 of the maximum light output (linear scale). The Photocell-level-down is the lowest photocell level allowed to maintain the light output level. If the photocell level goes below this point, the light output level goes down one light output level. The Photocell-level-up is the highest photocell level for this light output level. If the photocell level goes above this point, the light output level goes up one light output level. The photocell level (Up and Down) values may not exceed the value of the dmsIllumMaxPhotocellLevel object. The points transmitted should be selected so that there is no photocell level which does not have a light output level. Hysteresis is possible by defining the photocell-level-up at a level higher than the upper level's photocell-level-down. The encoding of the structure shall consist of a one byte integer value indicating the number of rows in the table. This is followed by a series of OER encoded Strings of the following structure: SEQUENCE { lightOutput INTEGER (0..65535), photocellLevelDown INTEGER (0..65535), photocellLevelUp INTEGER (0..65535) } If the sign does not support photocell and the dmsIllumControl object value is set to 'manualIndexed', then the values for the 'photocellLevelDown' and 'photocellLevelUp' still need to be entered that the table does not cause any errors as defined in the dmsIllumBrightnessValuesError object. However, since no photocell is supported, the entered values for 'photocellLevelDown' and 'photocellLevelUp' for the various 'lightOutputs' are meaningless. <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.7.7\"",
    "::=",
    "{",
    "illum",
    "7",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "OCTET STRING"
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition> . An OCTET STRING describing the sign's light output in relationship to the Photocell(s) detection of ambient light. For each light output level, there is a corresponding range of photocell levels. The number of light output levels transmitted is defined by the first byte of the data packet, but cannot exceed the value of the dmsIllumNumBrightLevels object. Setting the value of this object to a non-supported or erroneous value shall lead to a genErr. Cause of this error shall be denoted by the dmsIllumBrightnessValuesError object. After a SET, an implementation may interpolate these entries to create a table with as many entries as needed, but the value of the object shall not be affected by such interpolations. For each light output level, there are three 16-bit values that occur in the following order: Light output level, Photocell level down, Photocell level up. The light output level is a value between 0 (no light output) and 65535 (maximum light output). Each step is 1/65535 of the maximum light output (linear scale). The Photocell-level-down is the lowest photocell level allowed to maintain the light output level. If the photocell level goes below this point, the light output level goes down one light output level. The Photocell-level-up is the highest photocell level for this light output level. If the photocell level goes above this point, the light output level goes up one light output level. The photocell level (Up and Down) values may not exceed the value of the dmsIllumMaxPhotocellLevel object. The points transmitted should be selected so that there is no photocell level which does not have a light output level. Hysteresis is possible by defining the photocell-level-up at a level higher than the upper level's photocell-level-down. The encoding of the structure shall consist of a one byte integer value indicating the number of rows in the table. This is followed by a series of OER encoded Strings of the following structure: SEQUENCE { lightOutput INTEGER (0..65535), photocellLevelDown INTEGER (0..65535), photocellLevelUp INTEGER (0..65535) } If the sign does not support photocell and the dmsIllumControl object value is set to 'manualIndexed', then the values for the 'photocellLevelDown' and 'photocellLevelUp' still need to be entered that the table does not cause any errors as defined in the dmsIllumBrightnessValuesError object. However, since no photocell is supported, the entered values for 'photocellLevelDown' and 'photocellLevelUp' for the various 'lightOutputs' are meaningless. <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.7.7"
    ],
    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
Records for description 4NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 4

dmsIllumBrightnessValues · mandatoryNTCIP published standard MIB annexes (reviewed modules)1 source

Status in source: mandatory.

Names: dmsIllumBrightnessValues

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dmsIllumBrightnessValues",
    "OBJECT-TYPE",
    "SYNTAX",
    "OCTET",
    "STRING",
    "ACCESS",
    "read-write",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "“",
    "An",
    "OCTET",
    "STRING",
    "describing",
    "the",
    "sign",
    "'",
    "s",
    "Brightness",
    "Level",
    "in",
    "relationship",
    "to",
    "the",
    "Photocell",
    "(",
    "s",
    ")",
    "detection",
    "of",
    "ambient",
    "light",
    ".",
    "For",
    "each",
    "brightness",
    "level",
    ",",
    "there",
    "is",
    "a",
    "corresponding",
    "range",
    "of",
    "photocell",
    "levels",
    ".",
    "The",
    "number",
    "of",
    "levels",
    "transmitted",
    "is",
    "defined",
    "by",
    "the",
    "first",
    "byte",
    "of",
    "the",
    "datapacket",
    ",",
    "but",
    "cannot",
    "exceed",
    "the",
    "value",
    "of",
    "the",
    "dmsIllumNumBrightLevels",
    "object",
    ".",
    [
      "literal",
      "22"
    ],
    "::=",
    "{",
    "illum",
    "7",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "OCTET STRING"
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "An OCTET STRING describing the sign's Brightness Level in relationship to the Photocell(s) detection of ambient light. For each brightness level, there is a corresponding range of photocell levels. The number of levels transmitted is defined by the first byte of the datapacket, but cannot exceed the value of the dmsIllumNumBrightLevels object."
    ],
    null,
    null,
    null,
    null
  ]
}
  • NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1203:1997, Object Definitions for Dynamic Message Signs (DMS) Published December 1999 (superceded by NTCIP 1203 v02) — original PDF · Official record

    Module: DMS-MIB

    See published definition above

    Module imports
    {'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.

    Related ASN.1 definitions
    nema                     OBJECT IDENTIFIER ::= { enterprises 1206 }
    nemaExperimental         OBJECT IDENTIFIER ::= { nema 2 }
    · Download NTCIP1203v0115a.pdf — DMS-MIB (MIB transcription)
Records for description 5NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 5

dmsIllumBrightnessValues · mandatoryNTCIP published standard MIB annexes (reviewed modules)1 source

Status in source: mandatory.

Names: dmsIllumBrightnessValues

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dmsIllumBrightnessValues",
    "OBJECT-TYPE",
    "SYNTAX",
    "OCTET",
    "STRING",
    "ACCESS",
    "read-write",
    "Page",
    "184",
    "NTCIP",
    "1203",
    "v02",
    ".",
    "35",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition> For additional information see Annex E - Frequently Asked Questions section, questions 8 and 9. An OCTET STRING describing the sign's light output in relationship to the Photocell(s) detection of ambient light. For each light output level, there is a corresponding range of photocell levels. The number of light output levels transmitted is defined by the first byte of the data packet, but cannot exceed the value of the dmsIllumNumBrightLevels object. Setting the value of this object to a non-supported or erroneous value shall lead to a genErr. Cause of this error shall be denoted by the dmsIllumBrightnessValuesError object. After a SET, an implementation may interpolate these entries to create a table with as many entries as needed, but the value of the object shall not be affected by such interpolations. For each light output level, there are three 16-bit values that occur in the following order: Light output level, Photocell level down, Photocell level up. The light output level is a value between 0 (no light output) and 65535 (maximum light output). Each step is 1/65535 of the maximum light output (linear scale). The Photocell-level-down is the lowest photocell level allowed to maintain the light output level. Should the photocell level go below this point, the light output level would go down one light output level. The Photocell-level-up is the highest photocell level for this light output level. Should the photocell level go above this point, the light output level would go up one light output level. The photocell level (Up and Down) values may not exceed the value of the dmsIllumMaxPhotocellLevel object. The points transmitted should be selected so that there is no photocell level which does not have a light output level. Hysteresis is possible by defining the photocell-level-up at a level higher than the upper level's photocell- level-down. The encoding of the structure shall consist of a one byte integer value indicating the number of rows in the table. This will be followed by a series of OER encoded Strings of the following structure: SEQUENCE { lightOutput INTEGER (0..65535), photocellLevelDown INTEGER (0..65535), photocellLevelUp INTEGER (0..65535) } If the sign does not support photocell and the dmsIllumControl object value is set to 'manualIndexed', then the values for the 'photocellLevelDown' and 'photocellLevelUp' still need to be entered that the table does not cause any errors as defined in the dmsIllumBrightnessValuesError object. However, since no photocell is supported, the entered values for 'photocellLevelDown' and 'photocellLevelUp' for the various 'lightOutputs' are meaningless. <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.7.7\"",
    "::=",
    "{",
    "illum",
    "7",
    "}"
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1206)

Schopp Bruce J.

Siblings (8)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.1206.4.2.3.7.1 dmsIllumControl00
1.3.6.1.4.1.1206.4.2.3.7.2 dmsIllumMaxPhotocellLevel00
1.3.6.1.4.1.1206.4.2.3.7.3 dmsIllumPhotocellLevelStatus00
1.3.6.1.4.1.1206.4.2.3.7.4 dmsIllumNumBrightLevels00
1.3.6.1.4.1.1206.4.2.3.7.5 dmsIllumBrightLevelStatus00
1.3.6.1.4.1.1206.4.2.3.7.6 dmsIllumManLevel00
1.3.6.1.4.1.1206.4.2.3.7.8 dmsIllumBrightnessValuesError00
1.3.6.1.4.1.1206.4.2.3.7.9 dmsIllumLightOutputStatus00