Senders Service Interface Properties

R2026b

Configure sender service interface definitions for port elements of Out Bus Element blocks

Since R2026b

Use the Senders tab of the Service Mappings editor to map signals of Out Bus Element blocks to sender service interface definitions

A sender service is the endpoint of a communication service. It sends data elements from sender port elements, which are individual signals of Out Bus Element blocks, to other components in the system.

Properties

The table entries in the Senders tab are organized as parent entries and child entries. Each parent entry corresponds to an Out Bus Element block of the top model. Each child entry corresponds to a single port element of the Out Bus Element block. Use the table entries to configure sender service definitions for each port element.

Source — Name of corresponding model element

This property is read-only.

Name of the model element that corresponds to the table entry.

Sender Service — Type of service

Default:Queued | Default:LatestValue | Queued | LatestValue

Must specify the type of service of the receiving party:

LatestValue

The receiver service keeps only the last received data element. Any older data element that has not been delivered to the port element is discarded upon arrival of a new element.

Queued

The receiver service keeps incoming data elements in a queue, and delivers each of them to the port element in turn.

Default:Queued or Default:LatestValue

Use the predefined default value, LatestValue or Queued, as the type of service. Select this option for model elements that need to use the predefined value regardless of its value, for example, when you need your model behavior to be consistent with other models.

Sample Time — Seconds between consecutive sending events

-1 (default) | positive number

This property is applicable only in periodic systems with fixed-step size and must be compatible with the value of the property on the receiving party.

Seconds between consecutive events of sending a data element through the port element by the generated code.

-1

Inherit the sample time from the system. The generated code sends to the sender port element once every system step.

positive scalar

Number of seconds between one sample and the next. The value must be an integer multiple of the fixed-step size of the model.

AUTOSAR

AUTOSAR

Service port — Combine sender events with server methods

Default: Out Bus Element block name (default) | dictionary required port | ...

Use this property to combine events from a sender port with methods from a server port.

Only applies to parent entries.

By default, each Out Bus Element block maps to a separate AUTOSAR Adaptive Required port with the same name as the block. This includes both blocks that are mapped to sender services and blocks that are mapped to server services. To combine the events of a block that is mapped to sender services with the methods of a block that is mapped to server services onto a shared required port, specify the same required port as the Service port of both blocks. To learn about the AUTOSAR dictionary and required ports in it, see Define AUTOSAR Adaptive Software Component Ports and Interfaces.

To configure this property, click the pencil icon at the end of the parent entry to open the dialog box. In the AUTOSAR section, select the service port to use with this port.

Alternatively, you can select the parent port in the model canvas while the Property Inspector is open. Then, in the Service tab of the Property Inspector, in the AUTOSAR section, select the service port to use with this port.

Version History

Introduced in R2026b