1 Public ETAS/SIN ETAS GmbH All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as

Transcription

1 1 Public ETAS/SIN ETAS GmbH All rights reserved, also regarding any disposal, exploitation, reproduction,

2 Overview of OBD Development process 2 Public ETAS/SIN ETAS GmbH All rights reserved, also regarding any disposal, exploitation, reproduction,

3 Common OBD Validation/ Calibration Specific requirements Engineers need to validate/ calibrate OBD Algorithms that are related to functions such as Sensor Plausibility Check ( IAF, MAF, ECT, CHT, Lambda) Sensor OC, SCB, SCG faults Sensor Thresholds De-bounce timings for fault setting. Tester functionality Fault Memory setting/ clearing MiL lamp setting Component monitoring such as DPF/ CatCon regeneration monitoring Misfire monitoring etc. 3 Public ETAS/SIN ETAS GmbH All rights reserved, also regarding any disposal, exploitation, reproduction,

4 Challenges in OBD Calibration/ Validation process Increase in number of variants but reduction in number of test vehicles Reduced development time but extended scope Increasing number of software releases which means increased need for testing impacting the cost and time constraints of the project. Addition of further components to the OBD sensor set: NOx sensor, PM sensor, NH3 slip sensor etc. Growing number of OBD modules and OBD calibration parameters. Stricter certification framework conditions. 4 Public ETAS/SIN ETAS GmbH All rights reserved, also regarding any disposal, exploitation, reproduction,

5 Challenges in Automation of Validation/ Calibration tasks Several bench based options are available but in vehicle validation remains as important as it was always There are several script based options available for automating in vehicle validation & calibration. But all of them require scripting expertise. Scalability Scripting Knowledge This leads to a few basic issues such as Software development skills collide with calibration expertise Unsatisfactory flexibility in the car Validation engineer has no chance to apply -even minor- modifications Unclear transparency (black-box) Project Managemen t Flexibility 5 Public ETAS/SIN ETAS GmbH All rights reserved, also regarding any disposal, exploitation, reproduction,

6 INCA- Flow as a tool Design Modeling Implementation Execution Planning & Design of the required work steps for the application task Graphical modeling with ready-to-use building blocks for automotive application task Generation of standalone executable for distribution Online application in the vehicle Documentation Detailed preparation of calibration and validation work in the office Less time in vehicle required 6 Public ETAS/SIN ETAS GmbH All rights reserved, also regarding any disposal, exploitation, reproduction,

7 A process based approach to solve problem Any OBD Calibration task/ Validation task revolves around executing a few steps that can be represented/approximated as the following The difference between a pure validation & calibration + validation task is highlighted in Yellow & black. Start Start Recording Stop Recording Process Init Do Calibration/ Execute Test Case Calibration / Test Preconditions met Yes No Test if system behavior is as per requirement Yes Process End End 7 Public ETAS/SIN ETAS GmbH All rights reserved, also regarding any disposal, exploitation, reproduction,

8 How to think INCA-Flow Calibration / Validation Task Base methods Flowchart Executable Library methods Base methods Read / Write of characteristics and signals User input/output functions Design methods (i.e.. Polyfit) Optimization methods (i.e. Simplex algorithm) Iterations (i.e. loops) Bypass methods (i.e. configurable PID governor) Stimuli generation (i.e. sine-wave, APRBS) Drive-cycle generation (i.e. FTP75-cycle) Interface to MATLAB Mathematical and statistical methods (formula editor, fourier transformation, filters, histogram, mean-/min-/max value etc.) Visualization methods (oscilloscope, histogram generation and modification of curves and maps) Library methods For re-use of commonly used sub-sequences INCA-Flow creates graphical and executable specifications for application processes! INCA-Flow 8 Public ETAS/SIN ETAS GmbH All rights reserved, also regarding any disposal, exploitation, reproduction,

9 Advantages Process Based Calibration/Validation Procedures The engineer uses the methods available in INCA- Flow and designs the validation/ calibration process as a Flowchart. It is step by step, readable and easy to understand and results are repeatable. Escape the ECU parameter trap by re using processes INCA Flow has in built layers of abstraction that helps the engineers escape the ECU label trap, i.e. the validation process can be designed independent of the ECU vendor INCA Flow OBD Calibration/ Validation Process User Defined Elements ECU Labels 12 Only mapping needs to be altered Other processes OBD Calibration/ Validation Process ECU Labels 12 Entire Process needs to get altered 9 Public ETAS/SIN ETAS GmbH All rights reserved, also regarding any disposal, exploitation, reproduction,

10 Advantages (Contd..) INCA Flow is Integrated to INCA INCA Flow is directly integrated with INCA s database which offers dataset management. Easy transfer of tasks with re usable databases and experiments and workspaces already configured in INCA INCA Read measurement data INCA-Flow Write calibration data 10 Public ETAS/SIN ETAS GmbH All rights reserved, also regarding any disposal, exploitation, reproduction,

11 Advantages (Contd..) Reporting and Documentation One Click HTML documentation with complete traceability with regard to Validation process flow with parent-child style traceability Dataset used Process description Labels used Measurement file links Custom documentation available through custom DLL calls or COM API based calls. 11 Public ETAS/SIN ETAS GmbH All rights reserved, also regarding any disposal, exploitation, reproduction,