🎓 Lesson 5
D3
Virtual Terminal (VT) Message Structure and Diagnostic Event Mapping
A Virtual Terminal (VT) message is a standardized digital 'note' sent between farm or mining equipment and a display screen so they can understand each other’s commands and status—like a universal language for machines.
🎯 Learning Objectives
- ✓ Explain the role of VT Object Pool IDs in diagnostic event mapping
- ✓ Analyze a VT message hex dump to identify diagnostic event type, severity, and source address
- ✓ Apply ISO 11783-6 Annex D mappings to decode a Class 3 Diagnostic Event message into actionable fleet alerts
- ✓ Design a minimal VT message sequence for reporting a hydraulic pressure fault in a drilling rig’s blast delivery system
📖 Why This Matters
In modern mining fleets, blast timing, charge delivery, and drill rig diagnostics rely on real-time ISOBUS communication—not just between tractors and implements, but between blast control units and telematics gateways. Misinterpreting a VT diagnostic message can delay fault response by hours, risk misfired charges, or trigger unnecessary equipment shutdowns. Mastering VT message structure ensures engineers can trace root causes in mixed-vendor environments—where a Komatsu drill, John Deere VT display, and third-party blast telemetry must interoperate flawlessly.
📘 Core Principles
VT messages are built on three foundational layers: (1) The CAN frame (ISO 11783-2), carrying a 29-bit PGN (Parameter Group Number) that identifies message class; (2) The VT Application Layer (ISO 11783-6), defining how objects (buttons, gauges, alarms) are instantiated, updated, and referenced via Object Pool IDs (OPIDs); and (3) Diagnostic Event Mapping (ISO 11783-12), which standardizes how faults—e.g., 'Low Nitro-Glycerin Line Pressure'—are encoded using Class 3 Diagnostic Events. Critically, VT messages do not transmit raw sensor values directly; instead, they reference pre-defined OPIDs linked to semantic descriptors in the VT’s object pool. A diagnostic event maps to an OPID that points to a standardized description in the VT’s internal dictionary—ensuring consistent interpretation regardless of display vendor.
📐 VT Diagnostic Event Decoding Formula
To map a received VT message to a human-readable diagnostic, engineers apply the Diagnostic Event Indexing Rule: the 16-bit 'Event ID' field in a Class 3 Diagnostic Event PDU is resolved using the VT’s Object Pool lookup table, where Event ID = OPID − Base Offset (0x4000). This yields the index into the standardized Diagnostic Event Dictionary (ISO 11783-12 Table 5).
Diagnostic Event OPID Resolution
OPID = Base_Offset + Event_IDCalculates the Object Pool ID from a Class 3 Diagnostic Event’s embedded Event ID field.
Variables:
| Symbol | Name | Unit | Description |
|---|---|---|---|
| OPID | Object Pool Identifier | hexadecimal (16-bit) | Index into VT’s internal object dictionary; determines displayed text and severity behavior. |
| Base_Offset | Diagnostic Base Offset | hexadecimal | Fixed value (0x4000) reserved for diagnostic event OPIDs per ISO 11783-6 Annex D. |
| Event_ID | Diagnostic Event Identifier | hexadecimal (16-bit) | Vendor-neutral code assigned to a specific fault condition in ISO 11783-12. |
Typical Ranges:
Valid diagnostic events: 0x0001 – 0x1FFF
💡 Worked Example
Problem: A VT message with PGN 65260 (Class 3 Diagnostic Event) contains Event ID = 0x02A8 (680 decimal). The VT uses base offset 0x4000 for diagnostic OPIDs. What OPID does this represent, and which diagnostic event is triggered per ISO 11783-12?
1.
Step 1: Convert hex Event ID 0x02A8 → decimal = 680
2.
Step 2: Apply resolution formula: OPID = Base Offset + Event ID = 0x4000 + 0x02A8 = 0x42A8 (17064 decimal)
3.
Step 3: Consult ISO 11783-12 Table 5: OPID 17064 maps to 'Hydraulic Pressure Below Threshold in Blast Delivery Manifold (Severity Level 2)'
Answer:
The result is OPID 0x42A8, corresponding to a medium-severity hydraulic pressure fault in the blast delivery manifold—requiring immediate verification before next round initiation.
🏗️ Real-World Application
At Newmont’s Boddington Mine (WA), a Cat MD6310 drill rig reported intermittent 'Charge Pump Fault' alerts on its John Deere Operations Center VT display. Field engineers captured the VT CAN trace and identified PGN 65260 with Event ID 0x01F4. Using ISO 11783-12, they resolved OPID = 0x4000 + 0x01F4 = 0x41F4 → mapped to 'Variable Displacement Pump Swashplate Position Sensor Drift'. This led to targeted calibration—not a full pump replacement—reducing unplanned downtime by 72 hours/month. The same event was simultaneously logged by the mine’s telematics platform (via ISOBUS gateway) using the identical OPID, enabling automated alert routing to maintenance dispatch.
🔧 Interactive Calculator
🔧 Open Telematics Data Schema Interpretation for Fleet Diagnostics Calculator📋 Case Connection
📋 Canadian Prairie Grain Transport Telematics Integration
Inconsistent payload reporting across OEMs led to inaccurate load reconciliation and bin-fill forecasting