JSON configuration file for RemotiveBroker. The configuration file must be named interfaces.json and all paths in the configuration are relative paths to this file.
Configures all interfaces that the broker will operate on.
List of configured interfaces available to RemotiveBroker.
No Additional ItemsVirtual signaling interface. This device doesn't use a database, any published signals will be sent to subscribers of the given signal.
Name assigned to device, used in signal operations.
Specifies a virtual interface.
Scripted signals
Specifies a scripted interface.
Path to a scripted database
Path to a scripted database
No Additional ItemsConfigure the interface to be public or private, default is public. Private namespaces are not exposed by the broker. This is useful for example when working with for example scripted VSS signals and you don't want the designer to see the internal vehicle signals.
CAN interface.
Path to signal database file. Supporting .dbc and .arxml. When using an arxml database, canphysicalchannel_name must be specified.
Same definition as databasePath to signal database file. Supporting .dbc and .arxml. When using an arxml database, canphysicalchannel_name must be specified.
No Additional ItemsThis property is required when using an arxml database. Path to the physical channel that should be used. Referenced by SHORT-NAME element, e.g. /Topology/Name/ID
Name of device in OS.
Have signals addressable in the RemotiveBroker by their name in the database.
If false, signal names with be generated base on their respective name space.
Specifies a CAN interface.
baud rate to apply to CAN when starting interface.
Configure the interface to be public or private, default is public. Private namespaces are not exposed by the broker. This is useful for example when working with for example scripted VSS signals and you don't want the designer to see the internal vehicle signals.
Same definition as publicMonitor CAN interfaces for state changes to error passive and reset upon detection. Note: Using virtual CAN devices will not support the built-in automatic recovery for CAN devices that enter passive mode. If automatic recovery mode is enabled for a virtual device, the server will issue a warning each time it attempts to retrieve the device's state.
CAN-FD interface.
Path to signal database file. Supporting .dbc and .arxml. When using an arxml database, canphysicalchannel_name must be specified.
Same definition as databasePath to signal database file. Supporting .dbc and .arxml. When using an arxml database, canphysicalchannel_name must be specified.
No Additional ItemsThis property is required when using an arxml database. Path to the physical channel that should be used. Referenced by SHORT-NAME element, e.g. /Topology/Name/ID
Same definition as can_physical_channel_nameName of device in OS.
Have signals addressable in the RemotiveBroker by their name in the database.
If false, signal names with be generated base on their respective name space.
Specifies a CAN-FD interface.
baud rate to apply to CAN when starting interface.
baud rate to apply to CAN-FD when starting interface.
Configure the interface to be public or private, default is public. Private namespaces are not exposed by the broker. This is useful for example when working with for example scripted VSS signals and you don't want the designer to see the internal vehicle signals.
Same definition as publicMonitor CAN interfaces for state changes to error passive and reset upon detection. Note: Using virtual CAN devices will not support the built-in automatic recovery for CAN devices that enter passive mode. If automatic recovery mode is enabled for a virtual device, the server will issue a warning each time it attempts to retrieve the device's state.
Same definition as auto_recoverCAN-via-UDP protocol. Can be used to communicate between RemotiveBrokers.
Path to signal database file. Supporting .dbc and .arxml. When using an arxml database, canphysicalchannel_name must be specified.
Same definition as databasePath to signal database file. Supporting .dbc and .arxml. When using an arxml database, canphysicalchannel_name must be specified.
No Additional ItemsThis property is required when using an arxml database. Path to the physical channel that should be used. Referenced by SHORT-NAME element, e.g. /Topology/Name/ID
Same definition as can_physical_channel_nameIf set, will use this frame size (bytes) for all packets.
Value must be greater or equal to 0
Required when using multicast to select the correct interface.
UDP port for RemotiveBroker to listen to and receive packets on.
Value must be greater or equal to 0 and lesser or equal to 65535
Have signals addressable in the RemotiveBroker by their name in the database.
If false, signal names with be generated base on their respective name space.
For multicast use, addresses in the range 224.0.0.1 to 239.255.255.255 are supported.
Specifies a CAN-via-UDP interface.
Configure the interface to be public or private, default is public. Private namespaces are not exposed by the broker. This is useful for example when working with for example scripted VSS signals and you don't want the designer to see the internal vehicle signals.
Same definition as publicSOME/IP interface configuration.
Path to signal database file. Supporting .xml and .arxml. When using an arxml database
Same definition as databasePath to signal database file. Supporting .xml and .arxml. When using an arxml database
No Additional ItemsSpecifies a SOME/IP interface.
List of to include from the provided database, can be used to speed up database parsing.
No Additional ItemsValue must be greater or equal to 0 and lesser or equal to 65535
Configuration for SOME/IP service discovery.
Network address accepted by the OS. Eg. Ipv4: 127.0.0.1.
Port number for discovery.
Value must be greater or equal to 0 and lesser or equal to 65535
List of SOME/IP endpoints.
No Additional ItemsSOME/IP endpoint configuration.
Transport protocol
Network address accepted by the OS. Eg. Ipv4: 127.0.0.1.
Service definition for SOME/IP.
Unique service identifier.
Value must be greater or equal to 0 and lesser or equal to 65535
Service instance identifier.
Value must be greater or equal to 0 and lesser or equal to 65535
Major version number.
Value must be greater or equal to 0 and lesser or equal to 255
List of static remote services that this endpoint consumes.
No Additional ItemsStatic remote configuration for SOME/IP services.
Network address accepted by the OS. Eg. Ipv4: 127.0.0.1.
Service definition for SOME/IP.
Same definition as chains_items_oneOf_i5_endpoints_items_service_ids_itemsDiscovery port.
Value must be greater or equal to 0 and lesser or equal to 65535
LIN master or slave node interface. Connects to a RemotiveLabs LIN ethernet device.
If the conditions in the "If" tab are respected, then the conditions in the "Then" tab should be respected. Otherwise, the conditions in the "Else" tab should be respected.
"master" LIN network configuration for communicating with RemotiveLabs LIN service.
LIN node ID.
Value must be greater or equal to 0 and lesser or equal to 16
Network address accepted by the OS. Eg. Ipv4: 127.0.0.1.
Path to LIN signal database .ldf file.
Type of LIN node.
Should LIN schedules start at boot? Or pause until user command.
Path to .ldf file used for schedules.
Path to .ldf file used for tables. TODO
Specifies a LIN interface.
Configure the interface to be public or private, default is public. Private namespaces are not exposed by the broker. This is useful for example when working with for example scripted VSS signals and you don't want the designer to see the internal vehicle signals.
Same definition as publicFlexRay interface.
RemotiveLabs software adapter.
Network address accepted by the OS. Eg. Ipv4: 127.0.0.1.
Technica CAN combo hardware.
What type of hardware.
Network interface to use.
For example eth0.
MAC address to use for multicast.
For example 01:00:5e:00:00:00.
Network address accepted by the OS. Eg. Ipv4: 127.0.0.1.
Path to FlexRay signal database .xml (FIBEX) file.
Specifies a FlexRay interface.
Configure the interface to be public or private, default is public. Private namespaces are not exposed by the broker. This is useful for example when working with for example scripted VSS signals and you don't want the designer to see the internal vehicle signals.
Same definition as publicName of the RemotiveBroker node. Required only if the configuration is used in the distributed broker mode. Example some_node@hostname
Configuration for build in gRPC server. Documentation for available service is available on <https://docs.remotivelabs.com>.
Server port for gRPC server.
Value must be greater or equal to 0 and lesser or equal to 65535
A list of reflector configurations.
No Additional ItemsConfigure reflectors to always bounce traffic.
No Additional ItemsBounce mechanism, with a source and a destination.
Name of source namespace.
Name of destination namespace.
List of frames to exclude in reflector.
No Additional ItemsName of frame to exclude