🎓 Lesson 16
D5
Building ISO 11783-6 Compliant Display Templates
An ISO 11783-6 compliant display template is a standardized digital layout for farm or mining machinery screens that ensures any compatible device can correctly show controls and data—like a universal app interface for heavy equipment.
🎯 Learning Objectives
- ✓ Design a VT display template that conforms to ISO 11783-6 object pool constraints
- ✓ Analyze VT message sequences to verify correct object instantiation and update timing
- ✓ Apply ISO 11783-6 state machine rules to implement modal behavior (e.g., password-protected calibration screens)
- ✓ Explain the functional relationship between VT Object IDs, ECU-provided data objects, and CAN message PGNs
📖 Why This Matters
In modern mining fleets, operators use multi-vendor equipment—from CAT drills to Komatsu haul trucks—all controlled via shared ISOBUS displays. Without ISO 11783-6 compliance, a blast design screen built for one vendor’s VT may crash, misrender, or fail to receive real-time borehole data from another vendor’s drill ECU. This lesson bridges software design and field interoperability: mastering VT templates isn’t just about pixels—it’s about safety-critical command integrity, regulatory certification (e.g., ISO/IEC 17065), and avoiding costly integration rework during fleet automation upgrades.
📘 Core Principles
ISO 11783-6 builds on the ISOBUS architecture (ISO 11783-2/5/7) by defining a strict object-oriented framework for VTs. Every interactive element—button, gauge, or list—is an 'object' with a unique 16-bit Object ID, type (e.g., OBJ_TYPE_BUTTON = 0x01), and properties (size, position, color). Objects reside in a hierarchical 'object pool' loaded at VT startup; dynamic updates occur via VT-ECU messages (PGN 65280) referencing these IDs. Critically, the standard enforces state management: e.g., a 'Blast Initiation Confirm' button must transition through enabled → pressed → disabled → confirmed states per defined timing windows (≤ 200 ms response) to prevent accidental activation. Understanding memory mapping (object pool size ≤ 64 kB), object lifetime (persistent vs. transient), and ECU-VT synchronization (via VT Status messages, PGN 65279) is foundational to robust design.
📐 Object Pool Memory Budget Calculation
The total memory required for a VT template’s object pool depends on object count, type complexity, and attribute overhead. Exceeding the ISO-specified 64 kB limit causes ECU rejection or VT boot failure. This calculation ensures scalability before hardware deployment.
Object Pool Memory Requirement
M_total = Σ(N_i × S_i) × 1.1Total memory (bytes) required for the VT object pool, including 10% overhead for alignment and metadata.
Variables:
| Symbol | Name | Unit | Description |
|---|---|---|---|
| M_total | Total object pool memory | bytes | Allocated memory footprint for all objects and metadata |
| N_i | Number of objects of type i | count | Quantity of each object type (e.g., buttons, sliders) |
| S_i | Base size per object of type i | bytes | Minimum memory per object, per ISO 11783-6 Annex B |
Typical Ranges:
Small drill rig VT: 1.5 – 8 kB
Full-fleet mine operations center VT: 32 – 62 kB
💡 Worked Example
Problem: A mining VT template includes: 12 buttons (OBJ_TYPE_BUTTON), 8 numeric displays (OBJ_TYPE_NUMERIC), 3 list boxes (OBJ_TYPE_LIST_BOX), and 1 bitmap background (OBJ_TYPE_BITMAP). Use ISO 11783-6 Annex B memory estimates.
1.
Step 1: Assign base sizes — Button = 24 bytes, Numeric = 40 bytes, List Box = 64 bytes, Bitmap = 1200 bytes (for 240×135 px, 16-bit color)
2.
Step 2: Calculate total: (12 × 24) + (8 × 40) + (3 × 64) + 1200 = 288 + 320 + 192 + 1200 = 2000 bytes
3.
Step 3: Add 10% overhead for alignment and metadata: 2000 × 1.1 = 2200 bytes (< 64 kB → compliant)
Answer:
The object pool requires 2.2 kB, well within the ISO 11783-6 maximum of 65,536 bytes (64 kB).
🏗️ Real-World Application
At Rio Tinto’s Pilbara iron ore operation, a custom VT template for blast hole depth verification was deployed across 42 drill rigs (Sandvik DD422i, Boart Longyear LF90). The template used ISO 11783-6 OBJ_TYPE_SLIDER for depth adjustment, OBJ_TYPE_TEXT for rock hardness class (fed from geotech ECU), and OBJ_TYPE_INDICATOR for real-time deviation alerts. During integration testing, non-compliant object ID reuse (two buttons sharing ID 0x01F2) caused intermittent CAN bus errors on 17% of rigs. Remediation involved strict ID allocation per ISO Table 11 (Object ID ranges) and adding VT Status polling (PGN 65279) to detect object pool load failures—reducing field commissioning time by 63%.
🔧 Interactive Calculator
🔧 Open ISOBUS Virtual Terminal (VT) Configuration & Interoperability Calculator📋 Case Connection
📋 VT Display Layout Standardization Across 12 Seeder Brands
Operator confusion due to inconsistent screen layouts, button placement, and parameter labeling across brands