Summary. ETAS INTECRIO

ETAS Bypass Concept

B In the OSC, move the F3’ software process to the INTECRIO software task assigned to the read action of SP 1.

C Remove empty tasks from the OS Configuration (optional).

8.6.4

Fig. 8-15 OS configuration (incomplete) for a bypass with read and write actions of a service point in different tasks

For SBB V3 and higher, the results of OS mapping and trigger assignment in the build process are reported in an XML log file. The file is stored in the workspace log directory, it is named <system name> _ETKSBBV3_TriggerInfo.xml

.

This file lists, for each service-point action used in the system project, the name

( TASKNAME ) and priority ( TASKPRIO ) of the task where the signal group is executed, as well as number ( TRGNUMBER ) and priority ( RASTERPRIO ) of the ETK trigger with which the signal group data will be transferred.

Example:

<TriggerInfo

SIGNALGROUPNAME=

"ETK_Bypass.MySP_1.MySP_1_before_receive_from_ECU"

RASTERPRIO ="8"

TASKNAME ="M_ETK_Bypass_MySP_1_before_re"

TASKPRIO ="195"

TRGNUMBER ="28"

TRGFLAGADDR="a303efb8"

RAID="1"/>

This information is useful if the bypass system must be debugged.

Summary

The implementation and integration of the ECU drivers must take care of the following:

• As the service-based bypass only overwrites ECU values with bypass values without preventing the ECU from writing these values, there is a possibility of data inconsistency which can lead to unpredicted behavior of the ECU.

• INTECRIO provides a configuration variable to set the maximal number of tolerated lost cycles, e.g. how many ECU calculation cycles without receiving bypass values are tolerated before this is regarded as an error.

But it is up to the provider of the ECU software to make sure missing bypass output values are detected.

INTECRIO V4.7 - User’s Guide 158

ETAS Bypass Concept

• INTECRIO provides a configuration variable to set a specific error behavior (if also supported by the ECU implementation). But it is up to the provider of the ECU software to make sure bypass failures or bypass deactivation can be detected by the ECU software! The configuration setting in the INTECRIO GUI can then be used to choose between different provided error behaviors in the ECU.

• INTECRIO allows disabling the bypassed ECU process. In this case, no

ECU values can be used as fallback values for bypass failures! It is up to the provider of the ECU software to make sure sensible data is written to the variables if both the ECU process and the bypass is disabled.

INTECRIO V4.7 - User’s Guide 159