This chapter will break down the use of the ADTF Calibration Toolbox 3. After reading this guide, you will know:
We provide an example project in order to show the use cases of several filters provided in this toolbox. The project contains several ADTF sessions for different use cases.
Demo XCP Substreams
The following sections will describe, how you can use the delivered sessions and their purposes.
In general, the sessions can be started in different ways. But we recommend to start them with the ADTF GUI Control, therefor you have to follow these steps:
Open the above mentioned ADTF-Project (calibrationtoolbox.adtfproject)
By selecting one of the listed sessions you will be asekd, what URL should be used. Simply use the default-values.
Now you can directly set your session in the 'initialized' and 'running' - state
This section will explain you, how you can connect two ADTF-Sessions with the help of the 'XCP on Ethernet' - Components. Our Master-Session includes the XCP-Master-, XCP-Decoder- and the necessary XCP-Encoder-Filter in his filter graph. These filters are used to de- and encode the XCP frames. For easy generation of example values, we deliver a QtQick-Filter (the XCP Communication). For the communication with the slave, which contains the ECU, we use in the streaming graph the delivered XCP On Ethernet Receiver and Transmitter.
If both sessions are running, the master sessions 'sends' your new values via the transmitter to the ECU (within the slave session). This virtual ECU processes the received values and gives the master session a reply.
But how can we start two sessions?
Go the same way as described above, but stop at point 3. Now it's important to use a unique URL for the second session (because port 8000 is already in use). For example use:
At first you have to start the xcp_on_eth_Slave session, before you can start the xcp_on_eth_Master session. Otherwise you will get a failure, which mentions
that the master session cannot establish a connection to the ECU.
If both sessions are running your are able to use the 'XCP Communication' window to generate and send values to the virtual ECU. Just play around with the example values (testudword1, period, period_d) and hit 'Send'.
Thanks to the open Mediadescription displays, you are able to see all the values, that are transmitted.
This is the way, how you can calibrate and read values of an ECU via the 'XCP on Ethernet' components.
You can follow the way described above. But you have to start only the
xcp_without_transportlayer session. This configuration could be useful, if you would like
to test your own written XCP-Emulator.
If you would like to build your own configuration, you can follow these steps: