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)
Related source files and packages:
Show more related files and packages
- 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)
Related source files and packages: