OTX ODX. MVCI-Server. Architecture. Diagnostic Sequences. Diagnostic Database. Diagnostic Runtime System

Transcription

1

2 Architecture 3 Diagnostic Database A standardized exchange format for diagnostic data ODX ISO Diagnostic Sequences A standardized exchange format for diagnostic sequences ISO Diagnostic Runtime System A standardized API for communication with the ECU MVCI-Server ISO

3 Architecture 4 ODF - Open Diagnostic Framework Diagnostic Workflows Graphical User Interface Diagnostic Application Workflow Designer Activity Library Data Binding Forms Designer Control Library Build ODF Runtime Integrated Development Environment (Design-Time) Runtime Environment ODX MVCI Server + PDU-Simulation Standardized Diagnostic RT-Systems SDX * D-PDU API Legacy RT-Systems Simulation Proprietary Diagnostic RT-Systems VCI - Vehicle Communication Interface ECU s * SDX = Simple Diagnostic Data Exchange Format by emotive to support proprietary Diagnostic Runtime Systems

4 Use Case 1: Development and Test of Diagnostic Sequences 5 Design & Specification Open Diagnostic Framework Design Time Simulation DiagData Monitoring Parameter Monitoring Debugging PDU-Simulation ODX Reporting Im- & Export Extensibility Diagnostic Runtime System MVCI Server API Legacy Runtime Systems D-PDU API PDU Simulation ECU

5 Use Case 2: Creating and Distributing of Stand- Alone Executable Tester Applications 6 Design Time Environment Runtime Environment Open Diagnostic Framework Workflow Design Stand-alone distributable Diagnostic Application (*.exe) ODX GUI Design PDU-Simulation Debugging Reporting XAML ODF Runtime ODF Core API Extensibility.NET Framework Diagnostic Runtime System MVCI Server API Legacy Runtime Systems D-PDU API PDU Simulation ECU

6 Use Case 3: Integration of Diagnostic Sequences into Existing Systems 7 Design Time Environment Runtime Environment Open Diagnostic Framework Design & Specification Existing System Existing System Existing System ODX Design Time Simulation Debugging Test & Monitoring Reporting ODF Runtime ODF Core API Extensibility.NET Framework Diagnostic Runtime System MVCI Server API Legacy Runtime Systems D-PDU API PDU Simulation Vehicle Vehicle Communication Communication Interface Interface (VCI) (VCI) ECU

7 Features 8 Managing diagnostic sequences: Easy graphical creation, specification, test and debugging of diagnostic sequences Supporting version 0.9.x Comprehensive input validation at designtime Comprehensive standard and diagnostic activity libraries Simple and efficient error management Simulation, stimulation, and analysis of the communication: Universal development tester High-performance, optimized handling of resources, multi-channeling Monitoring of diagnostic communication and variables tracing PDU simulation to use without connected hardware Independent of runtime system Diagnostic runtime system is included Large support of VCIs Creating of stand-alone diagnostic applications: Graphical creation of graphical user interface (GUI) and data binding to diagnostic sequences for in- and output Creation of slim and stand-alone Microsoft Windows executables (*.exe) of high performance Integrated user management Language-Manager to localize the application Open, modern, and familiar development environment (Visual Studio 2008) Simple distribution process of the created application General: Different reporting possibilities (HTML, PDF, SQL) Simple installation on the target system via MSI or MSM Multilingual (de, en) Documentation Consulting

8 Standards, Hardware & System Requirements 9 Supported Diagnostic Standards: MVCI Server API (ISO , ASAM MCD-3D Server) ODX (ISO , ASAM MCD-2D) Beta Version (ISO 13209) D-PDU-API (ISO ) CAN (ISO 11898) K-Line (ISO 9141) UDS (ISO 14229) ISOTP (KWP 2000 on CAN, ISO/DIS ) KWP 2000 (ISO 14230) Supported Hardware (Vehicle Communication Interface): Bosch MDI DSA MDI-G samtec HSX, HS+, HSlight Vector CANCardXL, CANCaseXL, CANBoardXL More interfaces with standardized D-PDU-API System Requirements PC with Windows XP SP2 32-Bit or higher Visual Studio 2008 Standard Edition (for development only).net Framework 3.5

9 Demo 10

10 Summary 12 Easy graphical creation, specification, test and debugging of diagnostic sequences (Rapid Prototyping) Supporting version 0.9.x Graphical creation of graphical user interface (GUI) and data binding to diagnostic sequences for in- and output No programming knowledge required Different possibilities for monitoring and reporting Simulation mode for usage without VCI Creation of stand-alone diagnostic applications Easily extendable at almost each layer Consistent usage of data-driven technologies

11 Thank You for Your Attention! 13 Contact us! We can help out.