CLASSIC
Modul: systemtemplate
Rolle: constitutive
Konfidenz: 95%
SNIP_CLASSIC_SYSTEMTEMPLATE_SECTION_6_4_IPdu_Timing
Wortlaut
6.4 IPdu Timing
AUTOSAR COM allows configuring statically two different transmission modes for each
IPdu (True and False). TransmissionModeDeclaration uses a transmission mode
selector, calculated from a number of individual TransmissionModeConditions or
ModeDrivenTransmissionModeConditions to decide which of the two modes is
selected. It is possible to switch between the transmission modes during runtime.
System Template
Describable
IPduTiming
+
minimumDelay: TimeValue [0..1]
TransmissionModeTiming
Identifiable
ISignalToIPduMapping
+
packingByteOrder: ByteOrderEnum [0..1]
+
startPosition: Integer [0..1]
+
transferProperty: TransferPropertyEnum [0..1]
+
updateIndicationBitPosition: Integer [0..1]
DataFilter
+
dataFilterType: DataFilterTypeEnum
+
mask: UnlimitedInteger [0..1]
+
max: UnlimitedInteger [0..1]
+
min: UnlimitedInteger [0..1]
+
offset: PositiveInteger [0..1]
+
period: PositiveInteger [0..1]
+
x: UnlimitedInteger [0..1]
TransmissionModeCondition
Describable
EventControlledTiming
+
numberOfRepetitions: Integer
Describable
CyclicTiming
TransmissionModeDeclaration
FibexElement
ISignal
+
dataTypePolicy: DataTypePolicyEnum
+
iSignalType: ISignalTypeEnum [0..1]
+
length: Integer
IPdu
ISignalIPdu
+
unusedBitPattern: Integer
ARElement
AtpBlueprint
AtpBlueprintable
AtpType
ModeDeclarationGroup
+
onTransitionValue: PositiveInteger [0..1]
AtpStructureElement
Identifiable
ModeDeclaration
+
value: PositiveInteger [0..1]
ModeDrivenTransmissionModeCondition
+modeDeclaration
1..*«atpVariation»
+eventControlledTiming 0..1
+cyclicTiming 0..1
+iSignalInIPdu
1
+iPduTimingSpecification
0..1
«atpVariation»
+modeDrivenTrueCondition
0..*
+dataFilter 1
+initialMode
1
+transmissionModeTrueTiming
0..1
+modeDeclaration
1..*
+iSignalToPduMapping
0..*
«atpVariation»
+iSignal
0..1
+transmissionModeFalseTiming
0..1
+transmissionModeCondition
0..*
+modeDrivenFalseCondition
0..*
+transmissionModeDeclaration
0..1
Figure 6.20: IPdu Timing
[TPS_SYST_01075] Signal content evaluation via TransmissionModeCondition ⌈The signal content can be evaluated as the transmission mode selector via
the TransmissionModeConditions.⌋(RS_SYST_00037)
[TPS_SYST_01076] Mode evaluation via modeDrivenTrueCondition or modeDrivenFalseCondition ⌈Mode conditions can be evaluated as the transmission
mode selector via the modeDrivenTrueConditions or modeDrivenFalseConditions.⌋(RS_SYST_00037)
[constr_3045] Signal content evaluation vs. Mode evaluation ⌈The mode evaluation and the signal content evaluation shall not be used in the same IPdu. A mix of
these two types is not allowed.⌋()
To use the signal content evaluation a TransmissionModeCondition can be attached to each signal within an IPdu. Each TransmissionModeCondition contains a reference to a signal and to an assigned filter. The filter condition is used for
System Template
the selection of the transmission mode. If at least one condition in the signal content
evaluation is true, Transmission Mode "TRUE" shall be used for this IPdu. In all other
cases, the Transmission Mode "FALSE" shall be used. More details can be found in
the COM Specification [21].
[constr_3046] Consistency of TransmissionModeCondition.iSignalInIPdu
⌈The ISignalToIPduMapping referenced by the TransmissionModeCondition
in the role iSignalInIPdu shall belong to the same ISignalIPdu as the TransmissionModeCondition.⌋()
In the mode driven evaluation ModeDeclarations are evaluated. The transmissionModeFalseTiming is activated if all defined modeDrivenFalseConditions
evaluate to true and the transmissionModeTrueTiming is activated if all defined
modeDrivenTrueConditions evaluate to true. Each condition that is defined by
ModeDrivenTransmissionModeCondition evaluates to true if one of the referenced ModeDeclarations is active.
The TransmissionModeDeclaration element aggregates the TransmissionModeTiming in two different roles: transmissionModeTrueTiming and transmissionModeFalseTiming. The available COM Transmission Mode Timings can
be described by the CyclicTiming and EventControlledTiming elements (see
Table 6.66) that are aggregated by the TransmissionModeTiming class.
[TPS_SYST_01077] Mapping of Com Transmission Modes to System Template
elements ⌈The mapping of COM Transmission Modes to System Template elements
is described in Table 6.66.⌋(RS_SYST_00037)
COM
Transmission
Modes
Description
realization in System Template
Periodic
Transmissions occur indefinitely
with a fixed period between them
CyclicTiming
Direct/n-times
Event driven transmission with n-1
repetitions
EventControlledTiming
Mixed
Periodic
transmission
with
direct/n-times
transmissions
in between
EventControlledTiming
and
CyclicTiming
None
No transmission
no timing assigned
Table 6.66: COM Transmission Modes
Class
TransmissionModeDeclaration
Package
M2::AUTOSARTemplates::SystemTemplate::Fibex::FibexCore::CoreCommunication::Timing
▽
System Template
△
Class
TransmissionModeDeclaration
Note
AUTOSAR COM provides the possibility to define two different TRANSMISSION MODES (True and
False) for each I-PDU.
As TransmissionMode selector the signal content can be evaluated via transmissionModeCondition
(implemented directly in the COM module) or mode conditions can be defined with the modeDrivenTrue
Condition or modeDrivenFalseCondition (evaluated by BswM and invoking Com_SwitchIpduTxMode
COM API). If modeDrivenTrueCondition and modeDrivenFalseCondition are defined they shall never
evaluate to true both at the same time.
The mixing of Transmission Mode Switch via API and signal value is not allowed.
Base
ARObject
Attribute
Type
Mult.
Kind
Note
modeDriven
FalseCondition
ModeDriven
TransmissionMode
Condition
*
aggr
Defines the trigger for the Com_SwitchIpduTxMode
Transmission Mode switch. Only if all defined modeDriven
FalseConditions evaluate to true (AND associated) the
transmissionModeFalseTiming shall be activated. mode
DrivenTrueCondition and modeDrivenFalseCondition
shall never evaluate to true both at the same time.
modeDriven
TrueCondition
ModeDriven
TransmissionMode
Condition
*
aggr
Defines the trigger for the Com_SwitchIpduTxMode
Transmission Mode switch. Only if all defined modeDriven
TrueConditions evaluate to true (AND associated) the
transmissionModeTrueTiming shall be activated. mode
DrivenTrueCondition and modeDrivenFalseCondition
shall never evaluate to true both at the same time.
transmission
ModeCondition
TransmissionMode
Condition
*
aggr
The Transmission Mode Selector evaluates the conditions
for a subset of signals and decides which transmission
mode should be used. In case only one transmission
mode is used there is no need for the "TransmissionMode
Condition" and its sub-structure. In case the transmission
mode shall be switched using the COM-API "Com_Switch
IpduTxMode" there is no need for the "TransmissionMode
Condition" and its sub-structure.
transmission
ModeFalse
Timing
TransmissionMode
Timing
0..1
aggr
Timing Specification if the COM Transmission Mode is
false. The Transmission Mode Selector is defined to be
false, if all Conditions evaluate to false.
transmission
ModeTrue
Timing
TransmissionMode
Timing
0..1
aggr
Timing Specification if the COM Transmission Mode is
true. The Transmission Mode Selector is defined to be
true, if at least one Condition evaluates to true.
Table 6.67: TransmissionModeDeclaration
Class
TransmissionModeCondition
Package
M2::AUTOSARTemplates::SystemTemplate::Fibex::FibexCore::CoreCommunication::Timing
Note
Possibility to attach a condition to each signal within an I-PDU.
If at least one condition evaluates to true, TRANSMISSION MODE True shall be used for this I-Pdu. In all
other cases, the TRANSMISSION MODE FALSE shall be used.
Base
ARObject
Attribute
Type
Mult.
Kind
Note
dataFilter
DataFilter
1
aggr
Possibilities to define conditions
iSignalInIPdu
ISignalToIPduMapping
1
ref
Reference to a signal to which a condition is attached.
Table 6.68: TransmissionModeCondition
Versionen & Provenienz · Zugeordnete Anforderungen
Diese Angaben zeigt der Versions-Explorer.
Begründung & Zuweisungs-Evidenz
Cited verbatim in the snippet (deterministic citation).
Dokumenten-Herkunft & Rückverfolgbarkeit
| Spezifikations-Dokument | SystemTemplate.pdf |
|---|---|
| Dokumentseite | Seite 274 |
| Ziel-Modul | systemtemplate (classic) |
| Ziel-Anforderung | TPS_SYST_01077 |
| Semantische Rolle | constitutive |
| Automatisierungs-Konfidenz | 0.95 |