OID reference

patternTableType

1.3.6.1.4.1.1206.4.2.1.4.6

Description

<Definition> This object provides information about any special organizational structure required for the pattern table. The defined structures are as follows: other: The pattern table setup is not described in this standard, refer to device manual. patterns: Each row of the pattern table represents a unique pattern a…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.1206.4.2.1.4 (coord)
Node code
6
Node name
patternTableType
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.1206.4.2.1.4.6
URN notation
urn:oid:1.3.6.1.4.1.1206.4.2.1.4.6
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

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

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
read-only
Status in MIB
optional, mandatory

Definitions may combine these properties differently.

Compare 2 source variants

Variant 1 — NTCIP published standard MIB annexes (reviewed modules)

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

Variant 2 — NTCIP published standard MIB annexes (reviewed modules)

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

Enumerated values

Numbers refer to source variants above. Each value is shown only for variants that define it.

ValueNameSource variants
1other1, 2
2patterns1, 2
3offset31, 2
4offset51, 2

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

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

Available source records contain 4 distinct definitions; some records may not include a definition.

Show 4 published definitions

patternTableType · optional

patternTableType   OBJECT-TYPE
   SYNTAX   INTEGER { other (1),
                     patterns (2),
                     offset3 (3),
                     offset5 (4) }
   ACCESS   read-only
   STATUS   optional
   DESCRIPTION
      "<Definition> This object provides information about
       any special organizational structure required for
       the pattern table. The defined structures are as
       follows:
          other: The pattern table setup is not described
             in this standard, refer to device manual.
          patterns: Each row of the pattern table
             represents a unique pattern and has no
             dependencies on other rows.
          offset3: The pattern table is organized into
             plans which have three offsets. Each plan
             uses three consecutive rows. Only
             patternOffsetTime and patternSequenceNumber
             values may vary between each of the three rows.
             Plan 1 is contained in rows 1, 2 and 3, Plan 2
             is contained in rows 4, 5 and 6, Plan 3 is in
             rows 7, 8 and 9, etc.




                                                                                          

                      
       

          offset5: The pattern table is organized into
             plans which have five offsets. Each plan
             occupies five consecutive rows. Only
             patternOffsetTime and patternSequenceNumber
             values may vary between each of the rows.
             Plan 1 is contained in rows 1, 2, 3, 4 and
             5, Plan 2 is contained in rows 6, 7, 8, 9 and
             10, Plan 3 is contained in rows 11, 12, 13, 14
             and 15, etc.
       <DescriptiveName> NTCIP-1202::ASC.patternTableType
       <DataConceptType> Data Element"
   REFERENCE
      "NEMA TS 2 Clause 3.6.2.1 and 3.6.2.2"
::= { coord 6 }

patternTableType · mandatory

patternTableType   OBJECT-TYPE
      SYNTAX INTEGER { other (1),
            patterns (2),
            offset3 (3),
            offset5 (4) }
      ACCESS read-only
      STATUS mandatory
      DESCRIPTION "<Definition> This object provides information about any
            special organizational structure required for the pattern table.
            The defined structures are as follows:
            other: The pattern table setup is not described in this standard,
            refer to device manual.
            patterns: Each row of the pattern table represents a unique
            pattern and has no dependencies on other rows.



                                                                                        

                  
        

            offset3: The pattern table is organized into plans which have
            three offsets. Each plan uses three consecutive rows. Only
            patternOffsetTime and patternSequenceNumber values may vary
            between each of the three rows. Plan 1 is contained in rows 1, 2
            and 3, Plan 2 is contained in rows 4, 5 and 6, Plan 3 is in rows
            7, 8 and 9, etc.
            offset5: The pattern table is organized into plans which have
            five offsets. Each plan occupies five consecutive rows. Only
            patternOffsetTime and patternSequenceNumber values may vary
            between each of the rows. Plan 1 is contained in rows 1, 2, 3, 4
            and 5, Plan 2 is contained in rows 6, 7, 8, 9 and 10, Plan 3 is
            contained in rows 11, 12, 13, 14 and 15, etc.
      <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.4.6"
      REFERENCE "NEMA TS 2 Clause 3.6.2.1 and 3.6.2.2"
::= { coord 6 }

patternTableType · mandatory

patternTableType OBJECT-TYPE
         SYNTAX INTEGER { other (1),
                                  patterns (2),
                                  offset3 (3),
                                  offset5 (4) }
         ACCESS read-only
         STATUS mandatory
         DESCRIPTION
              "This object provides information about any special organizational structure required for the
              pattern table. The defined structures are as follows:
                 other -    The pattern table setup is not described in this standard, refer to device
                            manual.
                 patterns - Each row of the pattern table represents a unique pattern and has no
                            dependencies on other rows.
                 offset3 - The pattern table is organized into plans which have three offsets. Each plan
                            uses three consecutive rows. Only the offsetTime value may vary between
                            each of the three rows. Plan 1 is contained in rows 1, 2 and 3, Plan 2 is
                            contained in rows 4, 5 and 6, Plan 3 is in rows 7, 8 and 9, etc..
                 offset5 - The pattern table is organized into plans which have five offsets. Each plan
                            occupies five consecutive rows. Only the offsetTime value may vary between
                            each of the rows. Plan 1 is contained in rows 1, 2, 3, 4 and 5, Plan 2 is
                            contained in rows , 6,7, 8, 9 and 10, Plan 3 is contained in rows 11, 12, 13, 14
                            and 15, etc..."
         REFERENCE
              "NEMA TS 2 Clause 3.6.2.1 and 3.6.2.2"
::= { coord 6 }

patternTableType · mandatory

patternTableType   OBJECT-TYPE
      SYNTAX INTEGER { other (1),
            patterns (2),
            offset3 (3),
            offset5 (4) }



                                                                                   

                                                                                    
                                                                                   

      ACCESS read-only
      STATUS mandatory
      DESCRIPTION "<Definition> This object provides information about any
            special organizational structure required for the pattern table.
            The defined structures are as follows:
            other: The pattern table setup is not described in this standard,
            refer to device manual.
            patterns: Each row of the pattern table represents a unique
            pattern and has no dependencies on other rows.
            offset3: The pattern table is organized into plans which have
            three offsets. Each plan uses three consecutive rows. Only
            patternOffsetTime and patternSequenceNumber values may vary
            between each of the three rows. Plan 1 is contained in rows 1, 2
            and 3, Plan 2 is contained in rows 4, 5 and 6, Plan 3 is in rows
            7, 8 and 9, etc.
            offset5: The pattern table is organized into plans which have
            five offsets. Each plan occupies five consecutive rows. Only
            patternOffsetTime and patternSequenceNumber values may vary
            between each of the rows. Plan 1 is contained in rows 1, 2, 3, 4
            and 5, Plan 2 is contained in rows 6, 7, 8, 9 and 10, Plan 3 is
            contained in rows 11, 12, 13, 14 and 15, etc.
      <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.4.6
      <Object Type> S"
      REFERENCE "NEMA TS 2 Clause 3.6.2.1 and 3.6.2.2"
::= { coord 6 }

Meaning

Descriptions

4 unique

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

Description 1

<Definition> This object provides information about any special organizational structure required for the pattern table. The defined structures are as follows: other: The pattern table setup is not described in this standard, refer to device manual. patterns: Each row of the pattern table represents a unique pattern and has no dependencies on other rows. offset3: The pattern table is organized into plans which have three offsets. Each plan uses three consecutive rows. Only patternOffsetTime and patternSequenceNumber values may vary between each of the three rows. Plan 1 is contained in rows 1, 2 and 3, Plan 2 is contained in rows 4, 5 and 6, Plan 3 is in rows 7, 8 and 9, etc. offset5: The pattern table is organized into plans which have five offsets. Each plan occupies five consecutive rows. Only patternOffsetTime and patternSequenceNumber values may vary between each of the rows. Plan 1 is contained in rows 1, 2, 3, 4 and 5, Plan 2 is contained in rows 6, 7, 8, 9 and 10, Plan 3 is contained in rows 11, 12, 13, 14 and 15, etc. <DescriptiveName> NTCIP-1202::ASC.patternTableType <DataConceptType> Data Element

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 2

<Definition> This object provides information about any special organizational structure required for the pattern table. The defined structures are as follows: other: The pattern table setup is not described in this standard, refer to device manual. patterns: Each row of the pattern table represents a unique pattern and has no dependencies on other rows. offset3: The pattern table is organized into plans which have three offsets. Each plan uses three consecutive rows. Only patternOffsetTime and patternSequenceNumber values may vary between each of the three rows. Plan 1 is contained in rows 1, 2 and 3, Plan 2 is contained in rows 4, 5 and 6, Plan 3 is in rows 7, 8 and 9, etc. offset5: The pattern table is organized into plans which have five offsets. Each plan occupies five consecutive rows. Only patternOffsetTime and patternSequenceNumber values may vary between each of the rows. Plan 1 is contained in rows 1, 2, 3, 4 and 5, Plan 2 is contained in rows 6, 7, 8, 9 and 10, Plan 3 is contained in rows 11, 12, 13, 14 and 15, etc. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.4.6

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 3

This object provides information about any special organizational structure required for the pattern table. The defined structures are as follows: other - The pattern table setup is not described in this standard, refer to device manual. patterns - Each row of the pattern table represents a unique pattern and has no dependencies on other rows. offset3 - The pattern table is organized into plans which have three offsets. Each plan uses three consecutive rows. Only the offsetTime value may vary between each of the three rows. Plan 1 is contained in rows 1, 2 and 3, Plan 2 is contained in rows 4, 5 and 6, Plan 3 is in rows 7, 8 and 9, etc.. offset5 - The pattern table is organized into plans which have five offsets. Each plan occupies five consecutive rows. Only the offsetTime value may vary between each of the rows. Plan 1 is contained in rows 1, 2, 3, 4 and 5, Plan 2 is contained in rows , 6,7, 8, 9 and 10, Plan 3 is contained in rows 11, 12, 13, 14 and 15, etc...

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 4

<Definition> This object provides information about any special organizational structure required for the pattern table. The defined structures are as follows: other: The pattern table setup is not described in this standard, refer to device manual. patterns: Each row of the pattern table represents a unique pattern and has no dependencies on other rows. offset3: The pattern table is organized into plans which have three offsets. Each plan uses three consecutive rows. Only patternOffsetTime and patternSequenceNumber values may vary between each of the three rows. Plan 1 is contained in rows 1, 2 and 3, Plan 2 is contained in rows 4, 5 and 6, Plan 3 is in rows 7, 8 and 9, etc. offset5: The pattern table is organized into plans which have five offsets. Each plan occupies five consecutive rows. Only patternOffsetTime and patternSequenceNumber values may vary between each of the rows. Plan 1 is contained in rows 1, 2, 3, 4 and 5, Plan 2 is contained in rows 6, 7, 8, 9 and 10, Plan 3 is contained in rows 11, 12, 13, 14 and 15, etc. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.4.6 <Object Type> S

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Evidence

Source records

4 records

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

Records for description 1NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 1

patternTableType · optionalNTCIP published standard MIB annexes (reviewed modules)1 source

Status in source: optional.

Names: patternTableType

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "patternTableType",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "other",
    "(",
    "1",
    ")",
    ",",
    "patterns",
    "(",
    "2",
    ")",
    ",",
    "offset3",
    "(",
    "3",
    ")",
    ",",
    "offset5",
    "(",
    "4",
    ")",
    "}",
    "ACCESS",
    "read-only",
    "STATUS",
    "optional",
    "DESCRIPTION",
    "\"<Definition> This object provides information about any special organizational structure required for the pattern table. The defined structures are as follows: other: The pattern table setup is not described in this standard, refer to device manual. patterns: Each row of the pattern table represents a unique pattern and has no dependencies on other rows. offset3: The pattern table is organized into plans which have three offsets. Each plan uses three consecutive rows. Only patternOffsetTime and patternSequenceNumber values may vary between each of the three rows. Plan 1 is contained in rows 1, 2 and 3, Plan 2 is contained in rows 4, 5 and 6, Plan 3 is in rows 7, 8 and 9, etc. offset5: The pattern table is organized into plans which have five offsets. Each plan occupies five consecutive rows. Only patternOffsetTime and patternSequenceNumber values may vary between each of the rows. Plan 1 is contained in rows 1, 2, 3, 4 and 5, Plan 2 is contained in rows 6, 7, 8, 9 and 10, Plan 3 is contained in rows 11, 12, 13, 14 and 15, etc. <DescriptiveName> NTCIP-1202::ASC.patternTableType <DataConceptType> Data Element\"",
    "REFERENCE",
    "\"NEMA TS 2 Clause 3.6.2.1 and 3.6.2.2\"",
    "::=",
    "{",
    "coord",
    "6",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "other",
            1
          ],
          [
            "patterns",
            2
          ],
          [
            "offset3",
            3
          ],
          [
            "offset5",
            4
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "optional"
    ],
    [
      "DESCRIPTION",
      "<Definition> This object provides information about any special organizational structure required for the pattern table. The defined structures are as follows: other: The pattern table setup is not described in this standard, refer to device manual. patterns: Each row of the pattern table represents a unique pattern and has no dependencies on other rows. offset3: The pattern table is organized into plans which have three offsets. Each plan uses three consecutive rows. Only patternOffsetTime and patternSequenceNumber values may vary between each of the three rows. Plan 1 is contained in rows 1, 2 and 3, Plan 2 is contained in rows 4, 5 and 6, Plan 3 is in rows 7, 8 and 9, etc. offset5: The pattern table is organized into plans which have five offsets. Each plan occupies five consecutive rows. Only patternOffsetTime and patternSequenceNumber values may vary between each of the rows. Plan 1 is contained in rows 1, 2, 3, 4 and 5, Plan 2 is contained in rows 6, 7, 8, 9 and 10, Plan 3 is contained in rows 11, 12, 13, 14 and 15, etc. <DescriptiveName> NTCIP-1202::ASC.patternTableType <DataConceptType> Data Element"
    ],
    [
      "REFERENCE",
      "NEMA TS 2 Clause 3.6.2.1 and 3.6.2.2"
    ],
    null,
    null,
    null
  ]
}
Records for description 2NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 2

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

Status in source: mandatory.

Names: patternTableType

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "patternTableType",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "other",
    "(",
    "1",
    ")",
    ",",
    "patterns",
    "(",
    "2",
    ")",
    ",",
    "offset3",
    "(",
    "3",
    ")",
    ",",
    "offset5",
    "(",
    "4",
    ")",
    "}",
    "ACCESS",
    "read-only",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition> This object provides information about any special organizational structure required for the pattern table. The defined structures are as follows: other: The pattern table setup is not described in this standard, refer to device manual. patterns: Each row of the pattern table represents a unique pattern and has no dependencies on other rows. offset3: The pattern table is organized into plans which have three offsets. Each plan uses three consecutive rows. Only patternOffsetTime and patternSequenceNumber values may vary between each of the three rows. Plan 1 is contained in rows 1, 2 and 3, Plan 2 is contained in rows 4, 5 and 6, Plan 3 is in rows 7, 8 and 9, etc. offset5: The pattern table is organized into plans which have five offsets. Each plan occupies five consecutive rows. Only patternOffsetTime and patternSequenceNumber values may vary between each of the rows. Plan 1 is contained in rows 1, 2, 3, 4 and 5, Plan 2 is contained in rows 6, 7, 8, 9 and 10, Plan 3 is contained in rows 11, 12, 13, 14 and 15, etc. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.4.6\"",
    "REFERENCE",
    "\"NEMA TS 2 Clause 3.6.2.1 and 3.6.2.2\"",
    "::=",
    "{",
    "coord",
    "6",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "other",
            1
          ],
          [
            "patterns",
            2
          ],
          [
            "offset3",
            3
          ],
          [
            "offset5",
            4
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition> This object provides information about any special organizational structure required for the pattern table. The defined structures are as follows: other: The pattern table setup is not described in this standard, refer to device manual. patterns: Each row of the pattern table represents a unique pattern and has no dependencies on other rows. offset3: The pattern table is organized into plans which have three offsets. Each plan uses three consecutive rows. Only patternOffsetTime and patternSequenceNumber values may vary between each of the three rows. Plan 1 is contained in rows 1, 2 and 3, Plan 2 is contained in rows 4, 5 and 6, Plan 3 is in rows 7, 8 and 9, etc. offset5: The pattern table is organized into plans which have five offsets. Each plan occupies five consecutive rows. Only patternOffsetTime and patternSequenceNumber values may vary between each of the rows. Plan 1 is contained in rows 1, 2, 3, 4 and 5, Plan 2 is contained in rows 6, 7, 8, 9 and 10, Plan 3 is contained in rows 11, 12, 13, 14 and 15, etc. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.4.6"
    ],
    [
      "REFERENCE",
      "NEMA TS 2 Clause 3.6.2.1 and 3.6.2.2"
    ],
    null,
    null,
    null
  ]
}
Records for description 3NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 3

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

Status in source: mandatory.

Names: patternTableType

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "patternTableType",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "other",
    "(",
    "1",
    ")",
    ",",
    "patterns",
    "(",
    "2",
    ")",
    ",",
    "offset3",
    "(",
    "3",
    ")",
    ",",
    "offset5",
    "(",
    "4",
    ")",
    "}",
    "ACCESS",
    "read-only",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"This object provides information about any special organizational structure required for the pattern table. The defined structures are as follows: other - The pattern table setup is not described in this standard, refer to device manual. patterns - Each row of the pattern table represents a unique pattern and has no dependencies on other rows. offset3 - The pattern table is organized into plans which have three offsets. Each plan uses three consecutive rows. Only the offsetTime value may vary between each of the three rows. Plan 1 is contained in rows 1, 2 and 3, Plan 2 is contained in rows 4, 5 and 6, Plan 3 is in rows 7, 8 and 9, etc.. offset5 - The pattern table is organized into plans which have five offsets. Each plan occupies five consecutive rows. Only the offsetTime value may vary between each of the rows. Plan 1 is contained in rows 1, 2, 3, 4 and 5, Plan 2 is contained in rows , 6,7, 8, 9 and 10, Plan 3 is contained in rows 11, 12, 13, 14 and 15, etc...\"",
    "REFERENCE",
    "\"NEMA TS 2 Clause 3.6.2.1 and 3.6.2.2\"",
    "::=",
    "{",
    "coord",
    "6",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "other",
            1
          ],
          [
            "patterns",
            2
          ],
          [
            "offset3",
            3
          ],
          [
            "offset5",
            4
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "This object provides information about any special organizational structure required for the pattern table. The defined structures are as follows: other - The pattern table setup is not described in this standard, refer to device manual. patterns - Each row of the pattern table represents a unique pattern and has no dependencies on other rows. offset3 - The pattern table is organized into plans which have three offsets. Each plan uses three consecutive rows. Only the offsetTime value may vary between each of the three rows. Plan 1 is contained in rows 1, 2 and 3, Plan 2 is contained in rows 4, 5 and 6, Plan 3 is in rows 7, 8 and 9, etc.. offset5 - The pattern table is organized into plans which have five offsets. Each plan occupies five consecutive rows. Only the offsetTime value may vary between each of the rows. Plan 1 is contained in rows 1, 2, 3, 4 and 5, Plan 2 is contained in rows , 6,7, 8, 9 and 10, Plan 3 is contained in rows 11, 12, 13, 14 and 15, etc..."
    ],
    [
      "REFERENCE",
      "NEMA TS 2 Clause 3.6.2.1 and 3.6.2.2"
    ],
    null,
    null,
    null
  ]
}
Records for description 4NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 4

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

Status in source: mandatory.

Names: patternTableType

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "patternTableType",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "other",
    "(",
    "1",
    ")",
    ",",
    "patterns",
    "(",
    "2",
    ")",
    ",",
    "offset3",
    "(",
    "3",
    ")",
    ",",
    "offset5",
    "(",
    "4",
    ")",
    "}",
    "ACCESS",
    "read-only",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition> This object provides information about any special organizational structure required for the pattern table. The defined structures are as follows: other: The pattern table setup is not described in this standard, refer to device manual. patterns: Each row of the pattern table represents a unique pattern and has no dependencies on other rows. offset3: The pattern table is organized into plans which have three offsets. Each plan uses three consecutive rows. Only patternOffsetTime and patternSequenceNumber values may vary between each of the three rows. Plan 1 is contained in rows 1, 2 and 3, Plan 2 is contained in rows 4, 5 and 6, Plan 3 is in rows 7, 8 and 9, etc. offset5: The pattern table is organized into plans which have five offsets. Each plan occupies five consecutive rows. Only patternOffsetTime and patternSequenceNumber values may vary between each of the rows. Plan 1 is contained in rows 1, 2, 3, 4 and 5, Plan 2 is contained in rows 6, 7, 8, 9 and 10, Plan 3 is contained in rows 11, 12, 13, 14 and 15, etc. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.4.6 <Object Type> S\"",
    "REFERENCE",
    "\"NEMA TS 2 Clause 3.6.2.1 and 3.6.2.2\"",
    "::=",
    "{",
    "coord",
    "6",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "other",
            1
          ],
          [
            "patterns",
            2
          ],
          [
            "offset3",
            3
          ],
          [
            "offset5",
            4
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition> This object provides information about any special organizational structure required for the pattern table. The defined structures are as follows: other: The pattern table setup is not described in this standard, refer to device manual. patterns: Each row of the pattern table represents a unique pattern and has no dependencies on other rows. offset3: The pattern table is organized into plans which have three offsets. Each plan uses three consecutive rows. Only patternOffsetTime and patternSequenceNumber values may vary between each of the three rows. Plan 1 is contained in rows 1, 2 and 3, Plan 2 is contained in rows 4, 5 and 6, Plan 3 is in rows 7, 8 and 9, etc. offset5: The pattern table is organized into plans which have five offsets. Each plan occupies five consecutive rows. Only patternOffsetTime and patternSequenceNumber values may vary between each of the rows. Plan 1 is contained in rows 1, 2, 3, 4 and 5, Plan 2 is contained in rows 6, 7, 8, 9 and 10, Plan 3 is contained in rows 11, 12, 13, 14 and 15, etc. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.4.6 <Object Type> S"
    ],
    [
      "REFERENCE",
      "NEMA TS 2 Clause 3.6.2.1 and 3.6.2.2"
    ],
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1206)

Schopp Bruce J.

Siblings (15)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.1206.4.2.1.4.1 coordOperationalMode00
1.3.6.1.4.1.1206.4.2.1.4.2 coordCorrectionMode00
1.3.6.1.4.1.1206.4.2.1.4.3 coordMaximumMode00
1.3.6.1.4.1.1206.4.2.1.4.4 coordForceMode00
1.3.6.1.4.1.1206.4.2.1.4.5 maxPatterns00
1.3.6.1.4.1.1206.4.2.1.4.7 patternTable19
1.3.6.1.4.1.1206.4.2.1.4.8 maxSplits00
1.3.6.1.4.1.1206.4.2.1.4.9 splitTable17
1.3.6.1.4.1.1206.4.2.1.4.10 coordPatternStatus00
1.3.6.1.4.1.1206.4.2.1.4.11 localFreeStatus00
1.3.6.1.4.1.1206.4.2.1.4.12 coordCycleStatus00
1.3.6.1.4.1.1206.4.2.1.4.13 coordSyncStatus00
1.3.6.1.4.1.1206.4.2.1.4.14 systemPatternControl00
1.3.6.1.4.1.1206.4.2.1.4.15 systemSyncControl00
1.3.6.1.4.1.1206.4.2.1.4.16 unitCoordSyncPoint00