OID reference

ptsMonitoringDetectors

1.3.6.1.4.1.1206.4.2.5.2.11.17

Description

<Definition>Indicates the pavement detectors that the PTS shall use in its algorithm that determines when the PTS will automatically trigger the sprayer. <DescriptiveName>PTS.monitoringDetectors:code <Valid Value Rule> Each bit indicates whether or not the associated pavement sensor shall be used within the algorithm.…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.1206.4.2.5.2.11 (essNtcipTreatment)
Node code
17
Node name
ptsMonitoringDetectors
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.1206.4.2.5.2.11.17
URN notation
urn:oid:1.3.6.1.4.1.1206.4.2.5.2.11.17
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 1206 4 2 5 2 11 17}

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

SNMP properties

Value type
OCTET STRING
Maximum access defined by MIB
read-write
Status in MIB
mandatory
Allowed size (octets)
4

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

ptsMonitoringDetectors · mandatory

ptsMonitoringDetectors OBJECT-TYPE
SYNTAX         OCTET STRING (SIZE (4))
ACCESS         read-write
STATUS         mandatory
DESCRIPTION "<Definition>Indicates the pavement detectors that the PTS shall
use in its algorithm that determines when the PTS will automatically trigger
the sprayer.
<DescriptiveName>PTS.monitoringDetectors:code
<Valid Value Rule>
Each bit indicates whether or not the associated pavement sensor shall be
used within the algorithm. The first (high order) bit in the bit string shall
reference the first pavement sensor. A value of one for any bit shall



                                                                                        

                 
        


indicate that the sensor input shall be considered, and a value of zero shall
mean that the input shall not be considered.
<Data Concept Type>Data Element"
::=   { essNtcipTreatment 17 }

ptsMonitoringDetectors · mandatory

ptsMonitoringDetectors OBJECT-TYPE
SYNTAX        OCTET STRING (SIZE (4))
ACCESS        read-write
STATUS        mandatory
DESCRIPTION "<Definition>Indicates the pavement detectors that the PTS shall
use in its algorithm that determines when the PTS will automatically trigger
the sprayer.
<DescriptiveName>PTS.monitoringDetectors:code
<Valid Value Rule>
Each bit indicates whether or not the associated pavement sensor shall be
used within the algorithm. The first (high order) bit in the bit string
shall reference the first pavement sensor. A value of one for any bit shall
indicate that the sensor input shall be considered, and a value of zero shall
mean that the input shall not be considered.
<Data Concept Type>Data Element"
::=     { essNtcipTreatment 17 }

ptsMonitoringDetectors · mandatory

ptsMonitoringDetectors OBJECT-TYPE
SYNTAX	OCTET STRING (SIZE (4)) 
ACCESS	read-write 
STATUS	mandatory 
DESCRIPTION "<Definition>Indicates the pavement detectors that the PTS shall use in its algorithm that determines when the PTS automatically triggers the sprayer.
<DescriptiveName>PTS.monitoringDetectors:code
<Valid Value Rule>Each bit indicates whether or not the associated pavement sensor shall be used within the algorithm. The first (high order) bit in the bit string shall reference the first pavement sensor. A value of one for any bit shall indicate that the sensor input shall be considered, and a value of zero shall mean that the input shall not be considered.
<Data Concept Type>Data Element
<Object Identifier> 1.3.6.1.4.1.1206.4.2.5.2.11.17"
::=	{ essNtcipTreatment 17 }

ptsMonitoringDetectors · mandatory

ptsMonitoringDetectors OBJECT-TYPE
SYNTAX      OCTET STRING (SIZE (4))



                                                                                   

                                                                                       
                                                                                      

ACCESS       read-write
STATUS       mandatory
DESCRIPTION "<Definition>Indicates the pavement detectors that the PTS shall
use in its algorithm that determines when the PTS automatically triggers the
sprayer.
<DescriptiveName>PTS.monitoringDetectors:code
<Valid Value Rule>Each bit indicates whether or not the associated pavement
sensor shall be used within the algorithm. The first (high order) bit in the
bit string shall reference the first pavement sensor. A value of one for any
bit shall indicate that the sensor input shall be considered, and a value of
zero shall mean that the input shall not be considered.
<Data Concept Type>Data Element
<Object Identifier> 1.3.6.1.4.1.1206.4.2.5.2.11.17"
::=    { essNtcipTreatment 17 }

Meaning

Descriptions

2 unique

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

Description 1

<Definition>Indicates the pavement detectors that the PTS shall use in its algorithm that determines when the PTS will automatically trigger the sprayer. <DescriptiveName>PTS.monitoringDetectors:code <Valid Value Rule> Each bit indicates whether or not the associated pavement sensor shall be used within the algorithm. The first (high order) bit in the bit string shall reference the first pavement sensor. A value of one for any bit shall indicate that the sensor input shall be considered, and a value of zero shall mean that the input shall not be considered. <Data Concept Type>Data Element

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 2

<Definition>Indicates the pavement detectors that the PTS shall use in its algorithm that determines when the PTS automatically triggers the sprayer. <DescriptiveName>PTS.monitoringDetectors:code <Valid Value Rule>Each bit indicates whether or not the associated pavement sensor shall be used within the algorithm. The first (high order) bit in the bit string shall reference the first pavement sensor. A value of one for any bit shall indicate that the sensor input shall be considered, and a value of zero shall mean that the input shall not be considered. <Data Concept Type>Data Element <Object Identifier> 1.3.6.1.4.1.1206.4.2.5.2.11.17

Sources for this description

ITE public NTCIP working repository MIBsNTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Evidence

Source records

2 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

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

Status in source: mandatory.

Names: ptsMonitoringDetectors

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "ptsMonitoringDetectors",
    "OBJECT-TYPE",
    "SYNTAX",
    "OCTET",
    "STRING",
    "(",
    "SIZE",
    "(",
    "4",
    ")",
    ")",
    "ACCESS",
    "read-write",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition>Indicates the pavement detectors that the PTS shall use in its algorithm that determines when the PTS will automatically trigger the sprayer. <DescriptiveName>PTS.monitoringDetectors:code <Valid Value Rule> Each bit indicates whether or not the associated pavement sensor shall be used within the algorithm. The first (high order) bit in the bit string shall reference the first pavement sensor. A value of one for any bit shall indicate that the sensor input shall be considered, and a value of zero shall mean that the input shall not be considered. <Data Concept Type>Data Element\"",
    "::=",
    "{",
    "essNtcipTreatment",
    "17",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "OCTET STRING",
      [
        "octetStringSubType",
        [
          [
            4
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition>Indicates the pavement detectors that the PTS shall use in its algorithm that determines when the PTS will automatically trigger the sprayer. <DescriptiveName>PTS.monitoringDetectors:code <Valid Value Rule> Each bit indicates whether or not the associated pavement sensor shall be used within the algorithm. The first (high order) bit in the bit string shall reference the first pavement sensor. A value of one for any bit shall indicate that the sensor input shall be considered, and a value of zero shall mean that the input shall not be considered. <Data Concept Type>Data Element"
    ],
    null,
    null,
    null,
    null
  ]
}
Records for description 2ITE public NTCIP working repository MIBs, NTCIP published standard MIB annexes (reviewed modules)1 record · 2 sources

Description 2

ptsMonitoringDetectors · mandatoryITE public NTCIP working repository MIBs, NTCIP published standard MIB annexes (reviewed modules)2 sources

Status in source: mandatory.

Names: ptsMonitoringDetectors

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "ptsMonitoringDetectors",
    "OBJECT-TYPE",
    "SYNTAX",
    "OCTET",
    "STRING",
    "(",
    "SIZE",
    "(",
    "4",
    ")",
    ")",
    "ACCESS",
    "read-write",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition>Indicates the pavement detectors that the PTS shall use in its algorithm that determines when the PTS automatically triggers the sprayer. <DescriptiveName>PTS.monitoringDetectors:code <Valid Value Rule>Each bit indicates whether or not the associated pavement sensor shall be used within the algorithm. The first (high order) bit in the bit string shall reference the first pavement sensor. A value of one for any bit shall indicate that the sensor input shall be considered, and a value of zero shall mean that the input shall not be considered. <Data Concept Type>Data Element <Object Identifier> 1.3.6.1.4.1.1206.4.2.5.2.11.17\"",
    "::=",
    "{",
    "essNtcipTreatment",
    "17",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "OCTET STRING",
      [
        "octetStringSubType",
        [
          [
            4
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition>Indicates the pavement detectors that the PTS shall use in its algorithm that determines when the PTS automatically triggers the sprayer. <DescriptiveName>PTS.monitoringDetectors:code <Valid Value Rule>Each bit indicates whether or not the associated pavement sensor shall be used within the algorithm. The first (high order) bit in the bit string shall reference the first pavement sensor. A value of one for any bit shall indicate that the sensor input shall be considered, and a value of zero shall mean that the input shall not be considered. <Data Concept Type>Data Element <Object Identifier> 1.3.6.1.4.1.1206.4.2.5.2.11.17"
    ],
    null,
    null,
    null,
    null
  ]
}
  • ITE public NTCIP working repository MIBs · Publisher's source file: NTCIP-1204 — NTCIP1204-Ess.mib

    Module: NTCIP1204-v04

    See published definition above

    Module imports
    {'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['Counter'], 'RFC1213-MIB': ['DisplayString'], 'NTCIP8004v02': ['ess', 'OerString']}

    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-1204 — NTCIP1204-Ess.mib
  • NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1204 v0426, National Transportation Communications for ITS Protocol Environmental Sensor Station (ESS) Interface Protocol — original PDF · Official record

    Module: NTCIP1204-v04

    See published definition above

    Module imports
    {'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['Counter'], 'RFC1213-MIB': ['DisplayString'], 'NTCIP8004v02': ['ess', 'OerString']}

    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 published normative SMI section omits its module END. The derived parser boundary is placed immediately before section 5.17, whose text explicitly says its items are not SNMP Objects. No declaration or numeric arc is added; the complete PDF is authoritative.

    Source data warning: Potentially inaccurate interpretation of historical NTCIP namespace references: NTCIP8004v02. 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 NTCIP-1204v0426b-2021_AsPublished.pdf — NTCIP1204-v04 (MIB transcription)

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1206)

Schopp Bruce J.

Siblings (22)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.1206.4.2.5.2.11.1 numEssTreatments00
1.3.6.1.4.1.1206.4.2.5.2.11.2 essPavementTreatmentTable15
1.3.6.1.4.1.1206.4.2.5.2.11.3 essPaveTreatmentAmount00
1.3.6.1.4.1.1206.4.2.5.2.11.4 essPaveTreatmentWidth00
1.3.6.1.4.1.1206.4.2.5.2.11.5 pavementTreatmentBlock00
1.3.6.1.4.1.1206.4.2.5.2.11.6 ptsOperationalMode00
1.3.6.1.4.1.1206.4.2.5.2.11.7 ptsCommandState00
1.3.6.1.4.1.1206.4.2.5.2.11.8 ptsSprayerState00
1.3.6.1.4.1.1206.4.2.5.2.11.9 ptsSignalDuration00
1.3.6.1.4.1.1206.4.2.5.2.11.10 ptsSignalEventCount00
1.3.6.1.4.1.1206.4.2.5.2.11.11 ptsLastSignalEvent00
1.3.6.1.4.1.1206.4.2.5.2.11.12 ptsActiveEventCount00
1.3.6.1.4.1.1206.4.2.5.2.11.13 ptsInactiveEventCount00
1.3.6.1.4.1.1206.4.2.5.2.11.14 ptsLastActiveEvent00
1.3.6.1.4.1.1206.4.2.5.2.11.15 ptsLastInactiveEvent00
1.3.6.1.4.1.1206.4.2.5.2.11.16 ptsError00
1.3.6.1.4.1.1206.4.2.5.2.11.18 ptsOperationalModeV300
1.3.6.1.4.1.1206.4.2.5.2.11.19 ptsCommandStateV300
1.3.6.1.4.1.1206.4.2.5.2.11.20 essPavementTreatmentLatitude00
1.3.6.1.4.1.1206.4.2.5.2.11.21 essPavementTreatmentLongitude00
1.3.6.1.4.1.1206.4.2.5.2.11.22 essPavementTreatmentLocation00
1.3.6.1.4.1.1206.4.2.5.2.11.23 essPavementTreatmentModelInformation00