AUTOSAR Cruise Control Composition

This SWC used to calculate the vehicle speed.

CC2

VehComponent [Application SW Component Type]

CC3

VehIB [Internal Behavior of VehComponent]

Input Ports

Base Data Type	Implementation Data Type	Port Name	Interface Type
double	Gradient_T	GradientIn	S/R
double	Force_T	DrvForceIn	S/R

Table 1: VehComponent Input Ports

Output Ports

Base Data Type	Implementation Data Type	Port Name	Interface Type
double	Speed_T	VehSpeedOut	S/R
double	WindResistance_T	WindResistanceOut	S/R

Table 2: VehComponent Output Ports

Runnables:

•Run_VehicleTick() [Mapped to TIMING EVENT] :
This Event triggers every 0.5ms.

This Cruise Control Algorithm SWC calculates the pedal force required to maintain the Set speed.

CC4

CruiseCntrlAlg [Application SW Component Type]

CC5

CruiseCntrlIB [Internal Behavior of CruiseCntrlAlg]

Input Ports:

Base Data Type	Implementation Data Type	Port Name	Interface Type
double	Speed_T	CruiseSpeedIn	S/R
Unsinged char	Mode_T	ToggleCruiseOnRisingEdgeIn	M/S
--	--	ControlCalcPortIn	C/S

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:

Base Data Type	Implementation Data Type	Port Name	Interface Type
double	CCPedal_T	CCPedalOut	S/R
--	--	ControlPPortOut	C/S

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]:

This Event triggers every 0.5ms.

•Control() [mapped to OPERATION INVOKED EVENT]:

This Event triggered by client port.

This SWC calculates the driving force required to maintain the set speed. CC6

Figure :DrvForceCal [Application SW Component Type]

CC7

Figure : DrivingForceCalc [Internal Behavior of DrvForceCalc]

Input Ports:

Base Data Type	Implementation Data Type	Port Name	Interface Type
double	CCPedal_T	CCPedalPercentIn	S/R
double	CCPedal_T	UserPedalPercentIn	S/R

Table5 : DrvForceCal Input Ports

Output Ports:

Base Data Type	Implementation Data Type	Port Name	Interface Type
double	Force_T	DrvForceOut	S/R

Table 6: DrvForceCal Output Ports

Runnables:

•DrivingForceCalc() [mapped to TIMING EVENT]:

This Event triggers every 0.5ms.

Port Details:

SWC Name	Port Name	AUTOSAR Interface	Interface Type
VehComponent	GradientIn	Rte_Receive_GradientIn_VehGradient	S/R
	DrvForceIn	Rte_Read_DrvForceIn_DrvForce	S/R
	WindResistanceOut	Rte_Send_WindResistanceOut_WindResistance	S/R
	VehSpeedOut	Rte_IWrite_VehSpeedOut_VehSpeed	S/R
CruiseCntrlAlg	CruiseSpeedIn	Rte_IRead_CruiseSpeedIn_VehSpeed	S/R
	ToggleCruiseOnRisingEdgeIn	Rte_Mode_ToggleCruiseOnRisingEdgeIn_ ToggleCruiseOnRisingEdgeGrp	M/S
	CCPedalOut	Rte_Write_CCPedalOut_CCPedal	S/R
	ControlCalcPortIn	Rte_Call_ControlCalcPortIn_ControlCalc	C/S
DrvForceCalc	UserPedalPercentIn	Rte_Read_UserPedalPercentIn_UserPedalPercent	S/R
	CCPedalPercentIn	Rte_Read_CCPedalPercentIn_CCpedal	S/R
	DrvForceOut	Rte_Write_DrvForceOut_DrvForce	S/R

Table 7: AUTOSAR Interfaces

Runnable Entities:

SWC Name	Runnable Name	Event Type	Task Name
VehComponent	Run_VehicleTick()	Timing Event (0.5ms)	MxV_Task_Alarm
CruiseCntrlAlg	ControlTick()	Timing Event (0.5ms)	MxV_Task_Alarm
CruiseCntrlAlg	Control()	Operation Invoked Event
DrvForceCalc	DrivingForceCalc()	Timing Event (0.5ms)	MxV_Task_Alarm

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)
Note: Harness generation will depend on 'ARXML FILES ONLY'.

4.3.7. Assembly Connectors:

Provided Component	Received Component	Provided Port	Received Port
VehComponent	CruiseCntrlAlg	VehSpeedOut	CruiseSpeedIn
CruiseCntrlAlg	CruiseCntrlAlg	ControlCalcPortIn	ControlPPortOut
CruiseCntrlAlg	DrvForceCalc	CCPedalOut	CCPedalPercentIn
DrvForceCalc	VehComponent	DrvForceOut	DrvForceIn

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