pixelFailureStatus

Status in source: mandatory.

Names: pixelFailureStatus

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "pixelFailureStatus",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "(",
    "0",
    ".",
    ".",
    "255",
    ")",
    "ACCESS",
    "read-only",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition> Indicates the current status of the specified pixel and the operation which made this determination. This is a bit field with the following format: <Format> Bit 0: 0: Not stuck on / 1: Stuck On Bit 1: 0: No Color Error / 1: Color Error Bit 2: 0: no electrical error / 1: electrical error Bit 3: 0: no mechanical error / 1: mechanical error Bit 4: 0: Not stuck off / 1: Stuck off Bit 5: 0: No partial failure / 1: Partial failure - a partial failure indicates a loss of pixel functionality that does not affect the full luminance or visible area of a pixel. For example, if an LED DMS uses multiple redundant LEDs at each pixel, the failure of a single LED at a given pixel would be flagged as a partial failure. A partial failure indicates that the pixel is still functioning, but with reduced visibility. <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.9.7.3.1.5\"",
    "::=",
    "{",
    "pixelFailureEntry",
    "5",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "integerSubType",
        [
          [
            0,
            255
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition> Indicates the current status of the specified pixel and the operation which made this determination. This is a bit field with the following format: <Format> Bit 0: 0: Not stuck on / 1: Stuck On Bit 1: 0: No Color Error / 1: Color Error Bit 2: 0: no electrical error / 1: electrical error Bit 3: 0: no mechanical error / 1: mechanical error Bit 4: 0: Not stuck off / 1: Stuck off Bit 5: 0: No partial failure / 1: Partial failure - a partial failure indicates a loss of pixel functionality that does not affect the full luminance or visible area of a pixel. For example, if an LED DMS uses multiple redundant LEDs at each pixel, the failure of a single LED at a given pixel would be flagged as a partial failure. A partial failure indicates that the pixel is still functioning, but with reduced visibility. <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.9.7.3.1.5"
    ],
    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

  Related source files and packages:

  • NTCIP 8004 v02 (2010) — normative namespace, pages 43–44
  • RFC 1155 — original SMI enterprise namespace
• NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1203 v03, Object Definitions for Dynamic Message Signs (DMS) Published September 2014 — original PDF · Official record

  Module: NTCIP1203-v03-05

  See published definition above

  Module imports

  {'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:

  • NTCIP 1203 v03, Object Definitions for Dynamic Message Signs (DMS) Published September 2014 — original PDF
  • NTCIP8004-NEMA.mib — ITE namespace dependency
  • NTCIP8004-Transportation.mib — ITE namespace dependency
• NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1203 v02, Object Definitins for Dynamic Message Signs (DMS) – Version 02 Published March 2007 (superceded by NTCIP 1203 v03) — original PDF · Official record

  Module: NTCIP1203-2005

  Same published definition

  Module imports

  {'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)

  Related source files and packages:

  • NTCIP 1203 v02, Object Definitins for Dynamic Message Signs (DMS) – Version 02 Published March 2007 (superceded by NTCIP 1203 v03) — original PDF

Status in source: unconfirmed.

Names: pixelFailureStatus

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "pixelFailureStatus",
    "OBJECT-TYPE",
    "SYNTAX",
    "NtcipIntegerBitmap8",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"<Definition> Indicates the current status of the specified pixel and the operation which made this determination. This is a bit field with the following format: <Format> Bit 0: 0: Not stuck on / 1: Stuck On Bit 1: 0: No Color Error / 1: Color Error Bit 2: 0: no electrical error / 1: electrical error Bit 3: 0: no mechanical error / 1: mechanical error Bit 4: 0: Not stuck off / 1: Stuck off Bit 5: 0: No partial failure / 1: Partial failure - a partial failure indicates a loss of pixel functionality that does not affect the full luminance or visible area of a pixel. For example, if an LED DMS uses multiple redundant LEDs at each pixel, the failure of a single LED at a given pixel would be flagged as a partial failure. A partial failure indicates that the pixel is still functioning, but with reduced visibility. <Parameter Type> Status <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.9.7.3.1.5\"",
    "::=",
    "{",
    "pixelFailureEntry",
    "5",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "NtcipIntegerBitmap8"
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "<Definition> Indicates the current status of the specified pixel and the operation which made this determination. This is a bit field with the following format: <Format> Bit 0: 0: Not stuck on / 1: Stuck On Bit 1: 0: No Color Error / 1: Color Error Bit 2: 0: no electrical error / 1: electrical error Bit 3: 0: no mechanical error / 1: mechanical error Bit 4: 0: Not stuck off / 1: Stuck off Bit 5: 0: No partial failure / 1: Partial failure - a partial failure indicates a loss of pixel functionality that does not affect the full luminance or visible area of a pixel. For example, if an LED DMS uses multiple redundant LEDs at each pixel, the failure of a single LED at a given pixel would be flagged as a partial failure. A partial failure indicates that the pixel is still functioning, but with reduced visibility. <Parameter Type> Status <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.9.7.3.1.5"
    ],
    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.5, but its DESCRIPTION explicitly lists 1.3.6.1.4.1.1206.4.2.3.9.7.3.1.5. 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

Status in source: mandatory.

Names: pixelFailureStatus

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "pixelFailureStatus",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "(",
    "0",
    ".",
    ".",
    "255",
    ")",
    "ACCESS",
    "read-only",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "“",
    "Indicates",
    "the",
    "current",
    "status",
    "of",
    "the",
    "specified",
    "pixel",
    "and",
    "the",
    "operation",
    "which",
    "made",
    "this",
    "determination",
    ".",
    "This",
    "is",
    "a",
    "bit",
    "field",
    "with",
    "the",
    "following",
    "format",
    ":",
    "Bit",
    "0",
    "0",
    ":",
    "Stuck",
    "Off",
    "/",
    "1",
    ":",
    "Stuck",
    "On",
    "Bit",
    "1",
    "0",
    ":",
    "No",
    "Color",
    "Error",
    "/",
    "1",
    ":",
    "Color",
    "Error",
    "Bit",
    "2",
    "0",
    ":",
    "no",
    "electrical",
    "error",
    "/",
    "1",
    ":",
    "electrical",
    "error",
    "Bit",
    "3",
    "0",
    ":",
    "no",
    "mechanical",
    "error",
    "/",
    "1",
    ":",
    "mechanical",
    "error",
    "“",
    "::=",
    "{",
    "pixelFailureEntry",
    "5",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "integerSubType",
        [
          [
            0,
            255
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "Indicates the current status of the specified pixel and the operation which made this determination. This is a bit field with the following format: Bit 0 0: Stuck Off / 1: Stuck On Bit 1 0: No Color Error / 1: Color Error Bit 2 0: no electrical error / 1: electrical error Bit 3 0: no mechanical error / 1: mechanical error"
    ],
    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)

  Related source files and packages:

  • NTCIP 1203:1997, Object Definitions for Dynamic Message Signs (DMS) Published December 1999 (superceded by NTCIP 1203 v02) — original PDF
  • NTCIP 1101:1996 — original NEMA_SMI namespace transcription
  • NTCIP 1101:1996 — original NEMA namespace PDF, pages 21 and 41

  Show more related files and packages

  • NTCIP 1201 v03 — original compatibility discussion PDF, page 41