| Phase | Purpose | UDS Services Used |
|---|---|---|
| Flash programming | Load production firmware if not pre-flashed | 0x10, 0x27, 0x34, 0x36, 0x37, 0x31 |
| ECU identification | Verify correct ECU hardware + software installed | 0x22 (0xF190 VIN, 0xF189 SW ver, 0xF191 HW ver) |
| Parameter writing | Write VIN, variant coding, plant-specific data | 0x2E (0xF190 VIN, 0x0100–0x01FF) |
| Actuator tests | Verify physical output connectivity (fans, pumps, relays) | 0x2F + 0x31 (actuation routines) |
| Sensor plausibility | Read and validate sensor signals in known conditions | 0x22 (application DIDs) |
| DTC clearance | Clear any production-process DTCs before shipment | 0x14 0xFF 0xFF 0xFF |
| EOL lock/activation | One-time activation routine; prevent unauthorised re-coding | 0x31 (EOL activation routine) |
End-of-Line (EOL) Diagnostic Testing Overview
Typical EOL Sequence Implementation
#!/usr/bin/env python3
# EOL diagnostic sequence: executed on production line for each vehicle unit
import udsoncan, time
from udsoncan.client import Client
def eol_sequence(client, vin: str, variant_code: int) -> dict:
results = {}
# Step 1: Establish session and security
client.change_session(udsoncan.services.DiagnosticSessionControl.Session.extendedDiagnosticSession)
security_access(client, level=1)
# Step 2: Write VIN
vin_bytes = vin.encode('ascii').ljust(17, b' ')[:17]
resp = client.write_data_by_identifier(0xF190, vin_bytes)
results['VIN_write'] = 'PASS' if resp.positive else f"FAIL NRC 0x{resp.code:02X}"
# Step 3: Write variant code
resp = client.write_data_by_identifier(0x0200, bytes([variant_code]))
results['Variant_write'] = 'PASS' if resp.positive else f"FAIL NRC 0x{resp.code:02X}"
# Step 4: Actuator test — cooling fan
fan_resp = client.io_control(0x0210, udsoncan.IOMasks(),
control_option_record=bytes([0x03, 0x64])) # 100%
time.sleep(2)
# Read feedback DID to verify fan running
feedback = client.read_data_by_identifier(0x0211)
fan_rpm = int.from_bytes(feedback.service_data.values[0x0211], 'big')
results['Fan_test'] = 'PASS' if fan_rpm > 800 else f"FAIL: RPM={fan_rpm}"
client.io_control(0x0210, udsoncan.IOMasks(), control_option_record=bytes([0x00]))
# Step 5: DTC clearance
resp = client.clear_dtc(0xFFFFFF)
results['DTC_clear'] = 'PASS' if resp.positive else "FAIL"
# Step 6: EOL activation (one-time, irreversible)
resp = client.routine_control(0x01, 0xDEAD, bytes([0x01])) # EOL lock
results['EOL_lock'] = 'PASS' if resp.positive else "FAIL"
return resultsEOL Automation Architecture
Production Line Control System (PLC / MES)
├── Receives order: VIN + variant code per vehicle unit
└── Triggers: EOL Tester (PC with CAN/DoIP interface)
│
▼
EOL Tester (ESAS, Dürr, or custom Python script)
├── Executes UDS sequence (< 30s per ECU)
├── Logs result (PASS/FAIL per step) to MES
└── Reports final: PASS → vehicle can leave station; FAIL → rework
DoIP path (Ethernet-based ECUs): EOL tool connects via OBD-II port Ethernet
├── Routing activation (0x0005)
├── Full UDS sequence over TCP
└── ~5× faster than CAN for VIN write + parameter programming
Parallel testing: multiple ECUs in parallel if independent CAN networks
CAN: one interface per network; EOL tests can run concurrently on separate busesSummary
EOL testing has four hard constraints: correctness (wrong VIN = compliance failure), speed (seconds per station cycle time), reliability (false failures block production), and repeatability (every unit identical). The EOL sequence should be a deterministic, fully scripted UDS sequence with explicit expected responses for every step — no interactive prompts, no manual operator decisions. The EOL lock (one-time activation routine) prevents unauthorised re-coding or parameter changes after the vehicle leaves the plant, closing the window between EOL test and vehicle delivery.
🔬 Deep Dive — Core Concepts Expanded
This section builds on the foundational concepts covered above with additional technical depth, edge cases, and configuration nuances that separate competent engineers from experts. When working on production ECU projects, the details covered here are the ones most commonly responsible for integration delays and late-phase defects.
Key principles to reinforce:
- Configuration over coding: In AUTOSAR and automotive middleware environments, correctness is largely determined by ARXML configuration, not application code. A correctly implemented algorithm can produce wrong results due to a single misconfigured parameter.
- Traceability as a first-class concern: Every configuration decision should be traceable to a requirement, safety goal, or architecture decision. Undocumented configuration choices are a common source of regression defects when ECUs are updated.
- Cross-module dependencies: In tightly integrated automotive software stacks, changing one module's configuration often requires corresponding updates in dependent modules. Always perform a dependency impact analysis before submitting configuration changes.
🏭 How This Topic Appears in Production Projects
- Project integration phase: The concepts covered in this lesson are most commonly encountered during ECU integration testing — when multiple software components from different teams are combined for the first time. Issues that were invisible in unit tests frequently surface at this stage.
- Supplier/OEM interface: This is a topic that frequently appears in technical discussions between Tier-1 ECU suppliers and OEM system integrators. Engineers who can speak fluently about these details earn credibility and are often brought into critical design review meetings.
- Automotive tool ecosystem: Vector CANoe/CANalyzer, dSPACE tools, and ETAS INCA are the standard tools used to validate and measure the correct behaviour of the systems described in this lesson. Familiarity with these tools alongside the conceptual knowledge dramatically accelerates debugging in real projects.
⚠️ Common Mistakes and How to Avoid Them
- Assuming default configuration is correct: Automotive software tools ship with default configurations that are designed to compile and link, not to meet project-specific requirements. Every configuration parameter needs to be consciously set. 'It compiled' is not the same as 'it is correctly configured'.
- Skipping documentation of configuration rationale: In a 3-year ECU project with team turnover, undocumented configuration choices become tribal knowledge that disappears when engineers leave. Document why a parameter is set to a specific value, not just what it is set to.
- Testing only the happy path: Automotive ECUs must behave correctly under fault conditions, voltage variations, and communication errors. Always test the error handling paths as rigorously as the nominal operation. Many production escapes originate in untested error branches.
- Version mismatches between teams: In a multi-team project, the BSW team, SWC team, and system integration team may use different versions of the same ARXML file. Version management of all ARXML files in a shared repository is mandatory, not optional.
📊 Industry Note
Engineers who master both the theoretical concepts and the practical toolchain skills covered in this course are among the most sought-after professionals in the automotive software industry. The combination of AUTOSAR standards knowledge, safety engineering understanding, and hands-on configuration experience commands premium salaries at OEMs and Tier-1 suppliers globally.