In an in-vehicle network, information exchange usually involves communication between multiple Electronic Control Units (ECUs). For safety-related signals such as speed, gear, vehicle/power mode, etc., data integrity and reliability are of paramount importance. tsmaster has developed the AUTOSAR E2E emulation module for users to realize end-to-end data protection, ensuring that data is not tampered with, lost or corrupted during transmission. This article focuses on the instructions for using TSMaster AUTOSAR E2E.
KEYWORDS in this article: TSMaster.AUTOSAR, E2E
Description of symbols
Some of the styles and symbols used in this article can be found in the following table descriptions.
Functional Overview
TSMaster has developed an AUTOSAR E2E emulation module for users. Based on the AUTOSAR E2E mechanism and the configuration information inputted by the user, the emulation module realizes the protection and detection of data, and shows whether the sent E2E information and received E2E information are correct or not through the UI interface. It mainly contains the following functions:
- E2E Messaging
- E2E Message Detection
- E2E Fault Injection
- Other development/testing functions
AUTOSAR E2E emulation module currently only supports CAN, CAN FD, SOME/IP, and will continue to add LIN, FlexRay, Ethernet.
Windows Forms
The AUTOSAR E2E simulation module contains two main functional areas.
- network composition
- text
3.1 Network composition
The network composition mainly displays the E2E information from the loaded ARXML in a tree structure, in the form of networks/nodes/messages/signal groups/signals.
Network - Message - Signal Value - Signal", "Type", "Configuration Name", "Configuration Type" are present in the network composition ".
network-newsletter-signal-value-signal.
Type:
Configuration Name:
Configuration type:
3.2 Information
The main contents of "Information" are the Profile algorithm information corresponding to the selected SignalGroup, as well as the E2E transmit and receive parity information.
The form description is as follows:
typical example
This section is about building and analyzing the TSMaster AUTOSAR E2E project.
4.1 TSMaster AUTOSAR E2E Project Construction
The database used by the TSMaster software in this paper is a temporary database and only demonstrates the implementation and detection of AUTOSAR E2E.
4.1.1 Importing the database
TSMaster has several ways of importing databases (dbc\ldf\ARXML\xml):
▲ Drag and drop the database file to the TSMaster software, it can be loaded to the corresponding bus type channel 1 by default, and then in the TSMaster software, you can modify the database to bind to the specified channel, the operation is shown in the following figure:
▲ In TSMaster, click [Analysis] -> [Databases] -> select the corresponding bus -> right-click the corresponding channel to add a database, as shown in the following figure:
After the above operation, the data has been successfully added to the TSMaster software.
4.1.2 View AUTOSAR E2E information
In TSMaster, click [Simulation] -> [AUTOSAR E2E] as shown below:
4.1.3 Enabling AUTOSAR E2E
To enable AUTOSAR E2E, simply activate the corresponding node in the RBS simulation to automatically enable the AUTOSAR E2E implementation and detection mechanism:
In TSMaster, click [Simulation] -> [CAN RBS Simulation] as shown below:
4.1.4 Verifying E2E Messages
After the previous operations in this subsection are complete, start the measurement, turn on the RBS emulation, and you can see the telegrams being sent in the Bus Information window. This is shown in the following figure:
In the message information interface, you can see that the CRC signal and RC signal are changing in real time, but users do not know whether the E2E information is correct or not in this interface. At this time, go back to AUTOSAR E2E Viewer and check the corresponding E2E SignalGroup to see whether the E2E information is correct or not, the green color indicates correct, red color indicates error, and black color indicates that the SignalGroup information is not detected. As shown in the figure below:
E2E Detection Status:
4.2 E2E Fault Injection
In TSMaster, a series of fault injection functions are provided for users to use to perform fault injection test, the current types of fault injection provided are as follows:
- lost message
- Signal value fixed
- CRC error
- RC Error
4.2.1 CRC Fault Injection
To implement CRC fault injection, you need to set the CRC value in the C script or Python script of TSMaster.
The sample C script code is shown below:
4.2.2 RC Fault Injection
To implement RC fault injection, you need to set the RC value in the C script or Python script of TSMaster.
The sample C script code is shown below:
API
5.1 can_rbs_fault_inject_handle_on_autosar_crc_event
5.2 can_rbs_fault_inject_handle_on_autosar_rc_event
Tip:
1. Software download:
Click on the software download link below to download and install directly, beta version is recommended:
2. Software upgrades:
You can check for upgrades to the latest version within the software, provided that your computer has an Internet connection.
Note: TOSUN Technical Support Email:support@tosunai.cnWe welcome inquiries! (Company and contact information must be indicated)
English 
Chinese