LIN example

Connect a secondary USB to ETH adapter to the host. Here you can connect a single LIN transceiver box alternatively a switch with a number of LIN transceivers. Each LIN transceiver is identified and configured according to its unique device_identifier.

This ID needs to reflect and be present in interfaces.json. The following configuration shows two LIN devices, 8 and 7. Note that 8 has been configured to operate as master, whereas 7 operates as a slave.

Each LIN transceiver needs a unique set of target_port and server port, which can be selected freely. Once the transceivers get powered, their configurations will be distributed.

{
  "chains": [
    {
      "namespace": "ecu_A",
      "type": "lin",
      "config": {
        "device_identifier": 8,
        "server_port": 2014,
        "target_port": 2013
      },
      "node_mode": "master",
      "database": "ldf/test.ldf",
      "schedule_file": "ldf/test.ldf",
      "schedule_table_name": "DEVMLIN01Schedule01",
      "schedule_autostart": true
    },
    {
      "namespace": "ecu_B",
      "type": "lin",
      "config": {
        "device_identifier": 7,
        "server_port": 2015,
        "target_port": 2016
      },
      "node_mode": "slave",
      "database": "ldf/test.ldf"
    }
  ]
}

info

The prebuilt image will host a DHCP server on the added adapter. LIN transceivers and the RemotiveBroker need to reside on the same subnet. Other custom topologies are supported and sometimes preferred.