Clients Service Interface Properties
R2026b
Use the Clients tab of the Service Mappings editor to map port elements of In Bus Element blocks to client service interface definitions
A client service is used to invoke Simulink® functions on other components in the system. A function caller in the model can be mapped to a client port, modeled as an In Bus Element port element, and invoke it as it would invoke a Simulink function in the model. The client service communicates with the server service to invoke the Simulink function on the other component.
Properties
The table entries in the Clients tab are organized as parent entries and child entries. Each parent entry corresponds to a client (modeled as an In Bus Element block). Each child entry corresponds to a function prototype of the client (modeled as an In Bus Element block element).
This property is read-only.
Name of the model element that corresponds to the table entry.
Only applies to child entries. Determines whether the client blocks while waiting for results from the server, or continues execution and polls for results at each execution step. In either case, the client stops waiting for results or stops polling for results once the timeout is exceeded.
Only applies to child entries. The maximum number of seconds the client attempts to
retrieve server results after function invocation. The value Inf
indicates that the caller waits indefinitely. You can either manually enter
Inf, or leave empty to have the software automatically treat the
value as Inf. When Call behavior is set to
Wait for server results:
The timeout must not be greater than the fixed-step size of the model.
If timeout is exceeded before getting results from the server, the client stops waiting for them.
When Call behavior is set to Allow delayed
server results and timeout is exceeded before getting results from the
server, the client stops polling for results.
AUTOSAR
AUTOSAR
Use this property to combine events from a receiver port with methods from a client port.
Only applies to parent entries.
By default, each In 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 receiver services and blocks that are mapped to client services. To combine the events of a block that is mapped to receiver services with the methods of a block that is mapped to client 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 receiver 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.
More About
There are no additional properties to the client service interface, but you can still
open the dialog box by clicking the pencil icon . To use the dialog box for opening the Property Inspector,
click the Open in Property Inspector button.
Version History
Introduced in R2026b
