Konzeption und Implementierung eines modularen Frame …1-ed Highest performance at minimal...

Cop

yrig

ht ©

4/1

0/20

11 e

mot

ive

Gm

bH -

All

right

s re

serv

ed

Content

3

Ope

n D

iagn

ostic

Wor

kflo

w

Highlights Architecture OTX-Designer System Requirements License model Screenshots Release Plan Summary

Cop

yrig

ht ©

4/1

0/20

11 e

mot

ive

Gm

bH -

All

right

s re

serv

ed Diagnostic runtime system

Standardized programming

interface for ECU

communication

MVCI-Server ISO 22900

Diagnostic database

Standardized exchange

format for diagnostic data

ODX ISO 22901

Basic Technologies (Standards)

4

Ope

n D

iagn

ostic

Wor

kflo

w


Diagnostic sequences

Standardized exchange

format for diagnostic

sequences

OTX ISO 13209

Cop

yrig

ht ©

4/1

0/20

11 e

mot

ive

Gm

bH -

All

right

s re

serv

ed

Highlights & Design Characteristics

5

Ope

n D

iagn

ostic

Wor

kflo

w


Data-driven solution for the complete diagnostic process chain

Specification, realisation, validation, documentation & test of OTX sequences

Independant of diagnostic runtime system

Completely new development

Simple custom extensibility at almost each layer

Concepts for complexity reduction

User group adaption

Connection and generation

GUI/HMI

Flexible usage: Stand-alone or SDK

On-the-fly code generation (C# …, no execution interpreter!)

Native and direct working on OTX data (no im-/export!)

Fast processing of very large OTX

databases

Cop

yrig

ht ©

4/1

0/20

11 e

mot

ive

Gm

bH -

All

right

s re

serv

ed

Principal Architecture

6

Ope

n D

iagn

ostic

Wor

kflo

w


ODF - Open Diagnostic Framework

OTX Runtime Environment

Screen-Designer

Control-Library

Data-Binding

Proprietary Diagnostic RT-Systems SDX*

D-PDU API Legacy RT-Systems Simulation

Standardized Diagnostic RT-Systems

MVCI-Server + PDU-Simulation ODX

OTX-Designer

Activity-Library

Project-Explorer

Test-Environment

Debugger

Unit-Tests

Database-Modul

XML-DB

OTX-API OTX

XQ

uery

VCI - Vehicle Communication Interface

ECU‘s

*SDX = Simple Diagnostic Data Exchange Format by emotive to support proprietary

Diagnostic Runtime Systems

Cop

yrig

ht ©

4/1

0/20

11 e

mot

ive

Gm

bH -

All

right

s re

serv

ed

Highest performance at minimal ressource usage!

Direct storing to XML without transformations

Flexible storage control: Only the parts that are currently in use are being loaded into memory

Database query via XQuery

Handling of practically unlimited large OTX projects

The user hardly feels a difference when handling a large or a small OTX project

Common solutions often are limited in memory (at ca. 100 MB OTX data). Additionally the working speed at large databases decreases quickly

Database Module

7

Ope

n D

iagn

ostic

Wor

kflo

w


OTX database module

OTX

XML database

OTX-API

XQuery

Cop

yrig

ht ©

4/1

0/20

11 e

mot

ive

Gm

bH -

All

right

s re

serv

ed

Runtime Environment

8

Ope

n D

iagn

ostic

Wor

kflo

w


OTX-

Runtime

ODF runtime

ODF-

Runtime Compiler

C#

Database module

OTX-API XML-DB XQuery

Data processing

ca. 3 MB Hard-drive storage requirement ca. 20 MB

OTX runtime environment

OTX

Data supply in OTX format

DLL

Data supply in binary format

Cop

yrig

ht ©

4/1

0/20

11 e

mot

ive

Gm

bH -

All

right

s re

serv

ed

For the runtime system C# code is generated

Alternatively other code may be generated later (Java, Python etc.)

For each OTX document a C# file is generated

Code is well-arragned and slim

The code corresponds the code of an experts for diagnotic sequences

The code is generated, compiled and executed on-the-fly

Advantages:

• Maximal performance

Appropriate also for control tasks

• Minimal ressources usage

Precompiled sequences can be divided in an extremly compact way

• Arbitrary target systems possible

Pocket-PC, browser, tablet PC etc.

Code Generation (OTX-Runtime)

9

Ope

n D

iagn

ostic

Wor

kflo

w


OTX C#

Package Namespace

Document Class

Procedure Method

Cop

yrig

ht ©

4/1

0/20

11 e

mot

ive

Gm

bH -

All

right

s re

serv

ed

Windows Presentation Foundation Windows Presentation Foundation

There can be different screen implementations

The screen implementation is not part of OTX

Inside the screen implementation there is a screen definition for each screen describing the layout of the screen

At runtime the in- and output parameter are mapped to the appropriate control elements

If there is no screen implementation, the in- and output parameters are displayed in tables

As preferable screen implementation .NET WPF is used (Silverlight)

HMI Screens (In- & Output)

10

Ope

n D

iagn

ostic

Wor

kflo

w


ODF-Runtime

OTX-Runtime Screen

Implementation

Screen

Definition XML

Scr

een

-In

terf

ace

Cop

yrig

ht ©

4/1

0/20

11 e

mot

ive

Gm

bH -

All

right

s re

serv

ed

Product Family

11

Ope

n D

iagn

ostic

Wor

kflo

w


ODF – Open Diagnostic Framework

OTX-Designer (Application)

OTX-Viewer (limited OTX-Designer)

OTX-API SDK (Access to OTX data)

OTX-Runtime SDK (Execution of OTX files)

OTX-Designer SDK (OTX-Designer Hosting)

Cop

yrig

ht ©

4/1

0/20

11 e

mot

ive

Gm

bH -

All

right

s re

serv

ed

OTX-Designer Controls

12

Ope

n D

iagn

ostic

Wor

kflo

w


SolutionExplorerControl WorkflowDesignerControl

VariablesTraceControl

DiagComTraceControl ErrorListControl ToolboxServiceControl

Method Calls

Cop

yrig

ht ©

4/1

0/20

11 e

mot

ive

Gm

bH -

All

right

s re

serv

ed

To graphically edit sequences

Every tab corresponds to a OTX procedure

A procedure consists of activities (nodes)

An OTX document may contain an arbitrary number of procedures

Display as generic flow diagram

• Generated from OTX without META data

• Authors may only influence the display quality but not the layout

Sequences may be copied as graphics into other application

A printed sequence displays all essential elements and can be interpreted without further help

Workflow-Designer

13

Ope

n D

iagn

ostic

Wor

kflo

w


Cop

yrig

ht ©

4/1

0/20

11 e

mot

ive

Gm

bH -

All

right

s re

serv

ed

Activities I

14

Ope

n D

iagn

ostic

Wor

kflo

w


An activity corresponds to an OTX node

Types of activities:

• CompoundNode

• ActionNode

Activity with one or more realisations

Activity without realisation

• Term

Activity with result

Linked activiy (nested term)

• Composite activity

Combination of arbitrary activites in one activity, e.g.

ExecuteDiagServiceEx

Transformation of activities

• Activities can be transformed into other activities

• Properties of equal types and names are applied

Name Icon

Selected

property Specification Description

Cop

yrig

ht ©

4/1

0/20

11 e

mot

ive

Gm

bH -

All

right

s re

serv

ed

Activities II Property Grid

15

Ope

n D

iagn

ostic

Wor

kflo

w


Icon

Property

Property

Description

Property value

Description of

activity

Website with

detailed information

Identical

Activity properties are displayed in the property window

Composite activities optionally have a specific property window, see illustration on right hand side

All inputs are validated, see design time validation

Cop

yrig

ht ©

4/1

0/20

11 e

mot

ive

Gm

bH -

All

right

s re

serv

ed

Toolbox

16

Ope

n D

iagn

ostic

Wor

kflo

w


Contains all activities in different views, grouped logically

Activities can be dragged via „Drag & Drop“ into the

workflow designer to valid positions

Via context menu „Add to Favourites“ frequently used

activities can be stored as favourites, optionally including

their current properties

If a pre-coded activity is dragged from toolbox to

designer:

• All pre-coded properties are applied

• Non-existing variables from stored properties are generated

Toolbox data is generated from two XML files, whose paths

are configurable (globally and locally)

Available activities, grouping and coding can be

configured user-specifically

Cop

yrig

ht ©

4/1

0/20

11 e

mot

ive

Gm

bH -

All

right

s re

serv

ed

An OTX file and all inputs are checked against the schema and the

checker rules

Dialogs can only be closed if the input is valid

Errors are being displayed in the error list

If the error refers to an activity, this activity is marked with a red

exclamation mark

The user can create checker rules himself (via program code) and

implement user-specific auther policies

Design Time Validation

17

Ope

n D

iagn

ostic

Wor

kflo

w


Cop

yrig

ht ©

4/1

0/20

11 e

mot

ive

Gm

bH -

All

right

s re

serv

ed

For diagnostic communication and variable change

Each entry contains a timestamp and detailled information about the element

Standing and spinning modue

Data can be saved in text file

Trace Window

18

Ope

n D

iagn

ostic

Wor

kflo

w


Cop

yrig

ht ©

4/1

0/20

11 e

mot

ive

Gm

bH -

All

right

s re

serv

ed

Pre-coding

Variables can be generated wherever needed

References adjustment

Upon changing of a name, all references are updated automatically

Object search

For example, object search finds all positions where variable „abc“ occurs

Undo/Redo

Arbitrary depth, inside designer and project structure

Development environment in German and Englsih

Further languages are integrated easily

General Features

19

Ope

n D

iagn

ostic

Wor

kflo

w


Cop

yrig

ht ©

4/1

0/20

11 e

mot

ive

Gm

bH -

All

right

s re

serv

ed

Supported diagnostic standards:

• MVCI Server API (ISO 22900-3, ASAM MCD-3D Server)

• ODX (ISO 22901-1, ASAM MCD-2D, 2.0.1, 2.0.2, 2.1.0, 2.2.0)

• OTX (ISO/DIS 13209, 0.9.5)

• D-PDU-API (ISO 22900-2)

• CAN (ISO 11898)

• K-Line (ISO 9141)

• UDS (ISO 14229)

• ISOTP (KWP 2000 on CAN, ISO/DIS 15765-3)

• KWP 2000 (ISO 14230)

Supported hardware (Vehicle Communication Interface):

• Bosch MDI

• DSA MDI-G

• samtec HSX, HS+, HSlight

• Vector CANCardXL, CANCaseXL, CANBoardXL

• Furhter interfaces with standardized D-PDU-API Schnittstelle

System requirements

• PC with Windows XP SP2 or higher (incl. 64-Bit)

• .NET Framework 3.5

Standards, Hardware & System Requirements

20

Ope

n D

iagn

ostic

Wor

kflo

w


Cop

yrig

ht ©

4/1

0/20

11 e

mot

ive

Gm

bH -

All

right

s re

serv

ed

Development license

Editions

• Professional edition

OTX-Designer, OTX-Viewer, Screen-Designer

• Standard edition

OTX-Designer, OTX-Viewer

• SDK edition (standard or professional)

OTX-API SDK, OTX-Runtime SDK, OTX-Designer SDK

To include in own applications

Includes standard or professional edition

Price like standard or professional edition

Sales agreement for runtime licenses

• Free edition

OTX-Viewer

Two licensing forms

• Full version

• Monthly cancelable rental version

• Interchanging among versions is possible

Single developer or general license

Activating of developement license via internet

Support and maintainance contract mandatory for first license

30 days evaluation version

Runtime license

2 kinds:

• Normal runtime license

OTX-API, OTX-Runtime

• Extended runtime license

OTX-Designer, OTX-API, OTX-Runtime

Single developemer or general license

No activation of runtime licenses

License Model

21

Ope

n D

iagn

ostic

Wor

kflo

w


Cop

yrig

ht ©

4/1

0/20

11 e

mot

ive

Gm

bH -

All

right

s re

serv

ed

Screenshots (Demonstration)

22

Ope

n D

iagn

ostic

Wor

kflo

w


Cop

yrig

ht ©

4/1

0/20

11 e

mot

ive

Gm

bH -

All

right

s re

serv

ed

Version 2.0

• Delivered since Feb. 2010

Version 3.0

• OTX-Designer

• OTX-API SDK

• OTX-Runtime SDK

• OTX-Designer SDK

• OTX 0.9.5

Core

DiagCom

HMI

Exception

Quantities

Event

Plan for future versions:

• Further libraries

• ODX mapping

• Document generating

• OTX-Differ, Merger

• Integration of Windows

Presentation Foundation

• ATX

• …

Release Plan I

23

Ope

n D

iagn

ostic

Wor

kflo

w


Cop

yrig

ht ©

4/1

0/20

11 e

mot

ive

Gm

bH -

All

right

s re

serv

ed

Release Plan II

24

Ope

n D

iagn

ostic

Wor

kflo

w


09 Dec. 2008

Begin of

development of

the ODF

Mile stone Today

09 Feb. 2010

Release ODF

Version 2.0

13 May 2011

Distributable Beta

version of ODF

Version 3.0

(planned)

25 Feb. 2011

DIS-Ballot (Draft

International

Standard)

Core only

28 June 2011

DIS-Release (Draft

International

Standard)

Core only

28 June 2011

Release ODF

Version 3.0

(planned)

19 Dec. 2008

New Work Item

Proposal

submission to ISO

Cop

yrig

ht ©

4/1

0/20

11 e

mot

ive

Gm

bH -

All

right

s re

serv

ed

Summary

25

Ope

n D

iagn

ostic

Wor

kflo

w


Data-driven solution for the complete diagnostic process chain

Specification, realisation, validation, documentation & test of OTX sequences

Independant of diagnostic runtime system

Completely new development

Simple custom extensibility at almost each layer

Concepts for complexity reduction

User group adaption

Connection and generation

GUI/HMI

Flexible usage: Stand-alone or SDK

On-the-fly code generation (C# …, no execution interpreter!)

Native and direct working on OTX data (no im-/export!)

Fast processing of very large OTX

databases

Cop

yrig

ht ©

4/1

0/20

11 e

mot

ive

Gm

bH -

All

right

s re

serv

ed

Contact us!

We can help out.

www.emotive.de

Thank you for your attention!

26

Ope

n D

iagn

ostic

Wor

kflo

w

Further information, videos and screenshots

of current version 2.0 may be found at

Konzeption und Implementierung eines modularen Frame …1-ed Highest performance at minimal...

Documents

Transcript of Konzeption und Implementierung eines modularen Frame …1-ed Highest performance at minimal...