Presented in Partial Fulfillment of the Requirements for

The Degree Of National Diploma of Engineering in Advanced Technologies

Option: Advanced Electronics and nanotechnology

Technical Internship
Host Company: ELCO Solutions

Presented by: Zohra BENAMOR

1/23/2024 1
 01 Host company
presentation

OUTLINE
Internship context &
AUTOSAR Architecture
overview
02

03 Communication Stack &

CAN Protocol

CAN Configuration &

Diagnostic tools 04

05 Conclusion &
Perspectives
1/23/2024 2
 1.
Host company
presentation
1/23/2024 3
1 Host Company presentation

• A Tunisian software engineering and

development company, founded in 2015,
specialized in software outsourcing and
Nearshoring.

• Provides a complete solution of embedded

software services, focusing on industrial
automation and industrial communication
systems.

• Offers a variety of services in the automotive

field. It supports customer projects related to
AUTOSAR, automotive connectivity, real-time
systems, test and validation

1/23/2024 4
 2.
Internship context &
AUTOSAR
Architecture overview

1/23/2024 5
2 Internship context & AUTOSAR Architecture overview

1/23/2024 6
2 Internship context & AUTOSAR Architecture overview

• Hardware and software widely independent of

each other

• Decouplable development (by abstraction)

through horizontal layers; therefore, reduced
development time and costs

• Enhanced quality and efficiency through

software reuse

1/23/2024 7
2 Internship context & AUTOSAR Architecture overview

1/23/2024 8
2 Internship context & AUTOSAR Architecture overview

Application Layer:

• The topmost layer where the application-specific

software components are implemented.

• Includes software functions responsible for

specific vehicle features and functionalities, such
as engine control, brake management…

• The application layer is developed independently

of the underlying hardware and communicates
with the lower layers through standardized
interfaces.

1/23/2024 9
2 Internship context & AUTOSAR Architecture overview

Runtime Environment (RTE) Layer:

• Sits between the application layer and the basic

software layer.

• Facilitates communication between different

software components by providing a standardized
runtime environment.

• Manages the interaction between software

components, ensuring that they can work together
seamlessly without detailed knowledge of each
other.

1/23/2024 10
2 Internship context & AUTOSAR Architecture overview

Basic Software (BSW) Layer:

•The layer responsible for providing standardized and

reusable software services that are essential for the
operation of the entire system.

•Includes services related to communication , diagnostics,

operating system functions, and more.

•Ensures that the application layer can access necessary

system services in a consistent and standardized manner.

1/23/2024 11
 3.
Communication Stack
& CAN Protocol

1/23/2024 12
3 Communication Stack & CAN Protocol

•Communication Management (ComM): Manages ECU

communication modes and coordination within the network.

•CAN Network Management (Nm): Coordinates network-

wide communication activities and startup/shutdown
processes.

•PDU Router: Routes Protocol Data Units (PDUs) between

different networks, enabling communication between ECUs.

•CAN TP: enable the transmission of large data frames over

the CAN bus, ensuring efficient and error-tolerant
communication between Electronic Control Units (ECUs).

•CAN SM: manages the various states and transitions that a

CAN node (Electronic Control Unit or ECU) goes through
during the communication process on the CAN bus.

1/23/2024 13
3 Communication Stack & CAN Protocol

1/23/2024 14
3 Communication Stack & CAN Protocol

Data Frame (CAN Data Frame):

•The most common type of CAN frame used for transmitting data between ECUs.

•Carries payload data (0 to 8 bytes) along with control and addressing information.

•Used for regular data transmission in the CAN network.

1/23/2024 15
3 Communication Stack & CAN Protocol

Remote Frame (CAN Remote Frame):

•Used to request data from another ECU in the network.

•Contains an identifier (similar to a Data Frame) but without actual payload data.

•Requests another ECU to send data identified by the frame's identifier.

1/23/2024 16
3 Communication Stack & CAN Protocol

Error Frame (CAN Error Frame):

•Indicates the presence of errors in the network.

•Contains error flags and no data payload.

•Generated and transmitted when errors such as CRC errors or bit errors are detected.

1/23/2024 17
3 Communication Stack & CAN Protocol

CAN FD (Flexible Data-rate):

•Introduces extended capabilities, including larger payload lengths (up to 64 bytes) and increased data rates.

•Includes additional frame types: FD Data Frame and FD Remote Frame.

•Bus load problems would be reduced drastically.

•Using several CAN buses would no longer be necessary.

•The need for gateways would be reduced if not abolished.

•Less segmentation of data thanks to larger payloads per frame

•A better ratio of payload and overhead data by fewer frames

1/23/2024 18
 3.
CAN Configuration &
Diagnostic tools

1/23/2024 19
3 CAN Configuration & Diagnostic tools

Purpose:

 Communication Matrix Configuration

 Frame and Signal Configuration

 Bus Configuration

 Timing Configuration

 Error Handling Configuration

 Network Management Configuration

 Diagnosis Configuration

1/23/2024 20
3 CAN Configuration & Diagnostic tools

1/23/2024 21
3 CAN Configuration & Diagnostic tools

CAPL (Communication Access Programming Language)

 Message Generation & Reception

 Signal Manipulation

 Simulation Control

 Error Handling

1/23/2024 22
 3.
Conclusion &
Perspectives

1/23/2024 23
5 Conclusion & Perspectives

Acquire new skills and a great kick off to start a carreer in automotive
industry.

Experience the challenges of professional environment.

Enhance our abilty of managing time and working under pressure.

1/23/2024 24
 Thank you for paying
attention !

1/23/2024 25