Short Description
The delay during communication can be constrained by constraints on events of connected ports. For the Design Level the FunctionConnector connecting ports of design functions are allocated to a LogicalBus in the hardware design architecture. Thereby the communication delay can be over that bus is constrained.
For the Implementation Level the events for the Virtual Function Bus, Communication and BswModuleDescription are of interest.
Links to TADL2 concepts
· DelayConstraint
· AgeConstraint
· ReactionConstraint
Abstraction level specific list of applicable events
EAST-ADL events:
· Concrete Events in the functional model at the Analysis and Design Level and specifically the Environment Model at the Vehicle Level.
o EventFunctionFlowPort
o EventFunctionClientServerPort
· receivedRequest
· receivedResponse
· sentRequest
· sentResponse
AUTOSAR events:
· Concrete TimingDescriptionEvents in the AUTOSAR model of the EAST-ADL Implementation Level.
o Timing events at the Virtual Function Bus level
§ TDEventVariableDataPrototype
· variableDataPrototypeReceived
· variableDataPrototypeSent
§ TDEventOperation
· operationCalled
· operationCallReceived
· operationCallResponseReceived
· operationCallResponseSent
§ TDEventModeDeclaration
· modeDeclarationSwitchCompleted
· modeDeclarationSwitchInitiated
o Timing events related to communication including the physical layer (EcuInstance).
§ TDEventISignal
· iSignalAvailableForRTE
· iSignalSentToCOM
§ TDEventIPdu
· iPduReceivedByCOM
· iPduSentToIf
§ TDEventFrame
· frameQueuedForTransmission
· frameReceivedByIf
· frameTransmittedOnBus
§ TDEventFrClusterCycleStart
§ TDEventTTCanCycleStart
o Timing events related to Basic Software modules (BswModuleDescription)
§ TDEventBswModule
· bswMEntryCalled
· bswMEntryCallReturned
§ TDEventBswModeDeclaration
· modeDeclarationRequested
· modeDeclarationSwitchCompleted
· modeDeclarationSwitchInitiated
Context Specific Example
---
|