INCA-FLEXRAY V6.2User Manual

2

Copyright

The data in this document may not be altered or amended without special noti-fication from ETAS GmbH. ETAS GmbH undertakes no further obligation in rela-tion to this document. The software described in it can only be used if thecustomer is in possession of a general license agreement or single license. Usingand copying is only allowed in concurrence with the specifications stipulated inthe contract.

Under no circumstances may any part of this document be copied, reproduced,transmitted, stored in a retrieval system or translated into another languagewithout the express written permission of ETAS GmbH.

© Copyright 2008 ETAS GmbH, Stuttgart

The names and designations used in this document are trademarks or brandsbelonging to the respective owners.

Document AM010103 R6.2.1 EN

Contents

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1.1 Safety Notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.2 General Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.3 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.4 Restrictions concerning INCA-FLEXRAY Support by Other Products . . . . . . . . 91.5 About this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2 New Features in INCA-FLEXRAY V6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.1 New Features in INCA-FLEXRAY V6.2.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.2 New Features in INCA-FLEXRAY V6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.3 New Features in INCA-FLEXRAY V6.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3 Installing INCA-FLEXRAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.1 Package Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.2 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.3 Installing INCA-FLEXRAY from CD-ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

4 Using the INCA-FLEXRAY Add-on in INCA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174.1 Setting up the Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174.2 Configuring the FlexRay Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

4.2.1 Configuring the FlexRay Hardware for FlexRay Monitoring. . . . . . . 194.2.2 Configuring the FlexRay Hardware for Measurement and Calibration

via XCP on FlexRay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224.3 Configuring the Experiment and starting FlexRay Monitoring . . . . . . . . . . . 24

5 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275.1 Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

5.1.1 Some FIBEX Data Types are not supported . . . . . . . . . . . . . . . . . . . 275.1.2 Data with FlexRay PreambleIndicatorBit Set is Discarded . . . . . . . . 275.1.3 FlexRay Network temporarily shuts down on Hardware Initialization27

Contents 3

4

5.1.4 FlexRay Bus Load leads to PC Overload . . . . . . . . . . . . . . . . . . . . . 275.1.5 Recursive Multiplexers are not Supported . . . . . . . . . . . . . . . . . . . 285.1.6 ASAM MCD-3 (new) / ASAP3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285.1.7 Flashing and Diagnosis over the XCP Interface are not Supported . 28

5.2 Tips and Tricks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295.2.1 Selecting the Correct Controller in the Hardware Configuration Editor

295.2.2 Selecting Variables by Frame, ECU or Signal Group . . . . . . . . . . . . 30

6 ETAS Contact Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Contents

1 Introduction

The FlexRay bus system is a standardized communication system which is becom-ing increasingly important for automotive engineering projects, because limita-tions of the amount of data on the CAN bus can be overcome, and redundanciesmake it possible to use FlexRay in safety-critical use cases. Moreover the deter-ministic design ensures a reliable transmission of messages.

INCA supports measurement and calibration of ECUs in vehicles that areequipped with a FlexRay bus by monitoring signals on the FlexRay channels intheir physical representation, as well as measurement and calibration via the XCPon FlexRay interface. The time stamps of the data samples are synchronized withall other data sources within INCA to enable causal analysis as well as error track-ing within the investigated system.

While performing the ECU calibration via ETK, CAN, or XCP on FlexRay, the usercan sample the signals on the FlexRay channels and store them together with allother data acquired by INCA in the measurement file for offline analysis. For theuser�s convenience, the integration of FlexRay monitoring keeps close to the wellknown and established CAN-Monitoring functionality in INCA.

The signals to be calibrated or monitored can be selected from all signals avail-able in the connected cluster; the FlexRay monitoring signals are defined in theFIBEX file, the measurement and calibration variables are defined in the projectdescribing files (*.a2l).

INCA imports the FIBEX file to get information on the FlexRay cluster. In addition,INCA uses the information from FIBEX to configure the interface hardware.

Introduction 5

6

1.1 Safety Notice

1.2 General Description

In typical FlexRay use cases, users often would like to carry out several tasks atthe same time:

� Measuring and calibrating ECUs with ETK / CAN / XCP on FlexRay

� Monitoring the in-vehicle FlexRay Bus with synchronized time stamps

� Measuring signals and analyzing them later

In these tasks, the user would like to

� work with physical signals (temperature, voltage, ...)

� use files for the network description which are compliant to the FIBEX standard

WARNING!

Improper use of STARTUP or SYNC controllers for the configuration of the INCA FlexRay hardware interface can result in unexpected effects or shutdown of the connected FlexRay network.Never use a STARTUP or SYNC controller for the configuration of the INCA FlexRay hardware interface on the road!

Selecting a controller with STARTUP or SYNC parameter for configu-ration causes the INCA FlexRay hardware interface to participate actively in the connected FlexRay network.Use controllers with STARTUP or SYNC parameter for configuration ONLY in FlexRay networks where the selected controller is NOT con-nected.

DANGER!

Calibration activities influence the behavior of the ECU and the sys-tems controlled by the ECU. This may result in unexpected behavior of the vehicle and thus can lead to safety critical situations.Only well trained personnel should be allowed to perform calibration activities.

Introduction

INCA-FLEXRAY can fulfil all these requirements.

Introduction 7

8

1.3 Definitions

FlexRay

FlexRay is a scalable and fault tolerant communication system for high-speed and deterministic data exchange. FlexRay�s time-division multiplex-ing facilitates the design of modular or safety-related distributed systems. Its high bandwidth of 10 MBaud on two channels helps to cope with the high network load caused by the increasing amount of innovative elec-tronic systems in modern vehicles.

The communication system�s specifications are released by the FlexRay consortium which is widely supported by vehicle manufacturers and sup-pliers worldwide.

FIBEX

FIBEX (Field Bus Exchange) is an exchange format based on XML schema which is used for complete descriptions of the in-vehicle communication network. FIBEX is defined for various network types (CAN, LIN, MOST, FlexRay) and contains information about the bus architecture, signals, node properties etc.

INCA uses FIBEX files to align tools and ECUs with the communication scheme given by the FlexRay cluster, i.e. the FIBEX file defines the signals which can be monitored via INCA in the connected cluster, and it contains data for the configuration of the interface hardware. The FIBEX file describes the whole FlexRay cluster; there is only one FIBEX file per cluster. If you are using the XCP on FlexRay interface, the definitions in the FIBEX file (description of the FlexRay cluster with the reserved frames for the XCP protocol) and the definitions in the A2L files of the ECUs that are part of the cluster (description of the available buffers for the XCP protocol of one ECU) must be consistent.

The FIBEX files have to be provided by the vehicle manufacturer.

The FIBEX file format is standardized by ASAM (Association for Standardisation of Automation- and Measuring Systems). INCA currently supports the following FIBEX baseline versions:

� FIBEX V1.1.5a

� FIBEX V1.2.0a

� FIBEX V2.0.0

� FIBEX V2.0.1

For further information please refer to the description of the FIBEX stan-dard at http://www.asam.net.

XCP

eXtended Calibration Protocol; XCP is a vendor- and interface-indepen-dent protocol for communication between calibration tools and control units. XCP was specified in the ASAM e.V.

ES520 FlexRay and CAN Interface Module

The ES520 vehicle bus interface module is the link between PC aided soft-ware like INCA and the data buses FlexRay and CAN. The connection to the PC is realized via the 100 MBit/s Ethernet interface of the ES520. Data

Introduction

traffic on CAN and FlexRay is managed simultaneously. The FlexRay trans-fer rate can be more than 20 times of CAN. The powerful microcontroller of the ES520 can process even these large data volumes loss-free.

Using the two FlexRay channels of the ES520 and the XCP on FlexRay interface requires the add-on INCA-FLEXRAY.

1.4 Restrictions concerning INCA-FLEXRAY Support by Other Products

� INCA-FLEXRAY support of IXXAT CCM hardware

INCA-FLEXRAY does not support the IXXAT CCM FlexRay hardware.

� INCA-FLEXRAY not supported by INCA-M

The add-on does not install on INCA-M.

If you need FlexRay functionality for your INCA-M installation please con-tact your ETAS office or the INCA product management.

� INCA-FLEXRAY not supported by ES71x Drive Recorder

The ES71x does not support the add-on INCA-FLEXRAY.

If you need FlexRay functionality for your ES71x please contact your ETAS office or the ES71x product management.

1.5 About this Manual

This manual addresses qualified personnel working in the fields of automobileECU development and calibration. Specialized knowledge in the areas of mea-surement and control unit technology is required. Moreover users need to beable to work with INCA and know the basic functionality.

The INCA-FLEXRAY manual consists of the following chapters:

� "Introduction" on page 5

This chapter contains some general information on the INCA-FLEXRAY add-on and the underlying concepts.

� "New Features in INCA-FLEXRAY V6" on page 11

This chapter contains a summary of the new features and changes.

You should read this section even if you are an experienced INCA-FLEXRAY user.

� "Installing INCA-FLEXRAY" on page 15

The installation chapter contains information on the scope of delivery, hardware and software requirements and describes the procedures used to install INCA-FLEXRAY.

� "Using the INCA-FLEXRAY Add-on in INCA" on page 17

This chapter addresses users who are new to INCA-FLEXRAY. Practice-ori-ented examples in tutorial style show you how to use INCA-FLEXRAY.

� "Appendix" on page 27

This chapter provides information on restrictions within INCA-FLEXRAY as well as tips and tricks for the user.

Introduction 9

10

Introduction

2 New Features in INCA-FLEXRAY V6

This section contains a summary of the new features that have been introducedin INCA-FLEXRAY V6. You should read this section even if you are already anexperienced INCA-FLEXRAY user. The latest changes are listed on top.

2.1 New Features in INCA-FLEXRAY V6.2.1

INCA-FLEXRAY V6.2.1 supports the measurement and calibration of FlexRayECUs via XCP on FlexRay. All functions required for memory page managementare available using this connection.

As interface hardware, you can use the ES520 FlexRay and CAN InterfaceModule, the ES512 FlexRay Network Module, or the ES920 FlexRay Module.

Note

Flash programming and diagnosis via the XCP on FlexRay interface is not sup-ported.

Note

The ES512 and ES920 modules will be released after INCA-FLEXRAY V6.2.1.

New Features in INCA-FLEXRAY V6 11

12

2.2 New Features in INCA-FLEXRAY V6.1

The following functional extensions and improvements are contained inINCA-FLEXRAY V6.1:

� Support of FIBEX V2.0.0 and V2.0.1

In addition to the FIBEX versions V1.1.5a and V1.2.0a, INCA-FLEXRAY V6.1also supports FIBEX V2.0.0 and V2.0.1. The handling in INCA is identical for all FIBEX versions.

� Writing imported FIBEX files back to the file system

It is now possible to write FIBEX files that you have imported into INCA back to the file system. For that purpose select the FIBEX file in the "Data-base Objects" listbox of the Database Manager and then select Write → FIBEX from the context menu.

� Support of compu methods TAB_NOINTP and FORMULA

When INCA is reading FIBEX files including the compu methods TAB_NOINTP and FORMULA, these are now fully supported.

New Features in INCA-FLEXRAY V6

2.3 New Features in INCA-FLEXRAY V6.0

The following functional extensions and improvements are contained inINCA-FLEXRAY V6.0:

� Keeping the same controller when another FIBEX project is assigned

When you assign another FIBEX file to an existing FlexRay interface in the Hardware Configuration Editor, the previously selected controller is kept, provided that it is also defined in the newly assigned FIBEX file.

� Displaying the FIBEX file name in the Hardware listbox of the Database Manager

In addition to the names of the FlexRay interface and the FlexRay channel, the Hardware listbox in the Database Manager also displays the name of the FIBEX description file which describes the cluster.

New Features in INCA-FLEXRAY V6 13

14

� FIBEX information on functions, groups and ECUs available in INCA

It is now possible to display information on functions, groups and ECUs that is contained in the FIBEX file. To see the information, select the corre-sponding item in the Sources list of the "Variable Selection" dialog and select About Variable Container from the context menu.

� Support of the FIBEX encoding SCALE-LINEAR

In the recent version INCA converted signal-encodings in FIBEX that are based on the SCALE-LINEAR definition to the CATEGORY "IDENTICAL". INCA-FLEXRAY V6.0 now fully supports the SCALE-LINEAR encoding.

New Features in INCA-FLEXRAY V6

3 Installing INCA-FLEXRAY

This chapter is for all users who install the INCA-FLEXRAY add-on on a PC. It alsocontains information on hardware and software requirements and the prepara-tion required for installation.

3.1 Package Contents

The INCA-FLEXRAY add-on consists of the following items which have to beordered separately:

� INCA-FLEXRAY software license

� CD ROM including

� Program files for the INCA-FLEXRAY add-on

� Manual in PDF format (Acrobat Reader)

� Product information in PDF format (Acrobat Reader)

� Demo Clip in avi format (Windows Media Player)

3.2 System Requirements

INCA-FLEXRAY V6.2 requires the following hardware and software:

� INCA-FLEXRAY hardware interface, e.g.

� ES520 FlexRay and CAN Interface Module includingES520 Driver (UCI)1 and the corresponding firmware version.

� INCA V6.2.1;Please refer to the INCA Getting Started manual for the INCA system requirements.

3.3 Installing INCA-FLEXRAY from CD-ROM

Please note that you must have administrator privileges to install theINCA-FLEXRAY add-on.

To install the INCA-FLEXRAY Add-on:

� Make sure that INCA is installed on your computer and that the release number of the INCA installa-tion is compatible with the release number of the INCA-FLEXRAY add-on.

� Close all active programs.

� Insert the CD with the installation program into the CD-ROM drive of your computer.

� If the installation CD does not start automatically, either execute the autostart.exe program on the CD to start the user interface of the CD or search for the Inca_AddOn-FLEXRAY.exe pro-gram on the CD and double-click it to start the installation routine manually.

1. UCI: Universal Communication Interface.The ES520 Driver (UCI) is a PC driver which is required as the interface between the ES520and INCA.

Installing INCA-FLEXRAY 15

16

� Follow the instructions in the installation routine to install the INCA-FLEXRAY add-on on your com-puter.

Before you can use the ES520 with INCA, you need to install the ES520 Driver(UCI).

To install the INCA-FLEXRAY Hardware Interface:

� Install the ES520 Driver (UCI). The ES520 Driver (UCI) is provided together with HSP (Hardware Ser-vice Package).

Installing INCA-FLEXRAY

4 Using the INCA-FLEXRAY Add-on in INCA

This chapter gives an example of how INCA-FLEXRAY can be used in INCA. Itdescribes a typical course of action for FlexRay monitoring as well as measure-ment and calibration via the XCP on FlexRay interface.

Before you can start monitoring the FlexRay bus via INCA, you have to prepareINCA for that task. Working with INCA-FLEXRAY comprises the following basictasks:

� Setting up the workspace in the Database Manager

� Configuring the FlexRay hardware in the Hardware Configuration Editor

� Configuring the experiment and starting monitoring and calibrating in the Experiment Environment

The course of action resembles the usual procedure for preparing and carryingout measurement and calibration tasks. For the description of the FlexRay cluster,however, FIBEX files are used. These are handled in the same way as CANdb files.

The following sections describe the basic procedures applied when working withFlexRay from within INCA. In some cases there is more than one way of perform-ing a task, e.g. FIBEX files can be added either in the Database Manager or in theHardware Configuration Editor. The following description provides an exampleof one typical course of action.

4.1 Setting up the Workspace

In the first step of preparing FlexRay monitoring, you create a new database andworkspace and add a FIBEX file to the database.

The FIBEX file has to be provided by the vehicle manufacturer. It contains adescription of the configuration of the measurement hardware as well as of thesignals which are available through the FlexRay bus.

To set up the Workspace:

� Create a new database:

� Select Database → New.

� In the New Database dialog, enter FlexRay_Demo.

� Click OK.

� Create a top folder in the database:

� Select Edit → Add → Add top folder.

� Rename the new folder Demo and press <ENTER>.

� Create a new workspace:

� Select the top folder you want to create the workspace in. Here, select the Demo folder.

� Select Edit → Add → Workspace.

� Rename the new workspace FlexRay and press <ENTER>.

� Add a FIBEX file to the database:

� Select the top folder, Demo.

Using the INCA-FLEXRAY Add-on in INCA 17

18

� Select Edit → Add → FIBEX.

� A dialog pops up where you can select the desired FIBEX file. Select the FIBEX file and click Open.

� Add the ECU project files to the database that are describing the ECUs used in your FlexRay cluster:

� Select the top folder, Demo.

� Select Edit → Add → ECU-Project (A2L).

� A dialog pops up where you can select the desired ECU project. Select the A2L file and click Open.

� A dialog pops up where you can select the desired dataset for the project. Select the dataset file (hex file) and click Open.

� In the same way, add an ECU project and dataset for any other ECU that is part of the FlexRay cluster.

Fig. 4-1 Workspace, FIBEX description, and projects in the Database Manager

4.2 Configuring the FlexRay Hardware

After having set up the workspace, you must add the hardware to your configu-ration.

In the case of FlexRay monitoring or measurement and calibration via the XCP onFlexRay interface, you assign a FIBEX file to the hardware used. The FIBEX filecontains hardware and signal related information such as formulas for automaticconversion to physical signal values, therefore making complex parameter entriesobsolete. One FIBEX file describes the complete cluster.

Using the INCA-FLEXRAY Add-on in INCA

For the XCP devices, you assign an ECU project file to the hardware used. TheECU project file describes the available buffers for the XCP protocol for an ECU.There must be one ECU project file for each ECU.

The following sections describe the hardware configuration separately forFlexRay Monitoring and for measurement and calibration via XCP on FlexRay.

4.2.1 Configuring the FlexRay Hardware for FlexRay Monitoring

To add the FlexRay Hardware for FlexRay Monitoring:

� In the Database Manager, select the FlexRay work-space. Then click the Configure Hardware icon above the Hardware listbox to start the Hardware Configuration Editor.

� In the Hardware Configuration Editor, add the FlexRay hardware for FlexRay Monitoring and assign the FIBEX description:

� Select Device → Insert.

� The Add hardware device dialog appears, showing a list of interfaces with available devices.

� Expand the ES520 folder by clicking on the + sign in front of it, then expand the FLX folder. Select the entry FLX Monitoring A.

� Click OK.

� A dialog appears, where you can select the FIBEX file with the description of the FlexRay communication. Select the FIBEX file.

� Click OK.

Fig. 4-2 FlexRay hardware in the Hardware Configuration Editor

Note

Make sure that the description in FIBEX and the description in the ECU project files are consistent. Otherwise the hardware cannot be successfully initialized.

Using the INCA-FLEXRAY Add-on in INCA 19

20

In the following section you first get some more background information aboutconfiguring the FlexRay controller before continuing with the step by stepinstruction on page 21.

One FlexRay bus consists of two physical channels: channel A and channel B. OneFlexRay controller on a node handles both channels A and B. The channels arenot independent. All nodes connected to one net represent one 'cluster'.

INCA receives all frames on both FlexRay channels of all interfaces connected toINCA. It can monitor 1 to 4 FlexRay clusters in parallel (i.e. 1 to 8 FlexRay chan-nels).

In the next step, after having selected the FLX:1 node in the Hardware deviceslist, you can select a controller for the configuration of the INCA Flexray hard-ware interface. The Controller drop down list contains all controllers that aredefined in the FIBEX description file1.

The FlexRay specification requires that for safety reasons, a FlexRay cluster musthave at least three STARTUP nodes. The FlexRay cluster still works with twoSTARTUP nodes. The ES520 monitoring device also works in clusters where onlyone STARTUP node is present, because it is able to represent the secondSTARTUP node itself. To use this feature, you have to select a controller from thelist that contains the string STARTUP.

The number behind the string STARTUP describes the slot ID (KEY_SLOT_ID) indecimal representation that is used for sending the startup information. Byselecting such a node, you determine that INCA represents the second STARTUPnode, which enables INCA to monitor communication on a FlexRay network inenvironments with only one physical STARTUP node.

1. FlexRay knows three different types of controllers:

� STARTUP nodes: controllers that are used for startup of the FlexRay network. STARTUP nodes are listed in FIBEX and therefore also in INCA with the appendix "STARTUP nn", where nn represents the slot ID used for sending the startup infor-mation.

Example for notation in FIBEX:<flexray:STARTUP-SYNC>60</flexray:STARTUP-SYNC>

� SYNC nodes: controllers that are used for time synchronization of the nodes in the network. SYNC nodes are listed in FIBEX and therefore also in INCA with the appendix "SYNC nn", where nn represents the slot ID used for sending the sync information. STARTUP nodes are always also SYNC nodes and can be used as such.

Example for notation in FIBEX:<flexray:SYNC>89</flexray:SYNC>

� Integration nodes: all other controllers, which can be used to configure FlexRay monitoring. The names of integration nodes are not specifically indexed.

Example for notation in FIBEX:<flexray:NONE/>

Using the INCA-FLEXRAY Add-on in INCA

The following figure shows an example of an INCA hardware configuration witha STARTUP node selected.

Fig. 4-3 FlexRay hardware in the Hardware Configuration Editor

Please note that usage of SYNC or STARTUP nodes in the hardware configura-tion are meant only for such cases where the selected controller is physically NOTconnected, i.e. a virtual controller has to be selected to simulate its behavior andensure startup of the FlexRay cluster. Selecting a controller with a STARTUP orSYNC parameter for configuration causes the FlexRay interface to participateactively in the connected FlexRay network. The FlexRay interface will send perma-nently Null frames in the slot represented by the KEY_SLOT_ID; it is thereforenever to be used if INCA is connected via the INCA FlexRay hardware interfaceand a FlexRay network to a vehicle on the road (see also "Selecting the CorrectController in the Hardware Configuration Editor" on page 29).

After having got this background information, you can now go on with selectinga controller and initializing the hardware:

To configure and initialize the FlexRay hardware:

� In the Hardware devices list, select the FLX:1 node.

� In the FLXParameters list, click in the field on the right of the FlexRay Cluster field. Click it once again to open the list of available clusters. Select the desired cluster.Please note that if the FIBEX file defines only one cluster, the list contains only one entry.

WARNING!

Improper use of STARTUP or SYNC controllers for the configuration of the interface between INCA and FlexRay can result in unexpected effects or shutdown of the connected FlexRay network.Never use a STARTUP or SYNC controller for the configuration of the INCA FlexRay hardware interface on the road!

Using the INCA-FLEXRAY Add-on in INCA 21

22

� In the FLXParameters list, click in the field on the right of the FlexRay Node field. Click it once again to open the list of available controllers. Select the controller you would like to use to configure the INCA FlexRay hardware interface.

� If you have selected a STARTUP controller, a warn-ing gets displayed. Read the warning carefully and close the dialog with OK or Cancel.

If you are using INCA on the road with the real vehi-cle, you need to select another controller of the type "Integration node" instead of the STARTUP controller.

� Select Hardware → Initialize hardware.

� The Connect Devices dialog box opens where you can map physically connected devices to devices created in the Hardware Configuration Editor. Assign the devices and click OK.

Fig. 4-4 FlexRay hardware after configuration and initialization

4.2.2 Configuring the FlexRay Hardware for Measurement and Calibration via XCP on FlexRay

You can now add XCP devices to the FlexRay cluster.

As you have already assigned the FIBEX description to the FLX:1 node in theHardware devices list of the Hardware Configuration Editor, the description ofthe FlexRay cluster is already available, and you can skip this step in the configu-ration of the XCP on FlexRay interface. If, however, you start the hardware con-figuration with adding XCP devices to your Flexray cluster, you must also assigna FIBEX file to the FLX node and configure the controller as described in "Config-uring the FlexRay Hardware for FlexRay Monitoring" on page 19.

Using the INCA-FLEXRAY Add-on in INCA

To add the XCP devices to the FlexRay cluster:

� In the Hardware Configuration Editor, add the hardware for measurement and calibration via XCP on FlexRay and assign the ECU project descriptions:

� In the Hardware devices list, select the FlexRay controller FLX:1.

� Select Device → Insert.

� The Add hardware device dialog appears. The FLX folder of the ES520 is already expanded. Select the entry XCP.

� Click OK.

� A dialog appears, where you can select the ECU project (A2L file) describing the ECU. Select the A2L file in the Projects list box, then select the dataset in the Datasets list box.

� Click OK.

� In the same way, add an XCP device for any other ECU that is part of the FlexRay cluster.

Fig. 4-5 FlexRay hardware in the Hardware Configuration Editor

Note

INCA supports up to 16 XCP on FlexRay devices.

Using the INCA-FLEXRAY Add-on in INCA 23

24

To initialize the FlexRay hardware:

� Select Hardware → Initialize hardware.

� The Connect Devices dialog box opens where you can map physically connected devices to devices created in the Hardware Configuration Editor. Assign the devices and click OK.

Fig. 4-6 FlexRay hardware after configuration and initialization

You have now finished hardware configuration and can close the HardwareConfiguration Editor. The FlexRay interface will join the FlexRay communicationas soon as the other participants in the cluster are present.

4.3 Configuring the Experiment and starting FlexRay Monitoring

In the Experiment Environment you can select all signals for monitoring whichare defined in the FlexRay part of the FIBEX file.

To configure the Experiment:

� In the Database Manager, select the FlexRay work-space. Then click the Start Experiment icon above the Experiment listbox to open an experiment in the Experiment Environment.

� Select and configure the variables you would like to add to the experiment:

� In the Experiment window, select Variables → Select.

The Variable Selection dialog opens.

� In the list Sources, select the device FLX Monitoring A:1.

Using the INCA-FLEXRAY Add-on in INCA

The variables list now shows all variables in alphabetical order that belong to thisdevice. It might happen that you do not see the variables that you expect or thatthere are no variables displayed at all; in this case please verify that there is nofilter being used. If required, you can deactivate all filters by clicking on the Clearall filters icon in the toolbar.

If you are interested only in variables for individual functions, you can expand thetree in the Sources list by clicking on the + sign left of the device and select onlythe desired functions. The variables list only displays the variables of the selectedfunctions. Depending on the definition in the FIBEX file, signals might also begrouped by frame, ECU or signal groups (see "Selecting Variables by Frame, ECUor Signal Group" on page 30). Summarizing these explanations, you can selectvariables in one of the following ways:

� You click on the FlexRay device and select the desired signals from a com-plete list of signals for that device.

� You expand the tree structure of the FlexRay device by clicking on the + sign in front of it, click on a function and select the desired variables from a list of signals associated with that function.For both devices and functions, the same icon representing a devices hierarchy is used in the tree view of the Sources list.

� You expand the tree structure of the FlexRay device by clicking on the + sign in front of it, further expand one of the groups for frames, ECUs or signal groups and click on the desired items. Afterwards you can select the desired variables from a subset containing signals associated with the selected frames, ECUs or signal groups. Groups are represented by a blue book icon in the tree view of the Sources list.

� In the variables list, select all variables you would like to monitor.

Please note that further information is displayed in the information pane of the dialog as soon as you select a variable.

� In the list Sources, select one of the XCP device that you have added to your workspace.

� In the variables list, select all variables you would like to measure or calibrate.

� Click OK to add the selected variables to the Exper-iment window.

� Select Experiment → Save.

The Save as dialog appears. In the list Database Objects select the Demo folder to add the experi-ment to the folder. Then enter the name Monitoring_Exp in the list Item name and click OK.

To start Monitoring / Measuring:

� Click <F11> to start visualization without recording

or

� Click <F12> to start recording.

Using the INCA-FLEXRAY Add-on in INCA 25

26

To start Calibrating:

� Make sure that the Working Page is activated.

� Perform your calibration tasks as usual.

For detailed information on how to perform calibration tasks please see the INCAtutorial.

Using the INCA-FLEXRAY Add-on in INCA

5 Appendix

This chapter gives some information on technical restrictions and provides helpfor trouble-shooting as well as tips and tricks for selected tasks.

5.1 Restrictions

This product has been manufactured with the utmost care for quality, usabilityand completeness in terms of users� expectations.

Nevertheless there are constraints that need to be considered when using thisproduct.

5.1.1 Some FIBEX Data Types are not supported

INCA supports all signal data types usually used. This includes data types of up to32 bit and float 64 data types.

Some minor data types are not supported in INCA and therefore removed fromthe imported FIBEX file:

� Signals with data types longer than 32 bit (A_UINT64, A_INT64)

� Signals with the data type A_UNICODE2STRING

� Signals with the data type A_BYTEFIELD

� Signals with the data type A_BITFIELD

� Signals with the data type OTHER

The .log files for the FIBEX import report any removal of data types from theFIBEX file.

5.1.2 Data with FlexRay PreambleIndicatorBit Set is Discarded

The FlexRay specification defines a preamble indicator bit for NetworkManage-ment and special filtering applications.

INCA-FLEXRAY discards the data of FlexRay frames where the preamble indicatorbit is set:

� The NetworkManagement information is neither captured nor used.

� Message filtering in the dynamic segment is not applied.

� The log file A1b_FlexRayMon.log logs events where data was discarded.

5.1.3 FlexRay Network temporarily shuts down on Hardware Initialization

The add-On INCA-FLEXRAY is able to represent one STARTUP node in a FlexRaynetwork.

In cases where only two STARTUP nodes are present in the connected cluster are-initialization of the measurement hardware necessarily results in a temporaryshutdown of the FlexRay network.

A re-initialization of the hardware can be initiated manually by the user or auto-matically by INCA, e.g. on recovering from measurement errors.

5.1.4 FlexRay Bus Load leads to PC Overload

FlexRay delivers a high amount of data to measurement systems.

Multiple FlexRay channels with high bus load may lead to an overload situationfor the PC.

Appendix 27

28

Overload situations can be expected in constellations exceeding this setup:

� 3 GHz PC in idle mode (no further task or measurement) +2 FlexRay channels with more than 90% bus load

5.1.5 Recursive Multiplexers are not Supported

FIBEX V2.0.1 allows the definition of recursive multiplexers. INCA does not yetsupport this functionality.

If you need the support of recursive multiplexers in INCA, please contact yourETAS office or the INCA product management.

5.1.6 ASAM MCD-3 (new)1 / ASAP3

When using the remote control functionality (ASAM-MCD3 MCD or ASAP3) youneed to select "FRAME AVAILABLE" from the available rasters to monitorFlexRay signals.

5.1.7 Flashing and Diagnosis over the XCP Interface are not Supported

The XCP on FlexRay interface only supports measurement and calibration usecases; flash programming and diagnosis are not supported. If you need to flashcode and/or data to the ECU, you can use other flash ports according to yoursystem configuration.

1. ASAM MCD 3 V2.00.02 (object-oriented model), dating from 04.04.2005

Appendix

5.2 Tips and Tricks

This section provides some help information for tasks which might be difficult tounderstand or can be optimized by means of little tips and tricks.

5.2.1 Selecting the Correct Controller in the Hardware Configuration Editor

FlexRay networks can contain integration nodes, SYNC nodes and STARTUPnodes (which are at the same time also SYNC nodes). These different node typesare designed for different purposes.

In theory, monitoring a FlexRay network can be accomplished with any of thethree node types. Starting up a FlexRay network, however, always requires atleast two STARTUP nodes in the network.

Every node contains a controller. The controller level is used for the configurationof the INCA FlexRay hardware interface via the INCA Hardware ConfigurationEditor.

In a vehicle on the road, all important nodes are already present. Therefore, youcan select in the Hardware Configuration Editor an integration controller for con-figuration, because another STARTUP node is not required. On the contrary, is iscrucial that you do NOT select a controller that is physically existing in the net-work! Selecting a physically existing controller in the INCA Hardware Configura-tion Editor would lead to protocol conflicts and therefore possibly to dangeroussituations! Still, if you selected a STARTUP or SYNC controller that does not phys-ically exist in the network, the network would be shut down at hardware initial-ization, at reset by INCA or at a PC crash!

The situation is less critical when you are using INCA-FLEXRAY for accessing aFlexRay network that is not used in a "real" vehicle on the road, but, forinstance, on a testbench. If there is only one ECU connected, you might need toenable system startup by selecting a FlexRay STARTUP controller in the HardwareConfiguration Editor. The number behind the string STARTUP describes the slotID (KEY_SLOT_ID) in decimal representation that is used for sending the startupinformation. By selecting such a controller, you determine that INCA representsthe second STARTUP node, which enables INCA to monitor communication on aFlexRay network in environments with only one physical STARTUP node.

Please note that usage of SYNC or STARTUP controllers in the hardware config-uration are meant only for such cases where the selected controller is physicallyNOT connected, i.e. a virtual controller has to be selected to simulate its behaviorand ensure startup.

Summarizing these pieces of information, only select controllers according to thefollowing rules:

Note

It is strongly recommended that you have at least one integration controller included in your FIBEX file that is explicitely meant to be used as a configuration basis, but not present in the FlexRay network by default.

Appendix 29

30

Monitoring a FlexRay Network on the Road

If INCA is connected via the INCA FlexRay hardware interface and a FlexRay net-work to a vehicle on the road:

� Make sure that for FlexRay Monitoring, you select an integration control-ler in the Hardware Configuration Editor.

Monitoring a FlexRay Network on a Testbench

If you use INCA and the INCA FlexRay hardware interface for accessing a FlexRaynetwork on a testbench, you have the following options for selecting a controllerin the Hardware Configuration Editor:

� You can select an integration controller for configuration (recommended).

� You can also select a controller with a STARTUP or SYNC parameter for configuration to enable system startup. Please only select controllers that are NOT physically connected because otherwise the network will not work properly due to protocol conflicts.

5.2.2 Selecting Variables by Frame, ECU or Signal Group

When you determine which variables are to be used in the INCA ExperimentEnvironment for measurement and calibration tasks, you usually first select adevice or a function of that device and then select the desired variables from aplain list in the "Variable Selection" dialog.

In case of CAN Monitoring devices, the variables are also grouped by CANframes so that you can either select the variables from a list of all variables orfrom a sub-list of variables belonging only to the selected CAN frame.

According to the same principle, the variables of a FlexRay device can be groupedby one of the following categories:

� Grouping by frames:When you select a frame in the Sources list, the variables list shows all signals located in the selected frame.

� Grouping by ECUs:When you select an ECU in the Sources list, the variables list shows all TX-signals of the selected ECU (i.e. signals that are sent by the ECU).

WARNING!

DO NOT select a controller with a STARTUP or SYNC parameter for configuration in any case!

Selecting a controller with a STARTUP or SYNC parameter for config-uration causes the FlexRay interface to participate actively in the con-nected FlexRay network and is therefore never to be used if INCA is connected via the INCA FlexRay hardware interface and a FlexRay network to a vehicle on the road!

Note

Depending on the description in the FIBEX file, the same signal can occur in different frames

Appendix

� Grouping by signal groups1:When you select a signal group in the Sources list, the variables list shows all signals that are part of the selected signal group.

In the "Variable Selection" dialog, each group is depicted by an icon represent-ing a blue book (see screenshot below):

1. In this context the term "signal group" refers to the signal groups as specified in the FIBEXfile in the <requirements> section. FIBEX specifies that all signals of a signal group mustbe located in one frame.

Note

Only those groupings are available in the "Variable Selection" dialog that are defined in the FIBEX file provided by the vehicle manufacturer. If the FIBEX file does not contain any of these groups, the FlexRay device does not contain any branches for groups in the Sources tree structure, and the variables belonging to the FlexRay device can only be selected from a plain list.

Appendix 31

32

Appendix

6 ETAS Contact Addresses

ETAS HQ

ETAS GmbH

ETAS Subsidiaries and Technical Support

For details of your local sales office as well as your local technical support teamand product hotlines, take a look at the ETAS website:

Borsigstraße 14 Phone: +49 711 89661-0

70469 Stuttgart Fax: +49 711 89661-106

Germany WWW: www.etas.com

ETAS subsidiaries WWW: www.etas.com/en/contact.php

ETAS technical support WWW: www.etas.com/en/hotlines.php

ETAS Contact Addresses 33

34

ETAS Contact Addresses