Port BUSACCESS - GENERIC_MAPPINGFILE 🛈¶

Deprecated since version 2025.3. This port will be removed in version 2026.1.

Stimulation¶

Stimulation of bus signals is performed via the model access and is only possible if this also supports stimulation. The restrictions/comments of the model access also apply to the generic bus access.

Restrictions:

Stimulus input signals are not supported.
Trace files being referenced by a DataFileSegment in an STI file are not converted automatically by ecu.test.
It is up to the user to check whether the trace format being used is supported by the tool.

Specifics¶

With this port type you can read and manipulate bus quantities (frames and signals) that are represented in the model. The mapping for bus signals to model data is described in a *.ini. The structure of the file is described in the following section.

Structure of the ini file

The mapping between signal and model path are read from a *.ini file.

In this file the necessary data for channels, frames and sections are described in sections. Every section is prefaced by an identifier in squared brackets. The identifier has to be unique within the file. The options in every section are denoted in the form option = value. Every section has to contain the option Type and Name. Allowed values for the option Type are currently only “Channel”, “Frame” and “Signal”. The name denotes the label of the respective element. Depending on the type, every section has more mandatory and optional options, which are described in the following paragraphs. Other, not listed options can be written into the file, but they won’t be used.

An exception to standard structure of the sections is the section with the label “Global”. In this section default values for the options in the other sections can denoted. This default values will be used, if a mandatory option in a section is missing.

Section type “Channel”

The section contains only the type and the name, but no other options.

Option	Description
Type	“Channel”
Name	Channel name, which also listed in the test bench configuration

Section type “Frame”

The following options are mandatory for every frame:

Option	Description
Type	“Frame”
Channel	Section name of the parent. Must be a section of the type “Channel”.
Name	Label of the frame, which has to match the frame name in the bus database.
RX	Boolean value. If true, the read paths have to present.
TX	Boolean value. If true, the write paths have to present.

Optional values for this section are:

Option	Description
ID	Identifier of the frame. Is currently not used by ecu.test.

Depending on the values of the options RX and TX, other options have to be present. If RX is True, the following options have to be set:

Option	Description
Rx_TimePath	Timestamp of the last received instance of this frame. Is currently not used by ecu.test.
Rx_DeltaTimePath	The time difference between the two last received instances of this frame. Is currently not used by ecu.test.
Rx_MessageCounterPath	Path for reading the count of sent messages. Is currently not used by ecu.test.

If TX is true, the following options have to be set:

Option	Description
KickoutPath	Writing the value 1 in this path triggers a onetime (additive) transmission. Is currently not used by ecu.test.
CycleTimePath	Path for setting the transmission period in ms. Is currently not used by ecu.test.
EnablePath	Path for activating the frame. The value 1 cause a periodic transmission of the frame. If 0 is set, the frame won’t be transmitted.
CRC_ErrorPath	Path used for reading the CRC error. Is currently not used by ecu.test.
AliveCounter_ErrorPath	Path used for reading the alive error. Is currently not used by ecu.test.
Tx_MessageCounterPath	Path used for reading the number of sended messages. Is currently not used by ecu.test.

Section typ “Signal”

The following options have to be present in the signal section:

Option	Description
Type	“Signal”
Frame	Section name of the parent. Must be a section of the type “Frame”.
Name	Label of the signal, which has to match the signal name in the bus database.
RX	Boolean value. If true, the read paths have to present.
TX	Boolean value. If true, the write paths have to present.

Depending on the values of the options RX and TX, other options have to be present. If RX is true, the following options have to be set:

Option	Description
ReadPath	Path, from which the last received signal can be read.

If TX is true, the following options have to be set:

Option	Description
ManipPath	Path, in which the manipulated value is written. The manipulated value will be sent in place of the in model calculated value.
SwitchStyle	The switch style defines, how switching between calculated and manipulated value takes place. Possible switch styles are “Switch”, “Neutral”, “Original”, “SwitchNeutral” and “SwitchOriginal”.
Encoding	Defines the value type, which is used for sending and writing. Allowed values are “Phys” and “Raw”. Is currently not used by ecu.test (fix: phys).

Depending on the switch style, the following options are possible:

Option	Description	Mandatory for:
SwitchPath	Path for switch between calculated and manipulated value.	Switch, SwitchNeutral, SwitchOriginal
NeutralValue	Neutral value, which must be written into the manipulation path to switch back to the calculated values.	Neutral, SwitchNeutral
SwitchManipValue	Value which must be written into the switch path to trigger using the manipulated value.	Switch, SwitchNeutral, SwitchOriginal
SwitchOriginalValue	Value which must be written into the switch path to trigger using the calculated value.	Switch, SwitchNeutral, SwitchOriginal

For every switch style, the manipulated value will be written into the manipulation path. With the switch style “switch”, changing to the manipulated values instead of the calculated values is achieved by writing the respective value into the switch path. The switch value is denoted throug the option SwitchManipValue. With the switch styles “Neutral” and “Original” the changing takes places implicitly. No value has to be written to the switch path.

To change back to the values calculated in the model, with the switch styles “Neutral” and “Original” the value in the manipulation path must be changed. In case of “Neutral” the specified NeutralValue is written there; in case of “Original” the value that has been read from the manipulation path before the start of the test is written back. The manipulation path remains unchanged if the switch style “Switch” is used. In this case the switching takes place explicitly through writing a specific value into the switch path. The value needed to trigger the switching back to calculated model values is specified under the option SwitchOriginalValue.

The switch styles “SwitchNeutral” and “SwitchOriginal” are combinations the describes styles. Therefore, the switch style “SwitchNeutral” behaves like the switch styles “Switch” and “Neutral” and the switch style “SwitchOriginal” behaves like the switch styles “Switch” and “Original”.

Section “Global”

In this section, default values for options in other sections can be declared. If a mandatory option is missing, the default value from the global section will be used.

Internally ecu.test uses the following default values:

Section	Option	Default value
Signal	Encoding	“Phys”
Signal	SwitchStyle	“Switch”
Signal	NeutralValue	-1
Signal	SwitchManipValue	1
Signal	SwitchOriginalValue	0

The default values can be overwritten through the respective entries in global section.

Properties 🛈¶

Name	Type	Description
Bus identifier	string	Logical name of the bus system
INI file	string	INI file including the mapping of bus and model values. Absolute paths reference a file located on the ecu.test host. However, relative paths are resolved relatively to the ecu.test workspace.
Bus-DB	string
Model port	string	Port ID (e.g. “MDL01”) of the model port via which the model access is to be performed. This property can remain empty if there is exactly one model port. If there is more than one model port, this property must be set.