1 About this Support Note

Size: px

Start display at page:

Download "1 About this Support Note"

Elisabeth Long
5 years ago
Views:

1 Author(s) Restrictions Morizur, Pascale Table of contents 1 About this Support Note Overview Ready to use Pool Examples with simulation Usage of the detail view of the trace window Ethernet Network Setting For the CANoe Tester For the Gateway Diagnostics Configuration Diagnostics/ISO TP Configuration Other possible Settings for the Tester Glossary Contacts About this Support Note In the table below you will find the icon conventions used throughout the Support Note. Symbol Utilization This icon gives you step-by-step instructions. This icon indicates notes and tips that facilitate your work. 2 Overview This Support Note describes step by step how to use CANoe to simulate > a DoIP Tester (Tester) and > an ECU (ECUbehindGateway) that is connected on a CAN network after a real DoIP/CAN Gateway (DUT_GW) The resulting configuration will make it possible to test the diagnostic software implemented in the DUT_GW. All network related settings are already explained and illustrated step by step in the Support Note (Usage of CANoe.Ethernet as Diagnostics Tester to Address one ECU) of this Vector KnowledgeBase article [1]. The present document focuses on the gateway related settings of CANoe s Diagnostics/ISO TP configuration dialog. The expected communication flows are documented as trace screenshots over the document. KB_1108_SN-IND-1-041_Usage_of_CANoe.Ethernet_as_Tester_for_Real_Diagnostic_Gateway Page 1

2 2.1 Ready to use Pool Examples with simulation To facilitate the setting of CANoe as a Tester, we recommend to first setup a simulated Gateway (GW). Once the communication between Tester & ECUbehindGateway is working based on the GW as expected (i.e. the CANoe trace contains the desired DoIP frames), then the GW can be replaced by the DUT_GW. A ready to use simulation is to find as a Pool Example Configuration (CANoe 8.5) of this Vector KnowledgeBase article [2]. It contains: > the necessary CAPL codes for simulation of the GW and the ECUbehindGateway > two example dbc as network description for the GW > a demo CDD that can be used both for the GW and the ECUbehindGateway 2.2 Usage of the detail view of the trace window CANoe offers a very convenient detail view that lets you analyze the content of the frames out of the trace windows, level for level. 3 Ethernet Network Setting 3.1 For the CANoe Tester See [1] 3.2 For the Gateway See [1] If the DUT_GW diagnostic services shall also be tested, then proceed for the GW node to the same settings than the one for the simulated ECU in [1] and adapt them to the gateway specification (i.e. IP Address.). KB_1108_SN-IND-1-041_Usage_of_CANoe.Ethernet_as_Tester_for_Real_Diagnostic_Gateway Page 2

4 Diagnostics Configuration Depending on the Network Design the CANoe Tester might address an ECU in the following different manners: > directly, using a fix ECU IP Address (this will omit the

3 4 Diagnostics Configuration Depending on the Network Design the CANoe Tester might address an ECU in the following different manners: > directly, using a fix ECU IP Address (this will omit the vehicle identification sequence) > after having sent a Vehicle Identification Request if no ECU IP address is known See [1] for the corresponding settings. 4.1 Diagnostics/ISO TP Configuration Step 1: On CAN Networks: > add a CDD for the ECUbehindGateway > enable Diagnostics via DoIP gateway / Access via Ethernet. The Gateway to CAN entry appears in the Diagnostic Access view, on the left side of the Diagnostics/ISO TP Configuration. KB_1108_SN-IND-1-041_Usage_of_CANoe.Ethernet_as_Tester_for_Real_Diagnostic_Gateway Page 3

> control the setting in the Overview and make sure the Default Adapter of the TCP/IP Stack configuration is selected.

4 Step 2: On Ethernet Networks: > add the CDD for the GW (assumed that you want to use diagnostic services provided by the GW as well) > adapt the logical address of both ECUbehindGateway and GW. Please note that they should be distinct. > control the setting in the Overview and make sure the Default Adapter of the TCP/IP Stack configuration is selected. It corresponds to CANoe s one. Figure 2.1 Figure 2.2 KB_1108_SN-IND-1-041_Usage_of_CANoe.Ethernet_as_Tester_for_Real_Diagnostic_Gateway Page 4

5 Figure 2.3 Figure 2.4 KB_1108_SN-IND-1-041_Usage_of_CANoe.Ethernet_as_Tester_for_Real_Diagnostic_Gateway Page 5

6 Figure 2.5 The Vehicle Simulation Parameter for both GW and Gateway to CAN shall be identical as they concern the same Gateway. Adapt them to your use case in the configuration dialogs (see above, Figure 2.2 and 2.5) and in the Gateway CAPL code (see below). Figure 2.6 KB_1108_SN-IND-1-041_Usage_of_CANoe.Ethernet_as_Tester_for_Real_Diagnostic_Gateway Page 6

7 Step 3: > choose the DoIP protocol version. KB_1108_SN-IND-1-041_Usage_of_CANoe.Ethernet_as_Tester_for_Real_Diagnostic_Gateway Page 7

Step 4: > set the P6a timing for the Tester direct access to GW

Step 5: > add to the Ethernet and CAN networks in Simulation

DoIp.dll (for Ethernet) and OSEK_TP.dll (for CAN).

8 Step 4: > set the P6a timing for the Tester direct access to GW and the P6b timing for its access to ECUbehindGateway over the GW. Step 5: > add to the Ethernet and CAN networks in Simulation Setup each a dbc defining the GW as a node layer module using DoIp.dll (for Ethernet) and OSEK_TP.dll (for CAN). KB_1108_SN-IND-1-041_Usage_of_CANoe.Ethernet_as_Tester_for_Real_Diagnostic_Gateway Page 8

$The two dbc are part of [2] but can also be found in CANoe Sample Configuration: C:\Users\Public\Documents\Vector\<your CANoe version i.e.9.0.$

9 The two dbc are part of [2] but can also be found in CANoe Sample Configuration: C:\Users\Public\Documents\Vector\<your CANoe version i.e (x64)>\canoe Sample Configurations\Ethernet\MoreExamples\DoIP_HSFZ\Candb Adapt the CAN dbc to contain an ECU and a GW. The Ethernet dbc must be adapted to contain a GW. KB_1108_SN-IND-1-041_Usage_of_CANoe.Ethernet_as_Tester_for_Real_Diagnostic_Gateway Page 9

10 KB_1108_SN-IND-1-041_Usage_of_CANoe.Ethernet_as_Tester_for_Real_Diagnostic_Gateway Page 10

called GW on both CAN and Ethernet networks.

11 Step 6: > add in the Simulation Setup a CAPL node called ECUbehindGateway on the CAN network and a second CAPL node called GW on both CAN and Ethernet networks. KB_1108_SN-IND-1-041_Usage_of_CANoe.Ethernet_as_Tester_for_Real_Diagnostic_Gateway Page 11

12 Step 7: > set the correct network node out of the dbc for both the ECUbehindGateway and GW. KB_1108_SN-IND-1-041_Usage_of_CANoe.Ethernet_as_Tester_for_Real_Diagnostic_Gateway Page 12

Do not forget to copy the two GWdiag.cin & DownloadSim.

13 Step 8: > add the UDSsim CAPL out of [2] as Node Specification for the ECUbehindGateway simulation and the GWsim CAPL as Node Specification for the GW simulation. Do not forget to copy the two GWdiag.cin & DownloadSim.cin include files to the directory where the CAPL simulations are saved. KB_1108_SN-IND-1-041_Usage_of_CANoe.Ethernet_as_Tester_for_Real_Diagnostic_Gateway Page 13

Network and OSEK_TP is only active on CAN. This assignment is only possible if you have previously added the two dbc to the GW as indicated in step 5.

14 Step 9: > check that both DoIP and OSEK_TP DLLs are active components in the node configuration. This should have been automatically done after both dbc have been added to the simulation Setup (see step 7) Take care that DoIP is only active on Ethernet Network and OSEK_TP is only active on CAN. This assignment is only possible if you have previously added the two dbc to the GW as indicated in step 5. If the Components configuration does not correspond to the above picture, then control the Node Layer attributes of the added dbc. KB_1108_SN-IND-1-041_Usage_of_CANoe.Ethernet_as_Tester_for_Real_Diagnostic_Gateway Page 14

Step 10: From CANoe 10 on: > configure the CDD of the ECUbehindGateway to be used for the node simulation like indicated in Figure 10.1. In this case the built-in diagnostic channel will be used.

15 Step 10: From CANoe 10 on: > configure the CDD of the ECUbehindGateway to be used for the node simulation like indicated in Figure In this case the built-in diagnostic channel will be used. > if you do not need sophisticated simulation functionality, this will do. > in case you need to manipulate the diagnostics response, please use the CCI. For more information, consult CANoe Online Help. For CANoe version up to 10 (Figure 10.2): > no built-in diagnostic channel is available. The CCI must be used. Figure 10.1 KB_1108_SN-IND-1-041_Usage_of_CANoe.Ethernet_as_Tester_for_Real_Diagnostic_Gateway Page 15

16 Figure 10.2 The Pool Example Configuration [2] has been developed to be used for CANoe from the version 8.5 on. Therefore, no usage of the built-in diagnostic channel has been made. KB_1108_SN-IND-1-041_Usage_of_CANoe.Ethernet_as_Tester_for_Real_Diagnostic_Gateway Page 16

17 Step 11: > Use the GW Diagnostic Console to send a Diagnostic Request to the GW and observe the Ethernet Trace. > Pease refer to [1] for a complete interpretation of the trace below that corresponds to the DoIP/HSFZ Settings of Diagnostics/ISO TP configuration Dialog of [1], chapter Mind the Trace Filters and Toggle display mode settings that shall correspond to the indicated one. Note that the GW always sends to the Tester a Diagnostic message positive acknowledge after each received diagnostic request. KB_1108_SN-IND-1-041_Usage_of_CANoe.Ethernet_as_Tester_for_Real_Diagnostic_Gateway Page 17

Step 13: > Deactivate the GW in the Simulation Setup and connect the

18 Step 12: > Send a Diagnostic Request to the ECUbehindGateway and observe in the trace the Ethernet and CAN messages. Step 13: > Deactivate the GW in the Simulation Setup and connect the DUT_GW. KB_1108_SN-IND-1-041_Usage_of_CANoe.Ethernet_as_Tester_for_Real_Diagnostic_Gateway Page 18

If you want to ameliorate your configuration with a more sophisticated ECUbehindGateway that responds to a specific Diagnostic Request (i.e. EngineStatus_Read) with a given response (i.e. Engine Speed = 500), then use the following CAPL code.

$EngineStatus_Read { } diagresponse this resp; diagsetparameter (resp, "Engine_Speed",504); diagsendresponse (resp); Consult this Vector KnowledgeBase article to get a Pool Example$

19 If you want to ameliorate your configuration with a more sophisticated ECUbehindGateway that responds to a specific Diagnostic Request (i.e. EngineStatus_Read) with a given response (i.e. Engine Speed = 500), then use the following CAPL code. Note that this code is only adapted for CANoe from 10 on as it does not contain the usage of CCI. See also chap. 3.2 of [1] concerning the built-in diagnostic channel. on diagrequest Door.EngineStatus_Read { } diagresponse this resp; diagsetparameter (resp, "Engine_Speed",504); diagsendresponse (resp); Consult this Vector KnowledgeBase article to get a Pool Example Configuration [3] containing a test module. KB_1108_SN-IND-1-041_Usage_of_CANoe.Ethernet_as_Tester_for_Real_Diagnostic_Gateway Page 19

20 5 Other possible Settings for the Tester See [1]. 6 Glossary [1] Support Note (Usage of CANoe.Ethernet as Diagnostics Tester to Address one ECU) of Vector KnowledgeBase article (How to Use CANoe as DoIP Tester to Address my ECU) [2] Example of Vector KnowledgeBase article (How to use CANoe.Ethernet as a Tester for a Real Diagnostic Gateway) [3] Example of Vector KnowledgeBase article (How to Use CANoe as DoIP Tester to Address my ECU) 7 Contacts Please find the contacts of Vector Informatik GmbH and all subsidiaries worldwide via: KB_1108_SN-IND-1-041_Usage_of_CANoe.Ethernet_as_Tester_for_Real_Diagnostic_Gateway Page 20

In the table below you will find the icon conventions used throughout the Support Note. This icon indicates notes and tips that facilitate your work.

In the table below you will find the icon conventions used throughout the Support Note. This icon indicates notes and tips that facilitate your work. 2016-01-26 SN-IND-1-015_CANoe_CANalyzer_Padding_DiagnosticFrames.pdf Author(s) Restrictions Morizur, Pascale and Ernst, Oliver Table of contents 1 About this Support Note... 1 2 Overview... 1 3 Set frame