Communication Services (CAN, LIN, FlexRay, Ethernet, Data, RPC)

Overview
CanControllers
LinControllers
EthernetControllers
FlexrayControllers
DataPublishers
DataSubscribers
RpcServers
RpcClients

Overview 

All services of the Vector SIL Kit can be configured within the participant configuration. The following sections describe how each service can be configured. The configuration of the single services is fully optional.

CanControllers 

CanControllers:
- Name: CAN1
  Network: CAN1

Table 4 CanController Configuration
Property Name	Description
Name	The name of the CAN Controller
Network	The name of the CAN Network to connect to (optional)

LinControllers 

LinControllers:
- Name: Lin1
  Network: Lin1

Table 5 LinController Configuration
Property Name	Description
Name	The name of the LIN Controller
Network	The name of the LIN Network to connect to (optional)

EthernetControllers 

EthernetControllers:
- Name: ETH1
  Network: Ethernet1

Table 6 Ethernet Controller Configuration
Property Name	Description
Name	The name of the Ethernet Controller
Network	The name of the Ethernet Network to connect to (optional)
UseTraceSinks	Experimental: Optional list of names of trace sinks, as defined in the Tracing configuration.
Replay	Experimental: The optional replay configuration, as described in Replay.

FlexrayControllers 

FlexrayControllers:
- Name: FlexRay1
  Network: PowerTrainCluster1
  ClusterParameters:
    gColdstartAttempts: 8
  NodeParameters:
    pChannels: AB

Table 7 FlexRay Controller Configuration
Property Name	Description
Name	The name of the FlexRay Controller
ClusterParameters	Allows to configure cluster specific settings. See `ParticipantConfiguration.schema.json` for a full set of parameters. (optional)
NodeParameters	Allows to configure node specific settings. See `ParticipantConfiguration.schema.json` for a full set of parameters. (optional)
TxBufferConfigurations	Allows to configure TXBuffers by specifying “channels” (`A`, `B`, `AB`, `None`), “slotId”, “offset”, “repetition”, “PPindicator”, “headerCrc” and “transmissionMode” (`SingleShot`, `Continuous`). See `ParticipantConfiguration.schema.json` for a full set of parameters. (optional)

DataPublishers 

DataPublishers:
- Name: DataPublisher1
  Topic: SomeTopic1

Table 8 DataPublisher Configuration
Property Name	Description
Name	The name of the data publisher.
Topic	The topic on which the data publisher publishes its information. (optional)

DataSubscribers 

DataSubscribers:
- Name: DataSubscriber1
  Topic: SomeTopic1

Table 9 DataSubscriber Configuration
Property Name	Description
Name	The name of the data subscriber.
Topic	The topic on which the data subscriber publishes its information. (optional)

RpcServers 

RpcServers:
- Name: RpcServer1
  FunctionName: SomeFunction1

Table 10 RPC Server Configuration
Property Name	Description
Name	The name of the RPC server.
FunctionName	The function name on which the RPC server offers its service. (optional)

RpcClients 

RpcClients:
- Name: RpcClient1
  FunctionName: SomeFunction1

Table 11 RPC Clients Configuration
Property Name	Description
Name	The name of the RPC client.
FunctionName	The function name to which the RPC client wants to connect to. (optional)