Our customer is an electronics manufacturing company with expertise in various control systems used in automotive and other industries.
ISO 26262 compliant automotive applications involve exchange of safety-critical data amongst the ECUs. Safety-critical data must reach the intended node within the timeframe, in the correct sequence and without any loss of data.
The customer’s development team faced the challenge in implementing the required protection modules for exchange of safety-critical data. Although the customer had completed the concept phase and were ready with the technical safety-requirements (TSR) and safety-goals, implementation of some of the safety mechanism related to data transmission was posing considerable challenge.
In a nutshell,
In order to mitigate this challenge, the customer was looking for a technology partner with deep domain knowledge of ECU communication as well as ISO 26262 functional safety. Embitel totally fit the bill for both ISO 26262 and ECU communication expertise.
End-to-End protection module was designed based on the technical safety requirements provided by the customer.
Our automotive team divided the scope of the project into two parts- E2E profile development and CRC Library implementation.
The protection module ensured that:
The E2E data exchange protection module was designed to handle the following potential faults:
Repetition : Unintended message repetition due to the same message being unintentionally sent again.
Loss : message loss during transmission.
The following cyclic redundancy check algorithms were developed and implemented to ensure the integrity of the data that is exchanged. The required version of the CRC can be chosen at runtime.
We had assumed complete responsibility of E2E protection module development which left the customer with ample resources and bandwidth to execute development of the application parallelly.
The customer was able to integrate the E2E protection profile with the target environment without losing any time, thus reducing the turn-around time.
Since we went for AUTOSAR 4.4 implementation, all APIs were standardized, and compatibility issues were mitigated right from the start to ensure seamless integration.