| Attribute | Value |
|---|---|
| Item | Lane Centering Assist (LCA) — keeps vehicle in lane at highway speeds |
| Function | Apply steering torque to maintain vehicle in lane centre; active > 60 km/h |
| Sensors | Front camera (lane markings), front radar (vehicle ahead) |
| Actuator | EPS ECU receives steering request from LCA ECU via CAN (ASIL-D interface) |
| Driver interface | Green LED on steering wheel when active; hands-off detection via torque sensor |
| Operating range | 60–180 km/h; straight roads and curves with radius > 150 m |
System Scenario: Lane Centering Assist (LCA)
Exercise 1: Systematic Hazard Identification
# LCA HARA — Hazard Identification Worksheet
## Method: Guide Words × Functions
Guide words: Omission, Commission, Late, Early, High, Low, Wrong direction
## Function: Apply steering torque to maintain lane centre
| ID | Guide Word | Failure Mode | Hazardous Event |
|-------|-------------|-------------------------------------------|----------------------------------------|
| HE-01 | Commission | Unintended steering torque applied | Vehicle departs lane unintentionally |
| HE-02 | Omission | No steering torque when needed | Vehicle drifts; driver must take over |
| HE-03 | High | Excessive steering torque (> driver can override) | Vehicle swerves into adjacent lane |
| HE-04 | Late | Steering response delayed > 200ms | Delayed correction; vehicle departs curve |
| HE-05 | Wrong dir | Steering torque in wrong direction | Vehicle driven toward lane marking (not away) |
| HE-06 | Commission | LCA activates below 60 km/h | Unexpected steering at city speeds |
## Function: Detect lane markings via camera
| ID | Guide Word | Failure Mode | Hazardous Event |
|-------|-------------|-------------------------------------------|----------------------------------------|
| HE-07 | Omission | No lane detection (fog, rain, faded markings) | LCA disables; driver not warned |
| HE-08 | Commission | False lane detection | Steering toward phantom lane line |
| HE-09 | Wrong value | Lane position error > 0.3 m | Vehicle off-centre with no fault detected |
## Function: Hands-off detection
| ID | Guide Word | Failure Mode | Hazardous Event |
|-------|-------------|-------------------------------------------|----------------------------------------|
| HE-10 | Omission | Hands-off not detected | LCA active; driver not monitoring |
| HE-11 | Commission | False hands-on (ghost torque) | System thinks driver is in control when not |Exercise 2: ASIL Classification for LCA
# LCA HARA — ASIL Classification
| ID | Hazardous Event | Scenario | S | E | C | ASIL |
|-------|--------------------------------------|-----------------------|-----|-----|-----|--------|
| HE-01 | Unintended steering (moderate torque)| Highway, v=120 km/h | S3 | E4 | C3 | ASIL-D |
| HE-02 | No steering torque | Highway curve | S2 | E3 | C2 | ASIL-B |
| HE-03 | Excessive torque (> 5 Nm) | Highway, v=120 km/h | S3 | E4 | C3 | ASIL-D |
| HE-04 | Delayed response > 500ms | Highway curve | S2 | E3 | C3 | ASIL-C |
| HE-05 | Wrong-direction torque | Highway, v=100 km/h | S3 | E4 | C3 | ASIL-D |
| HE-06 | Activation at low speed | City, v=30 km/h | S1 | E4 | C2 | ASIL-A |
| HE-08 | False lane detection → wrong steer | Highway, v=130 km/h | S3 | E3 | C3 | ASIL-D |
| HE-09 | Lane position error > 0.3 m | Highway, v=100 km/h | S2 | E4 | C2 | ASIL-C |
| HE-10 | Hands-off undetected | Highway, v=130 km/h | S2 | E3 | C2 | ASIL-B |
## Most Critical: HE-01, HE-03, HE-05, HE-08 → ASIL-D
## Safety Goals Derived:
SG-01 [ASIL-D]: Avoid unintended LCA steering torque > 2 Nm when no lane correction needed
SG-02 [ASIL-D]: Avoid LCA steering torque exceeding driver override threshold (> 4 Nm)
SG-03 [ASIL-D]: Avoid LCA steering in wrong direction relative to lane deviation
SG-04 [ASIL-D]: Avoid LCA activation based on falsely detected lane markingSummary
The LCA HARA exercise shows a common pattern: multiple hazardous events converge on ASIL-D, driven by the combination of high severity (S3 — lane departure at highway speed) and high exposure (E4 — highway driving is continuous). The guide-word method is effective for systematic hazard identification because it forces the team to consider both omission (function fails to act) and commission (function acts unintentionally) failure modes for each function. HE-05 (wrong-direction torque) is particularly insidious: if the safety monitor is checking for 'steering torque too high' but not for 'steering torque in wrong direction', the hazard is unmitigated.
🔬 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.