OID reference

ptsOperationalMode

1.3.6.1.4.1.1206.4.2.5.2.11.6

Description

<Definition>Indicates the operational mode of the Pavement Treatment System. When in the 'off' state, the PTS shall not trigger the sprayer even if commanded to do so and shall always be inactive. The PTS shall transition to the requested operational mode, upon request. When in the 'automatic' state, the PTS shall mon…

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
6
Node name
ptsOperationalMode
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.1206.4.2.5.2.11.6
URN notation
urn:oid:1.3.6.1.4.1.1206.4.2.5.2.11.6
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

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

SNMP properties

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

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-write
Status in MIB
mandatory

Variant 2 — ITE public NTCIP working repository MIBs, NTCIP published standard MIB annexes (reviewed modules)

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

Enumerated values

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

ValueNameSource variants
1off1, 2
2manual1, 2
3automatic1, 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.5.2.11.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

ptsOperationalMode · mandatory

ptsOperationalMode OBJECT-TYPE
SYNTAX       INTEGER {      off (1),
                            manual (2),
                            automatic (3)}
ACCESS       read-write
STATUS       mandatory
DESCRIPTION "<Definition>Indicates the operational mode of the Pavement
Treatment System.


                                                                                         

                                                                                 
                                                                                



When in the 'off' state, the PTS shall not trigger the sprayer even if
commanded to do so and shall always be inactive. The PTS shall transition to
the requested operational mode, upon request.

When in the 'automatic' state, the PTS shall monitor conditions and trigger
the sprayer based on a manufacturer specific algorithm. The algorithm shall
only consider input from the detectors selected in the ptsMonitoringDetectors
object. The PTS shall also trigger the sprayer if commanded to do so via the
ptsCommandState object. The PTS shall transition to the requested
operational mode, upon request.

When in the 'manual' state, the PTS shall trigger the sprayer if commanded to
do so via the ptsCommandState object. The PTS shall transition to the
requested operational mode, upon request.
<SetConstraint>always
<DescriptiveName>PTS.operationalMode.code
<Valid Value Rule>
off   When set to this value the ESS will not trigger the
      bridge sprayer

manual      When set to this value the ESS will only trigger the
      bridge sprayer when manually commanded to do
      so (e.g., see bridgeSprayerMgmtSignalState).

automatic    When set to this value the ESS will trigger the
       bridge sprayer when manually commanded to do
       so or when the internal algorithm determines
       that the sprayer should be triggered.
<Data Concept Type>Data Element"
::=    { essNtcipTreatment 6 }

ptsOperationalMode · obsolete

ptsOperationalMode OBJECT-TYPE
SYNTAX	INTEGER { 	off (1),
				manual (2),
				automatic (3)} 
ACCESS	read-write 
STATUS	obsolete 
DESCRIPTION "<Definition>Indicates the operational mode of the Pavement Treatment System.

When in the 'off' state, the PTS shall not trigger the sprayer even if commanded to do so and shall always be inactive. The PTS shall transition to the requested operational mode, upon request.

When in the 'automatic' state, the PTS shall monitor conditions and trigger the sprayer based on a manufacturer specific algorithm. The algorithm shall only consider input from the detectors selected in the ptsMonitoringDetectors object. The PTS shall also trigger the sprayer if commanded to do so via the ptsCommandState object. The PTS shall transition to the requested operational mode, upon request.

When in the 'manual' state, the PTS shall trigger the sprayer if commanded to do so via the ptsCommandState object. The PTS shall transition to the requested operational mode, upon request.
<DescriptiveName>PTS.operationalMode.code
<Valid Value Rule>
off	When set to this value the ESS does not trigger the 
	bridge sprayer 

manual	When set to this value the ESS only triggers the 
	bridge sprayer when manually commanded to do
	so (e.g., see bridgeSprayerMgmtSignalState). 

automatic	When set to this value the ESS triggers the
	bridge sprayer when manually commanded to do 
	so or when the internal algorithm determines
	that the sprayer should be triggered.
<Data Concept Type>Data Element
<Object Identifier> 1.3.6.1.4.1.1206.4.2.5.2.11.6"
::=	{ essNtcipTreatment 6 }

ptsOperationalMode · obsolete

ptsOperationalMode OBJECT-TYPE
SYNTAX      INTEGER {   off (1),
                        manual (2),
                        automatic (3)}
ACCESS      read-write
STATUS      obsolete
DESCRIPTION "<Definition>Indicates the operational mode of the Pavement
Treatment System.

When in the 'off' state, the PTS shall not trigger the sprayer even if
commanded to do so and shall always be inactive. The PTS shall transition to
the requested operational mode, upon request.

When in the 'automatic' state, the PTS shall monitor conditions and trigger
the sprayer based on a manufacturer specific algorithm. The algorithm shall
only consider input from the detectors selected in the ptsMonitoringDetectors
object. The PTS shall also trigger the sprayer if commanded to do so via the
ptsCommandState object. The PTS shall transition to the requested operational
mode, upon request.

When in the 'manual' state, the PTS shall trigger the sprayer if commanded to
do so via the ptsCommandState object. The PTS shall transition to the
requested operational mode, upon request.
<DescriptiveName>PTS.operationalMode.code
<Valid Value Rule>
off   When set to this value the ESS does not trigger the
      bridge sprayer

manual         When set to this value the ESS only triggers the
         bridge sprayer when manually commanded to do
         so (e.g., see bridgeSprayerMgmtSignalState).

automatic   When set to this value the ESS triggers the
      bridge sprayer when manually commanded to do
      so or when the internal algorithm determines
      that the sprayer should be triggered.
<Data Concept Type>Data Element
<Object Identifier> 1.3.6.1.4.1.1206.4.2.5.2.11.6"
::=   { essNtcipTreatment 6 }

ptsOperationalMode · obsolete

ptsOperationalMode OBJECT-TYPE
SYNTAX        INTEGER {  off (1),
                         manual (2),
                         automatic (3)}
ACCESS        read-write
STATUS        obsolete
DESCRIPTION "<Definition>Indicates the operational mode of the Pavement
Treatment System.

When in the 'off' state, the PTS shall not trigger the sprayer even if
commanded to do so and shall always be inactive. The PTS shall transition to
the requested operational mode, upon request.

When in the 'automatic' state, the PTS shall monitor conditions and trigger
the sprayer based on a manufacturer specific algorithm. The algorithm shall
only consider input from the detectors selected in the ptsMonitoringDetectors
object. The PTS shall also trigger the sprayer if commanded to do so via the
ptsCommandState object. The PTS shall transition to the requested operational
mode, upon request.

When in the 'manual' state, the PTS shall trigger the sprayer if commanded to
do so via the ptsCommandState object. The PTS shall transition to the
requested operational mode, upon request.
<SetConstraint>always
<DescriptiveName>PTS.operationalMode.code
<Valid Value Rule>
off   When set to this value the ESS will not trigger the
      bridge sprayer

manual      When set to this value the ESS will only trigger the
      bridge sprayer when manually commanded to do
      so (e.g., see bridgeSprayerMgmtSignalState).

automatic   When set to this value the ESS will trigger the
      bridge sprayer when manually commanded to do
      so or when the internal algorithm determines
      that the sprayer should be triggered.
<Data Concept Type>Data Element"
::=   { essNtcipTreatment 6 }

Meaning

Descriptions

2 unique

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

Description 1

<Definition>Indicates the operational mode of the Pavement Treatment System. When in the 'off' state, the PTS shall not trigger the sprayer even if commanded to do so and shall always be inactive. The PTS shall transition to the requested operational mode, upon request. When in the 'automatic' state, the PTS shall monitor conditions and trigger the sprayer based on a manufacturer specific algorithm. The algorithm shall only consider input from the detectors selected in the ptsMonitoringDetectors object. The PTS shall also trigger the sprayer if commanded to do so via the ptsCommandState object. The PTS shall transition to the requested operational mode, upon request. When in the 'manual' state, the PTS shall trigger the sprayer if commanded to do so via the ptsCommandState object. The PTS shall transition to the requested operational mode, upon request. <SetConstraint>always <DescriptiveName>PTS.operationalMode.code <Valid Value Rule> off When set to this value the ESS will not trigger the bridge sprayer manual When set to this value the ESS will only trigger the bridge sprayer when manually commanded to do so (e.g., see bridgeSprayerMgmtSignalState). automatic When set to this value the ESS will trigger the bridge sprayer when manually commanded to do so or when the internal algorithm determines that the sprayer should be triggered. <Data Concept Type>Data Element

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 2 matching source records

Description 2

<Definition>Indicates the operational mode of the Pavement Treatment System. When in the 'off' state, the PTS shall not trigger the sprayer even if commanded to do so and shall always be inactive. The PTS shall transition to the requested operational mode, upon request. When in the 'automatic' state, the PTS shall monitor conditions and trigger the sprayer based on a manufacturer specific algorithm. The algorithm shall only consider input from the detectors selected in the ptsMonitoringDetectors object. The PTS shall also trigger the sprayer if commanded to do so via the ptsCommandState object. The PTS shall transition to the requested operational mode, upon request. When in the 'manual' state, the PTS shall trigger the sprayer if commanded to do so via the ptsCommandState object. The PTS shall transition to the requested operational mode, upon request. <DescriptiveName>PTS.operationalMode.code <Valid Value Rule> off When set to this value the ESS does not trigger the bridge sprayer manual When set to this value the ESS only triggers the bridge sprayer when manually commanded to do so (e.g., see bridgeSprayerMgmtSignalState). automatic When set to this value the ESS triggers the bridge sprayer when manually commanded to do so or when the internal algorithm determines that the sprayer should be triggered. <Data Concept Type>Data Element <Object Identifier> 1.3.6.1.4.1.1206.4.2.5.2.11.6

Sources for this description

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

See 1 matching source record

Evidence

Source records

3 records

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

Records for description 1NTCIP published standard MIB annexes (reviewed modules)2 records · 2 sources

Description 1

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

Status in source: mandatory.

Names: ptsOperationalMode

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "ptsOperationalMode",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "off",
    "(",
    "1",
    ")",
    ",",
    "manual",
    "(",
    "2",
    ")",
    ",",
    "automatic",
    "(",
    "3",
    ")",
    "}",
    "ACCESS",
    "read-write",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition>Indicates the operational mode of the Pavement Treatment System. When in the 'off' state, the PTS shall not trigger the sprayer even if commanded to do so and shall always be inactive. The PTS shall transition to the requested operational mode, upon request. When in the 'automatic' state, the PTS shall monitor conditions and trigger the sprayer based on a manufacturer specific algorithm. The algorithm shall only consider input from the detectors selected in the ptsMonitoringDetectors object. The PTS shall also trigger the sprayer if commanded to do so via the ptsCommandState object. The PTS shall transition to the requested operational mode, upon request. When in the 'manual' state, the PTS shall trigger the sprayer if commanded to do so via the ptsCommandState object. The PTS shall transition to the requested operational mode, upon request. <SetConstraint>always <DescriptiveName>PTS.operationalMode.code <Valid Value Rule> off When set to this value the ESS will not trigger the bridge sprayer manual When set to this value the ESS will only trigger the bridge sprayer when manually commanded to do so (e.g., see bridgeSprayerMgmtSignalState). automatic When set to this value the ESS will trigger the bridge sprayer when manually commanded to do so or when the internal algorithm determines that the sprayer should be triggered. <Data Concept Type>Data Element\"",
    "::=",
    "{",
    "essNtcipTreatment",
    "6",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "off",
            1
          ],
          [
            "manual",
            2
          ],
          [
            "automatic",
            3
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition>Indicates the operational mode of the Pavement Treatment System. When in the 'off' state, the PTS shall not trigger the sprayer even if commanded to do so and shall always be inactive. The PTS shall transition to the requested operational mode, upon request. When in the 'automatic' state, the PTS shall monitor conditions and trigger the sprayer based on a manufacturer specific algorithm. The algorithm shall only consider input from the detectors selected in the ptsMonitoringDetectors object. The PTS shall also trigger the sprayer if commanded to do so via the ptsCommandState object. The PTS shall transition to the requested operational mode, upon request. When in the 'manual' state, the PTS shall trigger the sprayer if commanded to do so via the ptsCommandState object. The PTS shall transition to the requested operational mode, upon request. <SetConstraint>always <DescriptiveName>PTS.operationalMode.code <Valid Value Rule> off When set to this value the ESS will not trigger the bridge sprayer manual When set to this value the ESS will only trigger the bridge sprayer when manually commanded to do so (e.g., see bridgeSprayerMgmtSignalState). automatic When set to this value the ESS will trigger the bridge sprayer when manually commanded to do so or when the internal algorithm determines that the sprayer should be triggered. <Data Concept Type>Data Element"
    ],
    null,
    null,
    null,
    null
  ]
}
ptsOperationalMode · obsoleteNTCIP published standard MIB annexes (reviewed modules)1 source

Status in source: obsolete.

Names: ptsOperationalMode

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "ptsOperationalMode",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "off",
    "(",
    "1",
    ")",
    ",",
    "manual",
    "(",
    "2",
    ")",
    ",",
    "automatic",
    "(",
    "3",
    ")",
    "}",
    "ACCESS",
    "read-write",
    "STATUS",
    "obsolete",
    "DESCRIPTION",
    "\"<Definition>Indicates the operational mode of the Pavement Treatment System. When in the 'off' state, the PTS shall not trigger the sprayer even if commanded to do so and shall always be inactive. The PTS shall transition to the requested operational mode, upon request. When in the 'automatic' state, the PTS shall monitor conditions and trigger the sprayer based on a manufacturer specific algorithm. The algorithm shall only consider input from the detectors selected in the ptsMonitoringDetectors object. The PTS shall also trigger the sprayer if commanded to do so via the ptsCommandState object. The PTS shall transition to the requested operational mode, upon request. When in the 'manual' state, the PTS shall trigger the sprayer if commanded to do so via the ptsCommandState object. The PTS shall transition to the requested operational mode, upon request. <SetConstraint>always <DescriptiveName>PTS.operationalMode.code <Valid Value Rule> off When set to this value the ESS will not trigger the bridge sprayer manual When set to this value the ESS will only trigger the bridge sprayer when manually commanded to do so (e.g., see bridgeSprayerMgmtSignalState). automatic When set to this value the ESS will trigger the bridge sprayer when manually commanded to do so or when the internal algorithm determines that the sprayer should be triggered. <Data Concept Type>Data Element\"",
    "::=",
    "{",
    "essNtcipTreatment",
    "6",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "off",
            1
          ],
          [
            "manual",
            2
          ],
          [
            "automatic",
            3
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "obsolete"
    ],
    [
      "DESCRIPTION",
      "<Definition>Indicates the operational mode of the Pavement Treatment System. When in the 'off' state, the PTS shall not trigger the sprayer even if commanded to do so and shall always be inactive. The PTS shall transition to the requested operational mode, upon request. When in the 'automatic' state, the PTS shall monitor conditions and trigger the sprayer based on a manufacturer specific algorithm. The algorithm shall only consider input from the detectors selected in the ptsMonitoringDetectors object. The PTS shall also trigger the sprayer if commanded to do so via the ptsCommandState object. The PTS shall transition to the requested operational mode, upon request. When in the 'manual' state, the PTS shall trigger the sprayer if commanded to do so via the ptsCommandState object. The PTS shall transition to the requested operational mode, upon request. <SetConstraint>always <DescriptiveName>PTS.operationalMode.code <Valid Value Rule> off When set to this value the ESS will not trigger the bridge sprayer manual When set to this value the ESS will only trigger the bridge sprayer when manually commanded to do so (e.g., see bridgeSprayerMgmtSignalState). automatic When set to this value the ESS will trigger the bridge sprayer when manually commanded to do so or when the internal algorithm determines that the sprayer should be triggered. <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

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

Status in source: obsolete.

Names: ptsOperationalMode

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "ptsOperationalMode",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "off",
    "(",
    "1",
    ")",
    ",",
    "manual",
    "(",
    "2",
    ")",
    ",",
    "automatic",
    "(",
    "3",
    ")",
    "}",
    "ACCESS",
    "read-write",
    "STATUS",
    "obsolete",
    "DESCRIPTION",
    "\"<Definition>Indicates the operational mode of the Pavement Treatment System. When in the 'off' state, the PTS shall not trigger the sprayer even if commanded to do so and shall always be inactive. The PTS shall transition to the requested operational mode, upon request. When in the 'automatic' state, the PTS shall monitor conditions and trigger the sprayer based on a manufacturer specific algorithm. The algorithm shall only consider input from the detectors selected in the ptsMonitoringDetectors object. The PTS shall also trigger the sprayer if commanded to do so via the ptsCommandState object. The PTS shall transition to the requested operational mode, upon request. When in the 'manual' state, the PTS shall trigger the sprayer if commanded to do so via the ptsCommandState object. The PTS shall transition to the requested operational mode, upon request. <DescriptiveName>PTS.operationalMode.code <Valid Value Rule> off When set to this value the ESS does not trigger the bridge sprayer manual When set to this value the ESS only triggers the bridge sprayer when manually commanded to do so (e.g., see bridgeSprayerMgmtSignalState). automatic When set to this value the ESS triggers the bridge sprayer when manually commanded to do so or when the internal algorithm determines that the sprayer should be triggered. <Data Concept Type>Data Element <Object Identifier> 1.3.6.1.4.1.1206.4.2.5.2.11.6\"",
    "::=",
    "{",
    "essNtcipTreatment",
    "6",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "off",
            1
          ],
          [
            "manual",
            2
          ],
          [
            "automatic",
            3
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "obsolete"
    ],
    [
      "DESCRIPTION",
      "<Definition>Indicates the operational mode of the Pavement Treatment System. When in the 'off' state, the PTS shall not trigger the sprayer even if commanded to do so and shall always be inactive. The PTS shall transition to the requested operational mode, upon request. When in the 'automatic' state, the PTS shall monitor conditions and trigger the sprayer based on a manufacturer specific algorithm. The algorithm shall only consider input from the detectors selected in the ptsMonitoringDetectors object. The PTS shall also trigger the sprayer if commanded to do so via the ptsCommandState object. The PTS shall transition to the requested operational mode, upon request. When in the 'manual' state, the PTS shall trigger the sprayer if commanded to do so via the ptsCommandState object. The PTS shall transition to the requested operational mode, upon request. <DescriptiveName>PTS.operationalMode.code <Valid Value Rule> off When set to this value the ESS does not trigger the bridge sprayer manual When set to this value the ESS only triggers the bridge sprayer when manually commanded to do so (e.g., see bridgeSprayerMgmtSignalState). automatic When set to this value the ESS triggers the bridge sprayer when manually commanded to do so or when the internal algorithm determines that the sprayer should be triggered. <Data Concept Type>Data Element <Object Identifier> 1.3.6.1.4.1.1206.4.2.5.2.11.6"
    ],
    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)

    Related source files and packages:

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.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.17 ptsMonitoringDetectors00
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