Skip to main content

Error codes

Error codes​

This documnent describes error codes and how to resolve them.

E001: name is required​

When instantiating a topology you need to specify a name. You have two options:

  1. add --name <name> to your command line
  2. add a name attribute in the instance.yaml, eg:
schema: remotive-topology-instance:0.2
name: <name>

E002: schema is required​

Each instance.yaml must have the schema name and version, eg

schema: remotive-topology-instance:0.2

E003: major version mismatch​

The schema major version is not supported by the RemotiveTopology CLI you are using. You need to use an older or newer version of the CLI. Notice that all included instance.yaml files must use the same major version.

E004: minor version mismatch​

The schema minor version is not supported by the RemotiveTopology CLI you are using. Upgrade RemotiveTopology CLI.

E005: Invalid schema​

Schema version must be specified using remotive-topology-instance:<major>.<minor> format.

E010: Undefined ECU​

The ECU is missing from the platform. This can be because a platform file is missing or because of a spelling error. Ensure that you have added the proper signal databases or ECU extracts. For example use remotive-topology show topology ecu-extract.arxml to verify that the ECU has the name you are expecting.

E011: Undefined channel​

The channel is missing from the platform. Ensure that the spelling is correct. Sometimes channels are not defined in ARXML and must be added manually, for example by adding a DBC file:

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

E012: Undefined ECU channel​

The ECU is not connected to the channel. Ensure the spelling is correct. To manually add an ECU channel you can add the following:

schema: remotive-topology-platform:0.2
ecus:
    BCM:
      channels:
        DriverCan0:

This adds the DriverCan0 to the BCM.

E013: Invalid EthernetChannel​

An EthernetChannel must include subnet.

schema: remotive-topology-platform:0.2
channels:
  ETH:
    type: ethernet
    subnet: 10.1.1.0/24

E014: can_over_udp must be empty or contain subnet, target_host, and port​

When using udp emulation for CAN you can optionally specify details about the UDP broadcast. If you specify subnet, target_host or port you must specify all three.

Option 1: Use defaults (automatically assigns free subnet and port)

schema: remotive-topology-instance:0.2

channels:
  DriverCan0:
    type: can-over-udp

Option 2: Explicit configuration

schema: remotive-topology-instance:0.2

channels:
  DriverCan0:
    type: can-over-udp
    port: 14000
    subnet: 10.19.1.0/24
    target_host: 230.0.0.1

The explicit configuration might be useful when adding other tools such as wireshark.

E015: Failed to instantiate channel​

The instance is missing information how to instantiate the channel. Typically this happens for CAN as you need to decide if you want to use SocketCAN or emulation over UDP. See E014 above.

E020: Failed to load​

This typically happens because the file is correctly formatted or corrupt.