OID reference

dcmMEType

1.3.6.1.4.1.1206.4.2.9.6.26.1.3

Description

Indicates the encoding of the data packet returned by the device. The values are: -other(1)=not defined. -asciiData(2)=data packet is encoded using an ascii representation of the ‘Data’ column of the Data Structure Table. This mode of operation is intended to provide the user with readable data directly from the devic…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.1206.4.2.9.6.26.1 (dcmMEEntry)
Node code
3
Node name
dcmMEType
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.1206.4.2.9.6.26.1.3
URN notation
urn:oid:1.3.6.1.4.1.1206.4.2.9.6.26.1.3
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

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

SNMP properties

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

Enumerated values

ValueName
1other
2asciiData
3binaryData

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. The index encoding is not inferred here.

Published row index: dcmMEStudyNum.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.1206.4.2.9.6.26.1.3

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.

dcmMEType OBJECT-TYPE
 SYNTAX INTEGER
 {
   other (1),
   asciiData (2),
   binaryData (3)
 }
 ACCESS read-write
 STATUS mandatory
 DESCRIPTION
 "Indicates the encoding of the data packet returned by the device.       The
values are:
-other(1)=not defined.

-asciiData(2)=data packet is encoded using an ascii representation of the
‘Data’ column of the Data Structure Table. This mode of operation is intended
to provide the user with readable data directly from the device without
requiring interpretation (it is included for historical purposes). Each field
of the data packet (a defined bin for a binned study, a pvr parameter for a
pvr study, or each field of an event record for an event study) shall be
separated by a ‘white space’ (either an ascii space, ascii comma, ascii tab).
Each record (all of the binned counts for a binned study, each set of vehicle
parameters for a pvr study and each logical IO event record for an event
study), will be terminated by a ‘white terminator’ (an ascii carriage return,
an ascii line feed or a combination ascii carriage return/line feed). Because
each field is separated by an ascii ‘white space’, the dcn device may choose
to pad each field with leading ascii zeros (ascii code h30) to make each
identical field the same length for readability. The octet string code (04h)
and the length of the octet string fields are not sent in asciiData mode. The
number of octets per binned counts for binned studies is not sent. The
vehicle time tag for pvr studies may be translated by before being sent. The



                                                                                        

                      
       



data fields sent for event studies shall be the ascii hex representation of
each defined field since event records are defined in bits.

-binaryData(3)=data packet is encoded in binary. The data is encoded as
defined by the ‘Data’ field of the Data Structure Table for the specified type
of data.”
::= {dcmMEEntry 3}

Meaning

Descriptions

1 unique

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

Indicates the encoding of the data packet returned by the device. The values are: -other(1)=not defined. -asciiData(2)=data packet is encoded using an ascii representation of the ‘Data’ column of the Data Structure Table. This mode of operation is intended to provide the user with readable data directly from the device without requiring interpretation (it is included for historical purposes). Each field of the data packet (a defined bin for a binned study, a pvr parameter for a pvr study, or each field of an event record for an event study) shall be separated by a ‘white space’ (either an ascii space, ascii comma, ascii tab). Each record (all of the binned counts for a binned study, each set of vehicle parameters for a pvr study and each logical IO event record for an event study), will be terminated by a ‘white terminator’ (an ascii carriage return, an ascii line feed or a combination ascii carriage return/line feed). Because each field is separated by an ascii ‘white space’, the dcn device may choose to pad each field with leading ascii zeros (ascii code h30) to make each identical field the same length for readability. The octet string code (04h) and the length of the octet string fields are not sent in asciiData mode. The number of octets per binned counts for binned studies is not sent. The vehicle time tag for pvr studies may be translated by before being sent. The data fields sent for event studies shall be the ascii hex representation of each defined field since event records are defined in bits. -binaryData(3)=data packet is encoded in binary. The data is encoded as defined by the ‘Data’ field of the Data Structure Table for the specified type of data.

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

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 1NTCIP published standard MIB annexes (reviewed modules)1 record · 2 sources

Description 1

dcmMEType · mandatoryNTCIP published standard MIB annexes (reviewed modules)2 sources

Status in source: mandatory.

Names: dcmMEType

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dcmMEType",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "other",
    "(",
    "1",
    ")",
    ",",
    "asciiData",
    "(",
    "2",
    ")",
    ",",
    "binaryData",
    "(",
    "3",
    ")",
    "}",
    "ACCESS",
    "read-write",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"",
    "Indicates",
    "the",
    "encoding",
    "of",
    "the",
    "data",
    "packet",
    "returned",
    "by",
    "the",
    "device",
    ".",
    "The",
    "values",
    "are",
    ":",
    "-",
    "other",
    "(",
    "1",
    ")",
    "=",
    "not",
    "defined",
    ".",
    "-",
    "asciiData",
    "(",
    "2",
    ")",
    "=",
    "data",
    "packet",
    "is",
    "encoded",
    "using",
    "an",
    "ascii",
    "representation",
    "of",
    "the",
    "‘",
    "Data",
    "’",
    "column",
    "of",
    "the",
    "Data",
    "Structure",
    "Table",
    ".",
    "This",
    "mode",
    "of",
    "operation",
    "is",
    "intended",
    "to",
    "provide",
    "the",
    "user",
    "with",
    "readable",
    "data",
    "directly",
    "from",
    "the",
    "device",
    "without",
    "requiring",
    "interpretation",
    "(",
    "it",
    "is",
    "included",
    "for",
    "historical",
    "purposes",
    ")",
    ".",
    "Each",
    "field",
    "of",
    "the",
    "data",
    "packet",
    "(",
    "a",
    "defined",
    "bin",
    "for",
    "a",
    "binned",
    "study",
    ",",
    "a",
    "pvr",
    "parameter",
    "for",
    "a",
    "pvr",
    "study",
    ",",
    "or",
    "each",
    "field",
    "of",
    "an",
    "event",
    "record",
    "for",
    "an",
    "event",
    "study",
    ")",
    "shall",
    "be",
    "separated",
    "by",
    "a",
    "‘",
    "white",
    "space",
    "’",
    "(",
    "either",
    "an",
    "ascii",
    "space",
    ",",
    "ascii",
    "comma",
    ",",
    "ascii",
    "tab",
    ")",
    ".",
    "Each",
    "record",
    "(",
    "all",
    "of",
    "the",
    "binned",
    "counts",
    "for",
    "a",
    "binned",
    "study",
    ",",
    "each",
    "set",
    "of",
    "vehicle",
    "parameters",
    "for",
    "a",
    "pvr",
    "study",
    "and",
    "each",
    "logical",
    "IO",
    "event",
    "record",
    "for",
    "an",
    "event",
    "study",
    ")",
    ",",
    "will",
    "be",
    "terminated",
    "by",
    "a",
    "‘",
    "white",
    "terminator",
    "’",
    "(",
    "an",
    "ascii",
    "carriage",
    "return",
    ",",
    "an",
    "ascii",
    "line",
    "feed",
    "or",
    "a",
    "combination",
    "ascii",
    "carriage",
    "return",
    "/",
    "line",
    "feed",
    ")",
    ".",
    "Because",
    "each",
    "field",
    "is",
    "separated",
    "by",
    "an",
    "ascii",
    "‘",
    "white",
    "space",
    "’",
    ",",
    "the",
    "dcn",
    "device",
    "may",
    "choose",
    "to",
    "pad",
    "each",
    "field",
    "with",
    "leading",
    "ascii",
    "zeros",
    "(",
    "ascii",
    "code",
    "h30",
    ")",
    "to",
    "make",
    "each",
    "identical",
    "field",
    "the",
    "same",
    "length",
    "for",
    "readability",
    ".",
    "The",
    "octet",
    "string",
    "code",
    "(",
    "04",
    "h",
    ")",
    "and",
    "the",
    "length",
    "of",
    "the",
    "octet",
    "string",
    "fields",
    "are",
    "not",
    "sent",
    "in",
    "asciiData",
    "mode",
    ".",
    "The",
    "number",
    "of",
    "octets",
    "per",
    "binned",
    "counts",
    "for",
    "binned",
    "studies",
    "is",
    "not",
    "sent",
    ".",
    "The",
    "vehicle",
    "time",
    "tag",
    "for",
    "pvr",
    "studies",
    "may",
    "be",
    "translated",
    "by",
    "before",
    "being",
    "sent",
    ".",
    "The",
    "data",
    "fields",
    "sent",
    "for",
    "event",
    "studies",
    "shall",
    "be",
    "the",
    "ascii",
    "hex",
    "representation",
    "of",
    "each",
    "defined",
    "field",
    "since",
    "event",
    "records",
    "are",
    "defined",
    "in",
    "bits",
    ".",
    "-",
    "binaryData",
    "(",
    "3",
    ")",
    "=",
    "data",
    "packet",
    "is",
    "encoded",
    "in",
    "binary",
    ".",
    "The",
    "data",
    "is",
    "encoded",
    "as",
    "defined",
    "by",
    "the",
    "‘",
    "Data",
    "’",
    "field",
    "of",
    "the",
    "Data",
    "Structure",
    "Table",
    "for",
    "the",
    "specified",
    "type",
    "of",
    "data",
    ".",
    "”",
    "::=",
    "{",
    "dcmMEEntry",
    "3",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "other",
            1
          ],
          [
            "asciiData",
            2
          ],
          [
            "binaryData",
            3
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "Indicates the encoding of the data packet returned by the device. The values are: -other(1)=not defined. -asciiData(2)=data packet is encoded using an ascii representation of the ‘Data’ column of the Data Structure Table. This mode of operation is intended to provide the user with readable data directly from the device without requiring interpretation (it is included for historical purposes). Each field of the data packet (a defined bin for a binned study, a pvr parameter for a pvr study, or each field of an event record for an event study) shall be separated by a ‘white space’ (either an ascii space, ascii comma, ascii tab). Each record (all of the binned counts for a binned study, each set of vehicle parameters for a pvr study and each logical IO event record for an event study), will be terminated by a ‘white terminator’ (an ascii carriage return, an ascii line feed or a combination ascii carriage return/line feed). Because each field is separated by an ascii ‘white space’, the dcn device may choose to pad each field with leading ascii zeros (ascii code h30) to make each identical field the same length for readability. The octet string code (04h) and the length of the octet string fields are not sent in asciiData mode. The number of octets per binned counts for binned studies is not sent. The vehicle time tag for pvr studies may be translated by before being sent. The data fields sent for event studies shall be the ascii hex representation of each defined field since event records are defined in bits. -binaryData(3)=data packet is encoded in binary. The data is encoded as defined by the ‘Data’ field of the Data Structure Table for the specified type of data."
    ],
    null,
    null,
    null,
    null
  ]
}
  • NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1206:2005, Object Definitions for Data Collection and Monitoring (DCM) Devices Published November 2005 — original PDF · Official record

    Module: DCM-MIB1

    See published definition above

    Module imports
    {'TMIB-II': ['devices'], 'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['Counter']}

    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: 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 closing quotation mark terminates a DESCRIPTION in this PDF. Normalize that delimiter only in the derived MIB transcription; preserve the literal published definition and unmodified PDF. No numeric assignment changes.

    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-II. 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 NTCIP1206v0123f.pdf — DCM-MIB1 (MIB transcription)
  • NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1206:2005, Object Definitions for Daqta Collection and Monitoring (DCM) Devices Published November 2005 (superceded by NTCIP 1206 v02) — original PDF · Official record

    Module: DCM-MIB1

    Same published definition

    Module imports
    {'TMIB-II': ['devices'], 'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['Counter']}

    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: 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 closing quotation mark terminates a DESCRIPTION in this PDF. Normalize that delimiter only in the derived MIB transcription; preserve the literal published definition and unmodified PDF. No numeric assignment changes.

    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-II. 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 NTCIP1206v0123f-1.pdf — DCM-MIB1 (MIB transcription)

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1206)

Schopp Bruce J.

Siblings (6)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.1206.4.2.9.6.26.1.1 dcmMEStudyNum00
1.3.6.1.4.1.1206.4.2.9.6.26.1.2 dcmMEIONum00
1.3.6.1.4.1.1206.4.2.9.6.26.1.4 dcmMETimeInterval00
1.3.6.1.4.1.1206.4.2.9.6.26.1.5 dcmMEControl00
1.3.6.1.4.1.1206.4.2.9.6.26.1.6 dcmMEStatus00
1.3.6.1.4.1.1206.4.2.9.6.26.1.7 dcmMEPollNow00