OID reference

pixelFailureDetectionType

1.3.6.1.4.1.1206.4.2.6.9.7.3.1.1

Description

<Definition> Indicates the type of test/display that leads to the pixel failure entry. Once a pixel is detected as failed, it is entered in the table with a type of either pixelTest or messageDisplay. In either case the failed pixel stays in the table until pixelTestActivation is set to either test or clearTable. <For…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.1206.4.2.6.9.7.3.1 (pixelFailureEntry)
Node code
1
Node name
pixelFailureDetectionType
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.1206.4.2.6.9.7.3.1.1
URN notation
urn:oid:1.3.6.1.4.1.1206.4.2.6.9.7.3.1.1
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) global(6) globalV2(9) statError(7) pixelFailureTable(3) pixelFailureEntry(1) pixelFailureDetectionType(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) global(6) dmsStatus(9) statError(7) pixelFailureTable(3) pixelFailureEntry(1) pixelFailureDetectionType(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dms(6) globalV2(9) statError(7) pixelFailureTable(3) pixelFailureEntry(1) pixelFailureDetectionType(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dms(6) dmsStatus(9) statError(7) pixelFailureTable(3) pixelFailureEntry(1) pixelFailureDetectionType(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) global(6) globalV2(9) statError(7) pixelFailureTable(3) pixelFailureEntry(1) pixelFailureDetectionType(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) global(6) dmsStatus(9) statError(7) pixelFailureTable(3) pixelFailureEntry(1) pixelFailureDetectionType(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dms(6) globalV2(9) statError(7) pixelFailureTable(3) pixelFailureEntry(1) pixelFailureDetectionType(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dms(6) dmsStatus(9) statError(7) pixelFailureTable(3) pixelFailureEntry(1) pixelFailureDetectionType(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) global(6) globalV2(9) statError(7) pixelFailureTable(3) pixelFailureEntry(1) pixelFailureDetectionType(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) global(6) dmsStatus(9) statError(7) pixelFailureTable(3) pixelFailureEntry(1) pixelFailureDetectionType(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) dms(6) globalV2(9) statError(7) pixelFailureTable(3) pixelFailureEntry(1) pixelFailureDetectionType(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) dms(6) dmsStatus(9) statError(7) pixelFailureTable(3) pixelFailureEntry(1) pixelFailureDetectionType(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) global(6) globalV2(9) statError(7) pixelFailureTable(3) pixelFailureEntry(1) pixelFailureDetectionType(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) global(6) dmsStatus(9) statError(7) pixelFailureTable(3) pixelFailureEntry(1) pixelFailureDetectionType(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) dms(6) globalV2(9) statError(7) pixelFailureTable(3) pixelFailureEntry(1) pixelFailureDetectionType(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) dms(6) dmsStatus(9) statError(7) pixelFailureTable(3) pixelFailureEntry(1) pixelFailureDetectionType(1)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/1206/4/2/6/9/7/3/1/1
  • /ISO/Identified-Organization/6/1/4/1/1206/4/2/6/9/7/3/1/1
  • /ISO/3/6/1/4/1/1206/4/2/6/9/7/3/1/1
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/global/globalV2/statError/pixelFailureTable/pixelFailureEntry/pixelFailureDetectionType
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/global/dmsStatus/statError/pixelFailureTable/pixelFailureEntry/pixelFailureDetectionType
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/dms/globalV2/statError/pixelFailureTable/pixelFailureEntry/pixelFailureDetectionType
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/dms/dmsStatus/statError/pixelFailureTable/pixelFailureEntry/pixelFailureDetectionType
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/global/globalV2/statError/pixelFailureTable/pixelFailureEntry/pixelFailureDetectionType
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/global/dmsStatus/statError/pixelFailureTable/pixelFailureEntry/pixelFailureDetectionType
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/dms/globalV2/statError/pixelFailureTable/pixelFailureEntry/pixelFailureDetectionType
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/dms/dmsStatus/statError/pixelFailureTable/pixelFailureEntry/pixelFailureDetectionType
  • /iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/global/globalV2/statError/pixelFailureTable/pixelFailureEntry/pixelFailureDetectionType
  • /iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/global/dmsStatus/statError/pixelFailureTable/pixelFailureEntry/pixelFailureDetectionType
  • /iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/dms/globalV2/statError/pixelFailureTable/pixelFailureEntry/pixelFailureDetectionType
  • /iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/dms/dmsStatus/statError/pixelFailureTable/pixelFailureEntry/pixelFailureDetectionType
  • /iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/global/globalV2/statError/pixelFailureTable/pixelFailureEntry/pixelFailureDetectionType
  • /iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/global/dmsStatus/statError/pixelFailureTable/pixelFailureEntry/pixelFailureDetectionType
  • /iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/dms/globalV2/statError/pixelFailureTable/pixelFailureEntry/pixelFailureDetectionType
  • /iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/dms/dmsStatus/statError/pixelFailureTable/pixelFailureEntry/pixelFailureDetectionType
  • Additional combinations skipped.

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
read-only
Status in MIB
current

Enumerated values

Notes below names come from selected MIB definitions.

ValueName and source notes
1other
deprecated
2pixelTest
3messageDisplay

Using this OID with SNMP

At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition.

In NTCIP1203-Dms, the row index consists of these components in order:

  1. pixelFailureDetectionType (INTEGER): one numeric subidentifier for the non-negative value.
  2. pixelFailureIndex (Integer32): one numeric subidentifier for the non-negative value.

An instance has the form .1.3.6.1.4.1.1206.4.2.6.9.7.3.1.1.<pixelFailureDetectionType>.<pixelFailureIndex>. Use values present on the device and permitted by its MIB. Other definitions can differ.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.1206.4.2.6.9.7.3.1.1

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.

The displayed source records contain one distinct definition. Compare its source records.

pixelFailureDetectionType  OBJECT-TYPE 
SYNTAX      INTEGER {
                 other (1), -- deprecated 
                 pixelTest (2),
                 messageDisplay(3) } 
MAX-ACCESS  read-only 
STATUS      current  
DESCRIPTION  
"<Definition> Indicates the type of test/display that leads to the pixel 
failure entry.
Once a pixel is detected as failed, it is entered in the table with a type of 
either pixelTest or messageDisplay. In either case the failed pixel stays in 
the table until pixelTestActivation is set to either test or clearTable. 
<Format>
Detection type pixelTest and messageDisplay are considered different methods 
of testing for failed pixels. 
other: Not defined by this document; this value was deprecated in NTCIP 1203 
    v02.
pixelTest: This is considered a foreground processing method of failed pixel 
    detection. Failed pixels detected during a foreground pixel test are 
    entered in the pixelTest pixel failure type. During a foreground pixel 
    test, the message on the display may or may not stay present on the 
    display. 
messageDisplay: This is considered a background processing method of failed 
    pixel detection. During a background test, the readability/legibility of 
    the message shall not be affected by the test. If the manufacturer 
    supports background pixel test, failed pixels detected during a 
    background pixel test are entered in the messageDisplay pixel failure 
    type.
<Informative> In v02, the enumerated value of 'other' was deprecated to 
improve interoperability.
<Parameter Type> Status
<Object Identifier> 1.3.6.1.4.1.1206.4.2.3.9.7.3.1.1"
::= { pixelFailureEntry 1 }

Meaning

Descriptions

1 unique

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

<Definition> Indicates the type of test/display that leads to the pixel failure entry. Once a pixel is detected as failed, it is entered in the table with a type of either pixelTest or messageDisplay. In either case the failed pixel stays in the table until pixelTestActivation is set to either test or clearTable. <Format> Detection type pixelTest and messageDisplay are considered different methods of testing for failed pixels. other: Not defined by this document; this value was deprecated in NTCIP 1203 v02. pixelTest: This is considered a foreground processing method of failed pixel detection. Failed pixels detected during a foreground pixel test are entered in the pixelTest pixel failure type. During a foreground pixel test, the message on the display may or may not stay present on the display. messageDisplay: This is considered a background processing method of failed pixel detection. During a background test, the readability/legibility of the message shall not be affected by the test. If the manufacturer supports background pixel test, failed pixels detected during a background pixel test are entered in the messageDisplay pixel failure type. <Informative> In v02, the enumerated value of 'other' was deprecated to improve interoperability. <Parameter Type> Status <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.9.7.3.1.1

Sources for this description

ITE public NTCIP working repository MIBs

See 1 matching source record

Evidence

Source records

1 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

pixelFailureDetectionType · unconfirmedITE public NTCIP working repository MIBs1 source

Status in source: unconfirmed.

Names: pixelFailureDetectionType

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "pixelFailureDetectionType",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "other",
    "(",
    "1",
    ")",
    ",",
    "pixelTest",
    "(",
    "2",
    ")",
    ",",
    "messageDisplay",
    "(",
    "3",
    ")",
    "}",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"<Definition> Indicates the type of test/display that leads to the pixel failure entry. Once a pixel is detected as failed, it is entered in the table with a type of either pixelTest or messageDisplay. In either case the failed pixel stays in the table until pixelTestActivation is set to either test or clearTable. <Format> Detection type pixelTest and messageDisplay are considered different methods of testing for failed pixels. other: Not defined by this document; this value was deprecated in NTCIP 1203 v02. pixelTest: This is considered a foreground processing method of failed pixel detection. Failed pixels detected during a foreground pixel test are entered in the pixelTest pixel failure type. During a foreground pixel test, the message on the display may or may not stay present on the display. messageDisplay: This is considered a background processing method of failed pixel detection. During a background test, the readability/legibility of the message shall not be affected by the test. If the manufacturer supports background pixel test, failed pixels detected during a background pixel test are entered in the messageDisplay pixel failure type. <Informative> In v02, the enumerated value of 'other' was deprecated to improve interoperability. <Parameter Type> Status <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.9.7.3.1.1\"",
    "::=",
    "{",
    "pixelFailureEntry",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "other",
            1
          ],
          [
            "pixelTest",
            2
          ],
          [
            "messageDisplay",
            3
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "<Definition> Indicates the type of test/display that leads to the pixel failure entry. Once a pixel is detected as failed, it is entered in the table with a type of either pixelTest or messageDisplay. In either case the failed pixel stays in the table until pixelTestActivation is set to either test or clearTable. <Format> Detection type pixelTest and messageDisplay are considered different methods of testing for failed pixels. other: Not defined by this document; this value was deprecated in NTCIP 1203 v02. pixelTest: This is considered a foreground processing method of failed pixel detection. Failed pixels detected during a foreground pixel test are entered in the pixelTest pixel failure type. During a foreground pixel test, the message on the display may or may not stay present on the display. messageDisplay: This is considered a background processing method of failed pixel detection. During a background test, the readability/legibility of the message shall not be affected by the test. If the manufacturer supports background pixel test, failed pixels detected during a background pixel test are entered in the messageDisplay pixel failure type. <Informative> In v02, the enumerated value of 'other' was deprecated to improve interoperability. <Parameter Type> Status <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.9.7.3.1.1"
    ],
    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.9.7.3.1.1, but its DESCRIPTION explicitly lists 1.3.6.1.4.1.1206.4.2.3.9.7.3.1.1. 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

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1206)

Schopp Bruce J.

Siblings (4)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.1206.4.2.6.9.7.3.1.2 pixelFailureIndex00
1.3.6.1.4.1.1206.4.2.6.9.7.3.1.3 pixelFailureXLocation00
1.3.6.1.4.1.1206.4.2.6.9.7.3.1.4 pixelFailureYLocation00
1.3.6.1.4.1.1206.4.2.6.9.7.3.1.5 pixelFailureStatus00