OID reference

dcmVehicleStatusFlag

1.3.6.1.4.1.1206.4.2.9.1.27

Description

Indicates a vehicle-specific status and warning information (e.g. unbalanced axle hits) for the specified vehicle. Setting a bit to one (1) indicates that the associated condition is true. The values are: bit 0 – other bit 1 – off/onScale – physical off scale sensor is triggered or the on scale sensor was NOT triggere…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.1206.4.2.9.1 (dcmVehCriteria)
Node code
27
Node name
dcmVehicleStatusFlag
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.1206.4.2.9.1.27
URN notation
urn:oid:1.3.6.1.4.1.1206.4.2.9.1.27
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

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

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
not-accessible
Status in MIB
optional
Allowed ranges
0–4294967295

Using this OID with SNMP

At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.

A query example is omitted because the source variants do not establish compatible read access.

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.

dcmVehicleStatusFlag OBJECT-TYPE
 SYNTAX INTEGER (0..4294967295) --Bitmap
 ACCESS not-accessible
 STATUS optional
 DESCRIPTION
 "Indicates a vehicle-specific status and warning information (e.g. unbalanced
axle hits) for the specified vehicle. Setting a bit to one (1) indicates that
the associated condition is true. The values are:
bit 0 – other
bit 1 – off/onScale – physical off scale sensor is triggered or the on scale
sensor was NOT triggered.
bit 2 – overHeight – physical overheight sensor was triggered
bit 3 – speedChange – too much speed change detected between adjacent axles
for this vehicle
bit 4 – partialAxle – something went wrong in the middle of processing an axle
bit 5 – unequalAxleCount – number of axles detected on each axle sensor is not
the same.
bit 6 – tailgating – this vehicle follows the preceding vehicle too closely



                                                                                        

                      
       



bit 7 – wrongLane – this vehicle is in the wrong lane
bit 8 – runningScale – this vehicle bypassed the weigh-station incorrectly
bit 9 – notWimLane – this class of vehicle should not be in this lane
bit 10 – overlength – vehicle exceeds length threshold
bit 11 – overGVW – vehicle exceeds GVW weight threshold
bit 12 – randomSafety – vehicle randomly selected for Safety check
bit 13 – overSpeed - vehicle exceeds the speed threshold
bit 14 – late – vehicle arrives late at the next sensor array; used in
conjunction with bits 18, 19, 20.
bit 15 – unexpected – vehicle arrives unexpectedly at the next sensor array
bit 16 – pastDue – vehicle didn’t arrive at the next sensor array within the
arrival threshold
bit 17 – noMatch – no vehicle match was found for this vehicle at this sensor
array
bit 18 – badLateralPosition – error computing vehicle position (tire tracking)
bit 19 – noCompliance – no vehicle compliance structure found for this class
of vehicle
bit 20 – overrideFail – failed to adjust the direction signs in time
bit 21 – wrongWay – vehicle went over the sensor array in an unexpected
direction
bit 22- MinSpeed – too slow for data processing purposes
bit 23 – AxleProcessingError – internal error inside the vehicle processing
software
bit 24 - MaxSpeed – too fast for data processing purposes
bit 25 - TooManyAxles – the value indicated in the dcmMaxAxles object has been
exceeded
bit 26 - SensorOrderError – at least one of the sensors within the array was
not activated in the expected order, e.g., only the upstream sensor, or only
the downstream sensor was activated, or a sensor was activated by another lane
movement
bit 27 – MinAxleSpacing – the detected value for the axle spacing was below
the threshold for minAxleSpacing
bit 28 – MinFirstAxleSpacing - the detected value for the first axle spacing
was below the threshold for minFirstAxleSpacing
All unused bits are reserved."
::= {dcmVehCriteria 27}

Meaning

Descriptions

1 unique

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

Indicates a vehicle-specific status and warning information (e.g. unbalanced axle hits) for the specified vehicle. Setting a bit to one (1) indicates that the associated condition is true. The values are: bit 0 – other bit 1 – off/onScale – physical off scale sensor is triggered or the on scale sensor was NOT triggered. bit 2 – overHeight – physical overheight sensor was triggered bit 3 – speedChange – too much speed change detected between adjacent axles for this vehicle bit 4 – partialAxle – something went wrong in the middle of processing an axle bit 5 – unequalAxleCount – number of axles detected on each axle sensor is not the same. bit 6 – tailgating – this vehicle follows the preceding vehicle too closely bit 7 – wrongLane – this vehicle is in the wrong lane bit 8 – runningScale – this vehicle bypassed the weigh-station incorrectly bit 9 – notWimLane – this class of vehicle should not be in this lane bit 10 – overlength – vehicle exceeds length threshold bit 11 – overGVW – vehicle exceeds GVW weight threshold bit 12 – randomSafety – vehicle randomly selected for Safety check bit 13 – overSpeed - vehicle exceeds the speed threshold bit 14 – late – vehicle arrives late at the next sensor array; used in conjunction with bits 18, 19, 20. bit 15 – unexpected – vehicle arrives unexpectedly at the next sensor array bit 16 – pastDue – vehicle didn’t arrive at the next sensor array within the arrival threshold bit 17 – noMatch – no vehicle match was found for this vehicle at this sensor array bit 18 – badLateralPosition – error computing vehicle position (tire tracking) bit 19 – noCompliance – no vehicle compliance structure found for this class of vehicle bit 20 – overrideFail – failed to adjust the direction signs in time bit 21 – wrongWay – vehicle went over the sensor array in an unexpected direction bit 22- MinSpeed – too slow for data processing purposes bit 23 – AxleProcessingError – internal error inside the vehicle processing software bit 24 - MaxSpeed – too fast for data processing purposes bit 25 - TooManyAxles – the value indicated in the dcmMaxAxles object has been exceeded bit 26 - SensorOrderError – at least one of the sensors within the array was not activated in the expected order, e.g., only the upstream sensor, or only the downstream sensor was activated, or a sensor was activated by another lane movement bit 27 – MinAxleSpacing – the detected value for the axle spacing was below the threshold for minAxleSpacing bit 28 – MinFirstAxleSpacing - the detected value for the first axle spacing was below the threshold for minFirstAxleSpacing All unused bits are reserved.

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

dcmVehicleStatusFlag · optionalNTCIP published standard MIB annexes (reviewed modules)2 sources

Status in source: optional.

Names: dcmVehicleStatusFlag

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dcmVehicleStatusFlag",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "(",
    "0",
    ".",
    ".",
    "4294967295",
    ")",
    "ACCESS",
    "not-accessible",
    "STATUS",
    "optional",
    "DESCRIPTION",
    "\"Indicates a vehicle-specific status and warning information (e.g. unbalanced axle hits) for the specified vehicle. Setting a bit to one (1) indicates that the associated condition is true. The values are: bit 0 – other bit 1 – off/onScale – physical off scale sensor is triggered or the on scale sensor was NOT triggered. bit 2 – overHeight – physical overheight sensor was triggered bit 3 – speedChange – too much speed change detected between adjacent axles for this vehicle bit 4 – partialAxle – something went wrong in the middle of processing an axle bit 5 – unequalAxleCount – number of axles detected on each axle sensor is not the same. bit 6 – tailgating – this vehicle follows the preceding vehicle too closely bit 7 – wrongLane – this vehicle is in the wrong lane bit 8 – runningScale – this vehicle bypassed the weigh-station incorrectly bit 9 – notWimLane – this class of vehicle should not be in this lane bit 10 – overlength – vehicle exceeds length threshold bit 11 – overGVW – vehicle exceeds GVW weight threshold bit 12 – randomSafety – vehicle randomly selected for Safety check bit 13 – overSpeed - vehicle exceeds the speed threshold bit 14 – late – vehicle arrives late at the next sensor array; used in conjunction with bits 18, 19, 20. bit 15 – unexpected – vehicle arrives unexpectedly at the next sensor array bit 16 – pastDue – vehicle didn’t arrive at the next sensor array within the arrival threshold bit 17 – noMatch – no vehicle match was found for this vehicle at this sensor array bit 18 – badLateralPosition – error computing vehicle position (tire tracking) bit 19 – noCompliance – no vehicle compliance structure found for this class of vehicle bit 20 – overrideFail – failed to adjust the direction signs in time bit 21 – wrongWay – vehicle went over the sensor array in an unexpected direction bit 22- MinSpeed – too slow for data processing purposes bit 23 – AxleProcessingError – internal error inside the vehicle processing software bit 24 - MaxSpeed – too fast for data processing purposes bit 25 - TooManyAxles – the value indicated in the dcmMaxAxles object has been exceeded bit 26 - SensorOrderError – at least one of the sensors within the array was not activated in the expected order, e.g., only the upstream sensor, or only the downstream sensor was activated, or a sensor was activated by another lane movement bit 27 – MinAxleSpacing – the detected value for the axle spacing was below the threshold for minAxleSpacing bit 28 – MinFirstAxleSpacing - the detected value for the first axle spacing was below the threshold for minFirstAxleSpacing All unused bits are reserved.\"",
    "::=",
    "{",
    "dcmVehCriteria",
    "27",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "integerSubType",
        [
          [
            0,
            4294967295
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "optional"
    ],
    [
      "DESCRIPTION",
      "Indicates a vehicle-specific status and warning information (e.g. unbalanced axle hits) for the specified vehicle. Setting a bit to one (1) indicates that the associated condition is true. The values are: bit 0 – other bit 1 – off/onScale – physical off scale sensor is triggered or the on scale sensor was NOT triggered. bit 2 – overHeight – physical overheight sensor was triggered bit 3 – speedChange – too much speed change detected between adjacent axles for this vehicle bit 4 – partialAxle – something went wrong in the middle of processing an axle bit 5 – unequalAxleCount – number of axles detected on each axle sensor is not the same. bit 6 – tailgating – this vehicle follows the preceding vehicle too closely bit 7 – wrongLane – this vehicle is in the wrong lane bit 8 – runningScale – this vehicle bypassed the weigh-station incorrectly bit 9 – notWimLane – this class of vehicle should not be in this lane bit 10 – overlength – vehicle exceeds length threshold bit 11 – overGVW – vehicle exceeds GVW weight threshold bit 12 – randomSafety – vehicle randomly selected for Safety check bit 13 – overSpeed - vehicle exceeds the speed threshold bit 14 – late – vehicle arrives late at the next sensor array; used in conjunction with bits 18, 19, 20. bit 15 – unexpected – vehicle arrives unexpectedly at the next sensor array bit 16 – pastDue – vehicle didn’t arrive at the next sensor array within the arrival threshold bit 17 – noMatch – no vehicle match was found for this vehicle at this sensor array bit 18 – badLateralPosition – error computing vehicle position (tire tracking) bit 19 – noCompliance – no vehicle compliance structure found for this class of vehicle bit 20 – overrideFail – failed to adjust the direction signs in time bit 21 – wrongWay – vehicle went over the sensor array in an unexpected direction bit 22- MinSpeed – too slow for data processing purposes bit 23 – AxleProcessingError – internal error inside the vehicle processing software bit 24 - MaxSpeed – too fast for data processing purposes bit 25 - TooManyAxles – the value indicated in the dcmMaxAxles object has been exceeded bit 26 - SensorOrderError – at least one of the sensors within the array was not activated in the expected order, e.g., only the upstream sensor, or only the downstream sensor was activated, or a sensor was activated by another lane movement bit 27 – MinAxleSpacing – the detected value for the axle spacing was below the threshold for minAxleSpacing bit 28 – MinFirstAxleSpacing - the detected value for the first axle spacing was below the threshold for minFirstAxleSpacing All unused bits are reserved."
    ],
    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 (31)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.1206.4.2.9.1.1 dcmVCTMaxNumRows00
1.3.6.1.4.1.1206.4.2.9.1.2 dcmVCTCurNumRows00
1.3.6.1.4.1.1206.4.2.9.1.3 dcmVehCriteriaTable14
1.3.6.1.4.1.1206.4.2.9.1.4 dcmAxleNumber00
1.3.6.1.4.1.1206.4.2.9.1.5 dcmNumAxles00
1.3.6.1.4.1.1206.4.2.9.1.6 dcmVehicleClass00
1.3.6.1.4.1.1206.4.2.9.1.7 dcmVehicleSpeed00
1.3.6.1.4.1.1206.4.2.9.1.8 dcmVehicleLength00
1.3.6.1.4.1.1206.4.2.9.1.9 dcmFrontOverhang00
1.3.6.1.4.1.1206.4.2.9.1.10 dcmRearOverhang00
1.3.6.1.4.1.1206.4.2.9.1.11 dcmAxleSpacing00
1.3.6.1.4.1.1206.4.2.9.1.12 dcmVehWheelbase00
1.3.6.1.4.1.1206.4.2.9.1.13 dcmVehClearance00
1.3.6.1.4.1.1206.4.2.9.1.14 dcmVehicleHeight00
1.3.6.1.4.1.1206.4.2.9.1.15 dcmAxleWidth00
1.3.6.1.4.1.1206.4.2.9.1.16 dcmVehicleWidth00
1.3.6.1.4.1.1206.4.2.9.1.17 dcmAxleTireCount00
1.3.6.1.4.1.1206.4.2.9.1.18 dcmAxleTireTrack00
1.3.6.1.4.1.1206.4.2.9.1.19 dcmVehicleGap00
1.3.6.1.4.1.1206.4.2.9.1.20 dcmVehicleHeadway00
1.3.6.1.4.1.1206.4.2.9.1.21 dcmLeftWheelWeight00
1.3.6.1.4.1.1206.4.2.9.1.22 dcmRightWheelWeight00
1.3.6.1.4.1.1206.4.2.9.1.23 dcmAxleWeight00
1.3.6.1.4.1.1206.4.2.9.1.24 dcmSensorWeight00
1.3.6.1.4.1.1206.4.2.9.1.25 dcmGrossVehicleWeight00
1.3.6.1.4.1.1206.4.2.9.1.26 dcmVehicleSeqNum00
1.3.6.1.4.1.1206.4.2.9.1.28 dcmAxleWeightViolationCode00
1.3.6.1.4.1.1206.4.2.9.1.29 dcmVehicleAcceleration00
1.3.6.1.4.1.1206.4.2.9.1.30 dcmNumVehicleIDs00
1.3.6.1.4.1.1206.4.2.9.1.31 dcmVehicleID00
1.3.6.1.4.1.1206.4.2.9.1.32 dcmVehicleTimeTag100000