ETAS Bypass Concept

• In the following illustration, Fn denotes the original function that runs on the ECU.

Rapid-Prototyping System

Hook labels

SOURCE_ID

BUFFER-OFFSET

Send data table

Buffer 1

Buffer 2

r pre action hooked service point

Fn

bypass value internally calculated value ECU

Fig. 7-3 Bypass with hooked service points

• Prior to the execution of the original function that runs on the ECU, hooked service points can be used to receive data from the ECU to the rapid prototyping system via a read or receive pre-action. The associated hook codes are usually implemented at the end of the original function.

The hooks receive their source (i.e. SOURCE_ID) and offset (i.e.

BUFFER_OFFSET) information from the associated hook labels.

• During the execution of the original function in the ECU, the rapid prototyping system writes data to a double-buffered send data table that can be accessed by these hooks in the original function. The two buffers are used alternately. Either the resulting bypass value or the value calculated internally by the original function is used.

7.4

Service-Based Bypass

Tip

INTECRIO does not support service-based bypass on an ETK with 8 Mbit/s.

For the service-based bypass , both the input values and the output values of the bypass function are transmitted with the same Distab13 mechanism. After the bypass input data is written to the ETK RAM, the bypass calculation is triggered.

In addition, a channel for writing back bypass results to the ETK where they can be retrieved by the ECU is introduced. Here, each bypassed ECU process uses and calls its own Distab.

This service also contains an inverted Distab mechanism to write back bypass outputs to the ECU. The ECU does not need to apply hooks to the variables written to, since the service simply overwrites the values with the bypass outputs.

INTECRIO sets up a Distab-like sorted address table with the addresses of the

ECU variables to be written to, and writes the corresponding values in a table of

INTECRIO V4.6 - User’s Guide 151

152

Bypass Concept ETAS the ETK Flash. The part of the ECU service that writes the bypass outputs to the

ECU parses the address table and gets the corresponding values from the data table and writes the values to the ECU addresses.

The following figure describes the service-based bypass principle.

Fn*

Bypass

Fn

ECU

time

Fig. 7-4 Service-Based Bypass: Principle (The dashed line indicates that bypass data can be written back at a later time as well.)

INTECRIO V4.6 supports several versions of service-based bypass (SBB). Tab. 7-1

lists the supported SBB versions for each target (+: supported, –: not supported),

and Tab. 7-2 lists the AML versions available in the SBB versions.

ES1000 / ES1232 / ETK

ES 910.2 / supported ETKs

ES 910.3 / supported ETKs

SBB V2.0

+

+

+

SBB V2.1

–

+

+

SBB V3.*

–

–

+

INTECRIO does not support service-based bypass on an ETK with 8 Mbit/s.

Tab. 7-1 Supported SBB versions

SBB version

V2.0 + V3.0

V2.1

V3.1

supported AML versions

ETK AML 1.2.0 – 1.7.0

XETK AML

SBB AML

≥ 1.0.0

≥ 2.0.0

ETK AML

XETK AML

SBB AML

ETK AML not supported

≥ 2.0.0

≥ 3.1.1

not supported

XETK AML

SBB AML

≥ 2.0.0

≥ 3.1.0

Tab. 7-2 SBB versions and AML versions supported Distab types

Distab13 - Distab16

Distab17

Distab17

INTECRIO V4.6 - User’s Guide