| Attribute | Value |
|---|---|
| Component | Dual-channel Hall-effect steering torque sensor |
| Function | Measure driver steering torque (−10 to +10 Nm); output two independent 0.5–4.5V analog signals |
| Redundancy | Channel A and Channel B are independent sensing elements in same package |
| Safety requirement | [ASIL-D] Detect torque sensor failure within 20 ms; transition EPS to safe state (motor off) |
| Diagnostic | MCU reads both channels every 2 ms; cross-checks difference; range check each channel |
Workshop Scenario: EPS Dual-Channel Torque Sensor
Exercise 1: FMEA for Torque Sensor
Markdowneps_fmea.md
# FMEA: EPS Dual-Channel Torque Sensor
| ID | Element | Failure Mode | Effect (Local) | Effect (System) | S | O | D | RPN | Diagnostic Mechanism | DC% |
|------|-----------------|-----------------------|------------------------|---------------------------|----|----|----|-----|-----------------------------------|------|
| FM-01| Ch-A sensing | Stuck at 0V (open) | Ch-A reads min (−10Nm) | EPS applies max assist unintentionally | 9 | 2 | 2 | 36 | Range check: <0.3V → fault | 97% |
| FM-02| Ch-A sensing | Stuck at 5V (short) | Ch-A reads max (+10Nm) | EPS applies max assist | 9 | 2 | 2 | 36 | Range check: >4.7V → fault | 97% |
| FM-03| Ch-A sensing | Drift ±15% | Ch-A reads wrong torque| Wrong steering assist level| 7 | 2 | 3 | 42 | Cross-check: |Ch-A - Ch-B| > 0.5Nm → fault | 90% |
| FM-04| Ch-B sensing | Stuck at 0V (open) | Ch-B reads min | Diagnostic detects Ch-B fault | 1 | 2 | 1 | 2 | Range check (same as FM-01) | 97% |
| FM-05| Ch-A AND Ch-B | Both drift same direction (CCF)| Both read wrong | No diagnostic triggers! | 9 | 1 | 9 | 81 | DFA required: sensors must be diverse design | 0% |
| FM-06| ADC Ch-A | Conversion error | Wrong digital value | Same as FM-03 | 7 | 2 | 2 | 28 | ADC self-test; reference check | 95% |
| FM-07| Power supply | Undervoltage < 4.5V | Both channels shift low| Cross-check detects difference | 5 | 1 | 2 | 10 | Supply monitor | 95% |
## Key Finding: FM-05 (CCF)
Both sensor channels failing in same direction has DC = 0% with current architecture.
Action: Require DFA evidence that Ch-A and Ch-B use diverse sensing principle
(e.g., Ch-A: Hall effect, Ch-B: magnetostrictive) OR prove CCF rate < 1e-9/hExercise 2: FTA for Loss of Steering Assist
Texteps_fta.txt
Top Event: Loss of steering assist without driver warning (HE: omission of EPS function)
[OR gate]
├── Torque sensor failure AND diagnostic fails to detect
│ [AND gate]
│ ├── Torque sensor total failure [OR gate]
│ │ ├── Ch-A stuck-at + Ch-B stuck-at [AND gate] ← very low probability
│ │ │ └── P = 2e-8/h × 2e-8/h = 4e-16/h
│ │ └── Sensor power supply failure → both channels offline
│ │ └── P = 1e-7/h (with redundant supply: 1e-7 × 1e-7 = 1e-14/h)
│ └── Diagnostic inactive (range check disabled or MCU frozen)
│ └── P = 1e-8/h (SW fault disabling monitor)
│
├── Motor drive circuit failure (inverter)
│ └── P = 5e-8/h (IGBT open circuit; motor phase loss)
│
└── MCU reset (no safe state transition)
└── P = 2e-8/h (power glitch; WDG reset)
Dominant contributor: Motor drive failure (5e-8/h) and MCU reset (2e-8/h)
→ Motor drive FMEA and MCU safe state handling are priority mitigationsSummary
The workshop exercise reveals a critical FMEA finding: FM-05 (both torque sensor channels drifting in the same direction) has zero diagnostic coverage with the cross-check alone, because the cross-check only detects differences between channels. This is the classic common cause failure that DFA must address. The FTA confirms that the dominant failure contributors are not the sensor itself but the motor drive circuit and MCU reset — both of which have higher individual failure rates than the sensor and must be addressed by specific safety mechanisms (motor phase-loss detection, watchdog-triggered safe state).
🔬 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.