Skip to main content

Describing the platform

The platform describes which ECUs and services that exist and how they communicate. In RemotiveTopology you can describe your platform in a number of different ways:

  • An ARXML ECU extract
  • An ARXML system description (contains all ECUs)
  • A DBC file describing a CAN channel and all ECUs on that channel. Notice that DBC does not include which channel it is describing!
  • RemotiveTopology platform.yaml to add addional information or combining other files

Showing a platform​

The easiest way to understand what a file contains is to

$ remotive-topology show topology <file>

This will show the platform contents as platform.yaml and includes all channels and ECUs described by the file.

Combining platforms​

Using ARXML​

ARXML contains channels, ECUs and how the ECUs are connected to the channels. Simply add ARXML as includes:

schema: remotive-topology-platform:0.2
includes: 
 - ../databases/my-ecu-a.arxml
 - ../databases/my-ecu-b.arxml

Notice that all included files must be compatible! This means that the referenced ECUs and channels must have the same names and settings. Ensure that the files are from the same version.

Using DBC​

DBC only contains ECUs and does not contain the channel name. This means that you must specify what channel should use the DBC using the database field:

schema: remotive-topology-platform:0.2
channels:
  DriverCan0:
    type: can
    database: ../databases/driver_can.dbc
    can_physical_channel_name: DriverCan0

This will automatically add the ECUs that are part of the DBC and connect these to the channel, that is:

$ remotive-topology show topology topology/simple.platform.yaml
---
channels:
  DriverCan0:
    can_physical_channel_name: DriverCan0
    database: .../databases/driver_can.dbc
    type: can
ecus:
  BCM:
    channels:
      DriverCan0:
        database: .../databases/driver_can.dbc
  SCCM:
    channels:
      DriverCan0:
        database: .../databases/driver_can.dbc
schema: remotive-topology-platform:0.2

Notice how database is also set for the ECU channels. The reason is that these ECUs will use that database to decode signals. Sometimes it is useful to only allow an ECU a partial view of the channel. To do this you can override the ECU channel database.

Using platform.yaml​

A key principle in RemotiveTopology is modularity. This means that combining platform subsystems is very easy using includes:

schema: remotive-topology-platform:0.2
includes: 
 - ./lighting.platform.yaml
 - ./climate.platform.yaml
 - ./driver.platform.yaml