Status in source: optional.
Names: dcmAxleWeightViolationCode
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"dcmAxleWeightViolationCode",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"(",
"0",
".",
".",
"16711425",
")",
"ACCESS",
"not-accessible",
"STATUS",
"optional",
"DESCRIPTION",
"\"Indicates axle-specific violations (e.g., axle overweight) for the specified vehicle. Setting a bit to one (1) indicates that the associated condition is true. This object is a bitmap. The bit assignments are: OtherWeightViolation (bit 0) – if a weight violation not defined below has been detected. SteeringViolation (bit 1) – if the allowable steering axle weight has been exceeded and if this axle is part of a steering axle group. SingleAxleViolation (bit 2) – if the allowable single axle weight has been exceeded and if this axle is a single axle. TandemAxleViolation (bit 3) - if the allowable tandem axle weight has been exceeded and if this axle is part of a tandem axle group. TridemAxleViolation (bit 4) - if the allowable tridem axle weight has been exceeded and if this axle is part of a tridem axle group. QuadremAxleViolation (bit 5) - if the allowable quadrem axle weight has been exceeded and if this axle is part of a quadrem axle group. AxleBalanceViolation (bit 6) – if the difference between axle weights within an axle group exceeds a pre-defined threshold. AxleGroupIndividualViolation (bit 7) – if the maximum weight ‘individual axle’ threshold for an individual axle within an axle group has been exceeded. BridgeViolation (bit 8) –if this axle is part of any combination of axles which exceed the maximum bridge weight threshold. WheelViolation (bit 9) - if the allowable wheel weight for any single wheel (group of tires) on an axle has been exceeded. WheelImbalanceViolation (bit 10) – if the imbalance between wheel weights on an axle exceeds a pre-defined threshold. The definition of what constitutes a violation is NOT defined by this standard. If a violation has been detected the corresponding bit shall be set to 1. Thus, if no violation has been detected, the value of this object is zero (0). This object is a multiple-occurrence object where the number of occurrences is equal to the number of axles detected for this vehicle. All unused bits are reserved.\"",
"::=",
"{",
"dcmVehCriteria",
"28",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"integerSubType",
[
[
0,
16711425
]
]
]
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"optional"
],
[
"DESCRIPTION",
"Indicates axle-specific violations (e.g., axle overweight) for the specified vehicle. Setting a bit to one (1) indicates that the associated condition is true. This object is a bitmap. The bit assignments are: OtherWeightViolation (bit 0) – if a weight violation not defined below has been detected. SteeringViolation (bit 1) – if the allowable steering axle weight has been exceeded and if this axle is part of a steering axle group. SingleAxleViolation (bit 2) – if the allowable single axle weight has been exceeded and if this axle is a single axle. TandemAxleViolation (bit 3) - if the allowable tandem axle weight has been exceeded and if this axle is part of a tandem axle group. TridemAxleViolation (bit 4) - if the allowable tridem axle weight has been exceeded and if this axle is part of a tridem axle group. QuadremAxleViolation (bit 5) - if the allowable quadrem axle weight has been exceeded and if this axle is part of a quadrem axle group. AxleBalanceViolation (bit 6) – if the difference between axle weights within an axle group exceeds a pre-defined threshold. AxleGroupIndividualViolation (bit 7) – if the maximum weight ‘individual axle’ threshold for an individual axle within an axle group has been exceeded. BridgeViolation (bit 8) –if this axle is part of any combination of axles which exceed the maximum bridge weight threshold. WheelViolation (bit 9) - if the allowable wheel weight for any single wheel (group of tires) on an axle has been exceeded. WheelImbalanceViolation (bit 10) – if the imbalance between wheel weights on an axle exceeds a pre-defined threshold. The definition of what constitutes a violation is NOT defined by this standard. If a violation has been detected the corresponding bit shall be set to 1. Thus, if no violation has been detected, the value of this object is zero (0). This object is a multiple-occurrence object where the number of occurrences is equal to the number of axles detected for this vehicle. 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: