advertisement
ETAS Understanding INTECRIO
3.2.2.1
Application Software
The application software (or functional software) contains the signal flowdriven control algorithm. This is a generic description that does not change its behavior (based on requirements and specifications). The software consists of individual modules or AUTOSAR software components and module/SWC
groups or functions (see Fig. 3-9 and the left side of Fig. 3-7).
Module/SWC A
Module/SWC B Module/SWC C
Module/
SWC A
Module/
SWC B
Module/
SWC C
Crossbar / AUTOASR-RTE
Activation interface
Communication driver
OSEK operating system
I/O driver
(hardware abstraction layer)
....
Signal sinks
Calculation algorithm
Signal sources
BMT view
Data
Fig. 3-9 Functional software: Details
The overview in Fig. 3-2 shows the development of the electronic control unit
software as a single development phase; however, section 3.1.2, Fig. 3-4
already showed that this phase is divided again into other phases. This figure is still too rough, though; even in the development of a specific functionality, it is possible that the individual modules, SWC or functions are developed by different suppliers using different tools.
Modules and AUTOSAR software components are principally designed the same way from the INTECRIO perspective and feature the following interfaces:
• Signal sinks (inputs or clients and receivers),
• Signal sources (outputs or server and sender),
• Activation interfaces (processes or runnable entities (RE); graphically not shown).
Sink 1 Source 1
Sink 2
...
Source 2
...
Module 1
Signal flow connection
Sink 1 Source 1
Sink 2
...
Source 2
...
Module 2
Receiver
Client
Mode
SWC A
Sender
Server
Fig. 3-10 Module/SWC: Schematic design (external view) and connection
Modules and AUTOSAR software components are also identical from an internal design. In addition to the interfaces listed, the internal view contains the following components:
• Calculation algorithm or functionality,
INTECRIO V4.7 - User’s Guide 20
ETAS Understanding INTECRIO
• Data of variables, constants and parameters.
Sink 1 Source 1
Sink 2 Source 2
...
Module 1
...
Activation interface
Signal sinks
(inputs)
Calculation algorithm
Signal sources
(outputs)
Sink 1 Source 1
Sink 2 Source 2
...
Module 2
...
Internal view
Data
(variables/ constants/parameters)
Module 1
Fig. 3-11 Modules: schematic internal view
Fig. 3-12 shows a simple ASCET example for the internal view of a module.
Activation interface
Signal sinks
Calculation algorithm
Signal sources
Internal view
Data
Fig. 3-12 Module: ASCET example
INTECRIO V4.7 - User’s Guide 21
ETAS Understanding INTECRIO
The activation interfaces correspond to the ASCET processes, signal sinks and sources correspond to the receive and send messages in ASCET. Variables, parameters and constants are represented by ASCET objects of the same
name. Fig. 3-13 shows the same example for MATLAB and Simulink.
Simulink model
Activation interface
Signal sinks
Calculation algorithm
Signal sources
Internal view
Data
Fig. 3-13 Module: Simulink ® example
For information to be exchanged between modules/SWC or functions and to create a functioning overall system, the objects must be interconnected, i.e. integrated. The calculation algorithms of the individual modules/SWC, i.e. their functionality, do not play a role for integration. The modules are handled as
"black boxes" with
Source 1 = f
1
(sink 1, sink 2, ...) and
Source 2 = f
2
(sink 1, sink 2, ...)
INTECRIO V4.7 - User’s Guide 22
advertisement