Name of the RemotiveBroker node. Required only if the configuration is used in the distributed broker mode.
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.
CAN interface.
Path to signal database file. Supporting .dbc and .arxml. When using an arxml database one should specify canphysicalchannel_name.
This 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.
CAN-FD interface.
Path to signal database file. Supporting .dbc and .arxml. When using an arxml database one should specify canphysicalchannel_name.
Same definition as databaseThis 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.
Internal RemotiveLabs protocol for UPD communication over network. Can be used to communicate between RemotiveBrokers.
If set, will use this frame size (bytes) for all packets.
Value must be greater or equal to 0
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.
Network address accepted by the OS. Eg. Ipv4: "127.0.0.1"
.
Sets the device type to UDP
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"
.
Type of LIN node.
Should LIN schedules start at boot? Or paus until user command.
Path to .ldf
file used for schedules.
Path to .ldf
file used for tables. TODO
Sets the device type to LIN
Flexray 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 address accepted by the OS. Eg. Ipv4: "127.0.0.1"
.
Sets the device type to Flexray
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.
Name of frame to exclude