1 SESSION OPENING

Telecoding module Project ECU Session opened by:

Selected

Activated

NOT selected

Select a ECU Modify a paramter (and the new value to be written) Select a LID/DID in the rolling

Selected

Activated

Selected (session closed)

Selected

Activated

Selected (session closed) box Sub-function

Selected NOT selected

Activated Activated

Selected (session closed) Selected

Click on the Start cycle button Activate telecoding module

1.1

In KWP for body ECUs, a session opening goes as follows :

1) Session opening (StartDiagnosticSession Mode session communication diagnostic actif). 2) If ECU is secured, unlock ECU (Unlocking request SecurityAccess#1 followed by an unlocking confirmation SecurityAccess#2). Reading traceability for ECU telecoding (Reading of LID A0: see Telecoding traceability).

1.2

In UDS for body ECUs, a session opening goes as follows :

1) Session opening (DiagnosticSessionControl Type ExtendedDiagnosticSession). 2) If ECU is secured, unlock ECU (Unlocking request SecurityAccess#1 followed by an unlocking confirmation SecurityAccess#2). Read traceability for ECU telecoding (Reading of DID 2901 followed by reading of DID C000: see Telecoding traceability).

1.3

In KWP for BSI ECUs, a session opening goes as follows :

1) Session opening (StartDiagnosticSession Mode session communication diagnostic actif). 2) If ECU is secured, unlock ECU (Unlocking request SecurityAccess#1 followed by an unlocking confirmation SecurityAccess#2). 3) If the indirection table is not loaded in the projects activation session, loading of the indirection table (RequestUpload).

Reading traceability for ECU telecoding (Reading of LID A0: see Telecoding traceability). 1.4

For drive train ECUs, a session opening goes as follows :

1) Session opening (StartCommunication). 2) If ECU is secured, unlock ECU (Unlocking request SecurityAccess#1 followed by an unlocking confirmation SecurityAccess#2). 3) Reading traceability for ECU telecoding (Reading of LID A0: see Telecoding traceability). Note: For drive train ECUs, LID A0 is the only LID for reading data. It contains, among others, telecoding traceability.

Dfgdfgdf
Following table summarizes different views for Telecoding menu :

Activated project

Selected ECU

DOTE loaded (and mapping table if needed)

DOTE view

ECU view

Colorization DOTE view

Colorization ECU view

Active elements

No

No

No

No

No

None

No

Yes

No

No

Yes

No

Sub-function menu DOTE data Check box Sub-function menu

No

Yes

Yes

Yes

Yes

Yes

No DOTE data Check box Sub-function menu DOTE data Check box E

Yes

Yes

No

No

Yes

No Cycle duration (ms) field Start cycle button

Yes Yes Yes

No No Yes

Yes No Yes

No No Yes

No No Yes

Yes

Yes

Remark : Concerning the "active elements" column, it goes without saying that the unspecified elements in the column are inactive.

Following table summarizes the contents of DOTE/ECU views depending on ECU type and on subFunction menu :
ECU type DRIVE TRAIN DRIVE TRAIN DRIVE TRAIN BSI, BODY Selected subfunction LID A0 DOTE view display ECU view display Parameters of LID A0 with read values Parameters of LID A0 with read values Parameters of LID A0 with read values Parameters of LID X with read values Parameters of messaging service with read values Parameters of all LIDs without read values

DOTE parameters

All

All DOTE parameters

All DOTE parameters DOTE parameters corresponding with parameters of ECU view All DOTE parameters

LID/DID X

BSI, BODY

All

BSI, BODY

All DOTE parameters

A DOTE value can be modified directly from the DOTE view by clicking on the row value corresponding to mnemonic.

This value change has to be taken into account by the affected DOTE mnemonic (colorization change), but this change must not affect the DOTE file, only Diamux interface.
This new value has to be stored in a way that it could be displayed again in DOTE view when the parameter will be read again.

Table below describes content of rolling menu in different cases :

Project activated No Yes Yes Yes/No

ECU selected No No Yes Yes

DOTE selected (+mapping table if necessary) Yes/No No No No

DOTE data check box ticked Yes/No Yes/No Yes No

ECU type

Data type

DRIVE TRAIN / BSI / Body DRIVE TRAIN / BSI / Body DRIVE TRAIN / BSI / Body DRIVE TRAIN / BSI / Body

Nothing Nothing Nothing All DIDs/LIDs

Yes/No

Yes

No

Yes

Nothing

Yes/No

Yes

Yes

No

All DIDs/LIDs

Yes/No

Yes

Yes

Yes

DOTE data

-For BSI 2004, traceability writing is only performed if a LID Bx occurred, but not after a LID Cx writing. -The DOTE writing button begins to telecode the data contained in DOTE. It works the following way :
Reading all messaging service data: allows to get the values for all parameters which may not appear in the DOTE (cases of inconsistency DOTE/Messaging service, or missing parameters in the DOTE), in order to rewrite these data with their read value instead of 0. Read/write DIDs/LIDs cycles in DOTE: writing and checking each writable DOTE data (LID by LID writing). Telecoding traceability writing if ECU is secured and followed by a session closing. Displaying DOTE writing report: differences between backup file and messaging service parameters displayed in a pop up window (missing or supplementary parameters, differences between read and written values). read all parameters of DOTE, write and read, (write and read traceability), close session.

If no problem occurred and all writing requests received a positive answer, then a pop up window is displayed with message DOTE writing done OK . If at least a request received a negative answer, then the pop up window has to display the name for sub-function which couldnt be written.

- The

Save telecoding button allows storing <Sub-functions/Parameter/value> information in XML format, for all writable LIDs/DIDs. On this purpose, Diamux has to read all of these writable parameters. read all sub-function User can choose the backup filename.
Remark : Telecoding backup files have to be compatible from a version to another. It has to be reusable with any Diamux version.

- The Restore telecoding button allows reloading data from XML backup file. The following actions are applied :
Analyzing differences between backup file and messaging service (displaying differences in a pop up window with a choice : Continue or Interrupt ) - If confirmed by user, restoring backup and read/write cycles of writable DIDs/LIDs in ECU (LID by LID writing). - Writing telecoding traceability if ECU is secured. - Displaying restoration report: differences between read and written values. read all writeable parameters, write and read parameters, (write and read traceability), read all parameters. If no problem occurred and all writing requests received a positive answer, then a pop up window is displayed with the message Restoration done OK . If at least a request received a negative answer, then the pop up window has to display the name for sub-function which couldnt be restored.