1. AVTC Model Based Design Curriculum Development Project Parallel Supervisory Control Presenter: Trevor Crain University of Washington

2. Remediation Diagnostics + Evaluation Component Level Component Level System Level System Level Mode Selection Signal Level Signal Level Diagnostics Subsystems

3. Component Diagnostics Overview Component Diagnostics Four primary questions: 1.Is the component’s ECU on? 2.What functionality is the ECU allowing? 3.What functionality should you allow? 4.Did it respond to your requests?

4. Distributed Control in Vehicles Component Diagnostics Most modules perform their own diagnostics on their inputs/outputs and will take action independently Usually report status over CAN network Supervisor’s Default Actions based on Fault Severity Low: Report but continue as normal Med:Reduce functionality of component High:Temporarily prevent component use Critical:Prevent component use until faults cleared

5. Supervisor Role – Evaluate Component Status Component and System Diagnostics Has the component ECU reported any faults? If faults exist, how have they limited operation? – Don’t ask for more than component can deliver Is that assessment actually correct? – There may be more diagnostics to run – OEM production code vs. prototype controllers Create requirements for supervisor’s assessment

6. Let’s Make Some Component Checks! Component Diagnostics Simulink Assignment: – In the supervisor’s Signal Diagnostics, design BMS diagnostics for each noted signal. – Decide if faults should be latching or not – Draft requirements for each diagnostic, along with tests to validate your checks – In Component Diagnostics, decide what values for which signals should trigger the component to be Online, Offline, or Limited – In System Diagnostics, decide if BMS being Online, Offline, or Limited should make whole eSystem be Online, Offline, or Limited