Port SERVICEACCESS - SERVICE_MANAGER 🛈

Service access via model

Stimulation

The stimulation of ServiceEvent signals takes place via the model access and is only possible if this also supports the stimulation. The restrictions/comments of the model access also apply to the generic ServiceManager 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

This port enables access to ethernet events using a model port. Service mappings from a configured Ethernet database can be used in the test case this way. For Read or Write test steps, a corresponding model path is accessed. These model quantities have to exist in the model. Their paths need to match a path template relative to the respective service mapping. These path templates are defined in a configuration file in XML format with the following structure.

<modelpathtemplates>
    <bus name="ETHERNET" trcFileServiceInterfaceShortNameActivated="True">
        <template name="[...]">
            <path>[...]</path>
        </template>
    </bus>
</modelpathtemplates>

Path templates

The port uses templates with “name”s as follows:

• base

  Base path that can be used in other templates

• manip

  Path for writing access

• switch

  Path for activating a manipulation

• org

  Path for reading access

• arrayMux

  Path for special treatment of multiplexers

• arrayDim

  Path for dynamic array length

• unpackCounter and receivedCounter

  Path for variables that need to increase before the next model access

Available placeholders

The path templates in the configuration file can contain certain placeholders. Those will be automatically replaced when accessing service events. A placeholder always begins with the character “%” and is enclosed by parenthesis, like so: %(<placeholder>). The closing parenthesis has to be followed by a formatter.

Info

A valid expression could be e.g: %(base)s/%(consumerNode)s/%(service)s/Events/%(alternativeMethodNameISignalIPdu)s/%(parameter)s/Value.

The following placeholders are permitted:

• base

• board

• busNameEthernet

• node

• consumerNode

• pcsis

• service

• serviceID

• instance

• alternativeMethodNameISignalIPdu

• alternativeMethodNameClientServerInterface

• alternativeStructureNameSystemSignal

• alternativeStructureNameISignal

• parameter

• method

• event

• i_matrixDim

• i_dynamicArrayDimension

• i_paramRoot

The “base” placeholder can be defined as a path template and then be referenced as placeholder in other templates.

Write access

To access events by writing, the port to be used for manipulation must be configured in the test configuration in addition to the service port. This manipulation port is optional.

Recording

Recording an event leaf will create a recording of the matching read model variable on the underlying model port. A sidecar file is created in the report folder next to the recording file that allows the trace analysis to match the model path with the service mapping.

Info

Recording array elements is not supported for technical reasons. ConsumerNodes in the mapping do not apply to recordings.

Notes

• It is possible that the templates do not uniquely define one model path for a given service mapping. If multiple model paths are found, the first one is used.

Properties 🛈

Name	Available if	Default value	Valid values	Type	Description
Path to the configuration file				string	This file on the tool host defines templates to find the matching model paths based on service data. Can be absolute or relative to the tool host base path.
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.
Cycle time ❲ms❳		100		int	Simulation step size of the model. Will be used as waiting time between sequential model access steps if new values need to be calculated within the model. For example, when reading an array the corresponding index is first registered in the model. The correct matching value is only available when it has been calculated by the model after a specified time.

2025-12-05