AUTOSAR Cruise Control Software Components
The objective of this project is to simulate Cruise Control functionality.
In this module there are 3 SWCs:
1.VehComponent
2.CruiseCntrlAlg
3.DrvForceCalc
Block Diagram of Cruise Control Model (AUTOSAR Compliance)
This SWC used to calculate the vehicle speed. VehComponent [Application SW Component Type]
VehIB [Internal Behavior of VehComponent]
Input Ports
Table 1: VehComponent Input Ports
Output Ports
Table 2: VehComponent Output Ports
Runnables: •Run_VehicleTick() [Mapped to TIMING EVENT] : |
This Cruise Control Algorithm SWC calculates the pedal force required to maintain the Set speed. CruiseCntrlAlg [Application SW Component Type]
CruiseCntrlIB [Internal Behavior of CruiseCntrlAlg]
Input Ports:
Table 3: CruiseCntrlAlg Input Ports
ControlCalcPortIn [C/S]: This port acts as ‘Client’, it calls the server, mapped to an Operation Invoked Event (Control function). Output Ports:
Table 4: CruiseCntrlAlg Output Ports
ControlPPortOut [C/S]: This port acts a ‘Server’, which is mapped to an Operation Invoked Event. Runnables •ControlTick() [mapped to TIMING EVENT]: •Control() [mapped to OPERATION INVOKED EVENT]:
|
This SWC calculates the driving force required to maintain the set speed. Figure :DrvForceCal [Application SW Component Type] Figure : DrivingForceCalc [Internal Behavior of DrvForceCalc]
Input Ports:
Table5 : DrvForceCal Input Ports
Output Ports:
Table 6: DrvForceCal Output Ports
Runnables: •DrivingForceCalc() [mapped to TIMING EVENT]: This Event triggers every 0.5ms.
|
Port Details:
Table 7: AUTOSAR Interfaces
Runnable Entities:
Table 8: Runnable Entities
Harness details: 4.3.1. AppIF.c •This include port registrations...etc 4.3.2. MxVAutosarHarness.c •AUTOSAR Interface implementations (see Table7) •TASK implementations (see Table 8) •RTE Life cycle API (Rte_Init(), Rte_Start(), and Rte_Stop()) implementations •StartOS() call..etc 4.3.3. MxVAutosarHarness.h •AppIF port declarations •RTE Life cycle API prototypes •MxVAutosarHarness_Init prototype •MxVAutosarHarness_Tick prototype 4.3.4. MxVOSEKOS.c •OSEK TASK configurations •ALARM configurations 4.3.5. MxVOSEKOS.h •OSEK TASK declarations •ALARM declarations 4.3.6. Application header files •'RTE Contract Phase Generator' enabled from GUI, then transform generates Header files for each SWC (software component). •Includes AUTOSAR Interface prototypes (see Table 7) •Includes mapping assembly connectors (see Table 9) 4.3.7. Assembly Connectors:
Table 9: Assembly Connectors Notes: •The 'RTE Contract Phase Generator' option should be enabled during harness generation. •The Transform does not generate Assembly connector received port AUTOSAR Interfaces in the MxVAutosarHarness.c file, since these received ports are mapped with the provided port data inside the respective required component Rte_<SWC>.h files as macro declarations. •We consider Delegate ports as MxV AppIF ports |
Related Topics: