---
title: "RemotiveTopology error codes"
description: "What each RemotiveTopology error code means (E001 and up) and how to fix it, from missing names and schema mismatches to undefined ECUs and channels."
source: https://developer.remotivelabs.com/docs/remotive-topology/reference/errors
last_updated: 2026-11-20
---

# RemotiveTopology error codes

## Error codes

This document 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`:

```yaml
schema: remotive-topology-instance:0.18
name: <name>
```

### E002: Schema is required

RemotiveTopology no longer reports this code. It's listed for users of older versions.

Each `instance.yaml` must have the schema name and version:

```yaml
schema: remotive-topology-instance:0.18
```

### E003: Major version mismatch

The schema major version isn't 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 isn't supported by the RemotiveTopology CLI you are using. Upgrade RemotiveTopology CLI.

### E005: Invalid schema

Schema version must be specified using `<type>:<major>.<minor>` format. Correct types are:

- `remotive-recording-mapping`
- `remotive-recording-session`
- `remotive-signal-database`
- `remotive-topology-instance`
- `remotive-topology-platform`

A common mistake is how to include platform in an instance. This is wrong:

```yaml
schema: remotive-topology-instance:0.18

includes:
  - ./my.platform.yaml
```

The correct way to include a platform in an instance:

```yaml
schema: remotive-topology-instance:0.18

platform:
  includes:
    - ./my.platform.yaml
```

### E006: `settings.remotivebroker.version` is required

RemotiveTopology no longer reports this code. It's listed for users of older versions.

To instantiate the topology a specific version of RemotiveBroker is needed. To get consistent behavior setting a fixed version is recommended.

### 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 platform 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 aren't defined in ARXML and must be added manually, for example by adding a DBC file:

```yaml
schema: remotive-topology-platform:0.18
channels:
  DriverCan0:
    type: can
    database: ../databases/driver_can.dbc
```

### E012: Undefined ECU channel

The ECU isn't connected to the channel according to the platform. Ensure the spelling is correct and that the correct databases have been included in the platform. To manually add an ECU channel you can add the following:

```yaml
schema: remotive-topology-platform:0.18
ecus:
  BCM:
    channels:
      DriverCan0:
```

This adds the DriverCan0 to the `BCM`.

### E013: Invalid Ethernet channel

An Ethernet channel must include subnet.

```yaml
schema: remotive-topology-platform:0.18
channels:
  ETH:
    type: ethernet
    subnet: 10.1.1.0/24
```

### E014: CAN UDP driver 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)

```yaml
schema: remotive-topology-instance:0.18

channels:
  DriverCan0:
    type: can
    driver:
      type: upd
```

Option 2: explicit configuration

```yaml
schema: remotive-topology-instance:0.18

channels:
  DriverCan0:
    type: can
    driver:
      type: upd
      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 map ecu to channel

RemotiveTopology couldn't determine how the ECU is connected to the channel. This can happen because there is missing information in the platform, for example for ethernet channels the platform must specify the host IP of the ECU:

```
ecus:
  MyECU:
    channels:
      Eth:
        config:
          type: ethernet
          host: 10.1.4.50
```

### E016: Invalid device name. Device name must be 1-15 lowercase alphanumeric characters or dashes

This error occurs when a network device name that the topology creates doesn't follow the required rules: the `device_name` of a `dockercan` driver, the `name` of an Ethernet `bridge` driver, or the `device` of an Ethernet `remotivebus` driver. The name must be 1–15 characters long and consist only of lowercase alphanumeric characters and dashes (`a-z`, `0-9`, and `-`).

To resolve this issue, specify a valid name in your instance configuration:

```yaml
schema: remotive-topology-instance:0.18

channels:
  DriverCan0:
    type: can
    driver:
      type: dockercan
      device_name: drivercan0
```

### E017: Invalid device name. Peer name must be 1-14 lowercase alphanumeric characters or dashes

This error occurs when the `peer` of a `dockercan` driver doesn't follow the required rules. The topology appends `0` to the peer name to name the device, so the peer name must be 1–14 characters long and consist only of lowercase alphanumeric characters and dashes (`a-z`, `0-9`, and `-`).

To resolve this issue, specify a valid `peer` in your instance configuration:

```yaml
schema: remotive-topology-instance:0.18

channels:
  DriverCan0:
    type: can
    driver:
      type: dockercan
      device_name: drivercan0
      peer: drivercanpeer
```

### E018: `device_name` is required for driver

Channel instance driver (e.g. `macvlan`, `ipvlan`) requires a `device_name` which is used to connect to a physical device.

### E019: Failed to instantiate channel

RemotiveTopology couldn't determine how to instantiate the channel. Try adding an instance channel.

### E020: Failed to load

This typically happens because the file is incorrectly formatted, corrupt, or missing.

### E021: Failed to copy database

Signal databases must be copied to be part of the generated output. This error happens when a signal database couldn't be copied. Make sure:

- the path to the signal database is correct
- the file system permissions on the signal database is correct
- the file system permissions on output folder is correct

When running `remotive-topology` using docker, make sure that all files exist in a sub-folder of your current working directory.

### E022: Failed to parse file

This can happen when there is an error in a topology instance or platform file. The error message includes which field and specifically what failed when parsing the file. Having json schema validation setup in your editor makes it easier to find this type of errors. A common mistake is to forget the `type` field when creating a channel or channel `config`.

### E023: Trying to include channel database as platform

This happens for trying to include DBC, LDF, or Fibex as platform include. These files doesn't include all necessary information that describe a platform and should instead be added as channel database for the correct channel:

```yaml
channels:
  DriverCan:
    type: can
    database: ../databases/driver_can.dbc
```

### E024: Trying to access file outside of workspace

Typically this happens when running without an explicit workspace. When initializing your workspace ensure that it's initialized at the root of your project, for example:

```bash
cd my_project
remotive topology workspace init
```

If the workspace isn't initialized and a file is referring to another file outside of the current workspace directory, for example when an `instance.yaml` or `platform.yaml` include a file in a different directory. Typically the reason why this happens is that you are running the command from the wrong directory. For example given the following file structure:

```
./my_project/
├── instances
│   └── main.instance.yaml
└── platform
    ├── databases
    │   └── something.dbc
    └── main.platform.yaml
```

This error is expected if you perform:

```bash
cd my_project/instances
remotive topology show instance ./main.instance.yaml
```

The reason is that `main.instance.yaml` includes `../platform/main.platform.yaml`. To make this work, you can run from the root of the project:

```bash
cd my_project
remotive topology show instance ./instances/main.instance.yaml
```

However, the best solution is to initialize the workspace!

### E025: Invalid host device name. Device name must be 1-15 lowercase alphanumeric characters or dashes

This error occurs when using the `remotivebus` driver, but the `host_device` doesn't follow the required rules. The `host_device` must be 1–15 characters long and consist only of lowercase alphanumeric characters and dashes (`a-z`, `0-9`, and `-`).

To resolve this issue, specify a valid `host_device` in your instance configuration:

```yaml
schema: remotive-topology-instance:0.18

channels:
  DriverCan0:
    type: can
    driver:
      type: remotivebus
      config:
        type: can
        device: drivercan
        host_device: host-drivercan
```

### E026: Invalid device name. Device name must be 1-15 lowercase alphanumeric characters or dashes

This error occurs when using the `remotivebus` driver, but the `device` name doesn't follow the required rules. The `device` name must be 1–15 characters long and consist only of lowercase alphanumeric characters and dashes (`a-z`, `0-9`, and `-`).

Note that the default device name is derived from the channel name. For channels with names longer than 15 characters, you must explicitly specify the device name.

To resolve this issue, specify a valid `device` name in your instance configuration:

```yaml
schema: remotive-topology-instance:0.18

channels:
  DriverCan0:
    type: can
    driver:
      type: remotivebus
      config:
        type: can
        device: drivercan
        host_device: host-drivercan
```

### E027: Invalid file format

The database file doesn't contain what its file extension says, for example an `.arxml` file without any AUTOSAR packages, an `.xml` Fibex file that describes no ECU, channel or service, or a `.dbc` or `.ldf` file that can't be read as one. Check that the file is a complete database of the format its extension names, and that it wasn't truncated or exported in another format.

### E028: Invalid `host_bridge_device` name. Device name must be 1-15 lowercase alphanumeric characters or dashes

This error occurs when using the `remotivebus` driver, but the `host_bridge_device` name doesn't follow the required rules. The `host_bridge_device` name must be 1–15 characters long and consist only of lowercase alphanumeric characters and dashes (`a-z`, `0-9`, and `-`).

Note that the default device name is derived from the cluster name. For clusters with names longer than 15 characters, you must explicitly specify the device name.

To resolve this issue, specify a valid `host_bridge_device` name in your instance configuration:

```yaml
schema: remotive-topology-instance:0.18

channels:
  vlan10:
    type: ethernet
    driver:
      type: remotivebus
      host_bridge_device: host-network
```

### E029: Invalid `host_physical_device` name. Device name must be 1-15 lowercase alphanumeric characters or dashes

This error occurs when using the `remotivebus` driver, but the `host_physical_device` name doesn't follow the required rules. The `host_physical_device` name must be 1–15 characters long and consist only of lowercase alphanumeric characters and dashes (`a-z`, `0-9`, and `-`).

To resolve this issue, specify a valid `host_physical_devices` name in your instance configuration:

```yaml
schema: remotive-topology-instance:0.18

channels:
  vlan10:
    type: ethernet
    driver:
      type: remotivebus
      host_physical_devices: [eth0]
```

### E030: SOME/IP service instance not found

This happens when `provided_service_instances` or `consumed_service_instances` is referring to an instance that's not defined. Make sure the service is defined in the same channel as it's being used.

### E031: SOME/IP service provider endpoint not found

This happens when trying to consume a service instance that has no `provided_service_instances` defined.

### E032: SOME/IP endpoint type mismatch

This happens when trying to consume a SOME/IP service with the incorrect protocol. For example if the service instance is provided over TCP it must be consumed over TCP or vice versa for UDP.

### E033: SOME/IP service instance `service_id` missing

This typically happens when manually configuring a SOME/IP service instance and you forget to set the `service_id`.

### E034: SOME/IP service instance `instance_id` missing

This typically happens when manually configuring a SOME/IP service instance and you forget to set the `instance_id`.

### E035: SOME/IP service instance `version_major` missing

This typically happens when manually configuring a SOME/IP service instance and you forget to set the `version_major`. This can also happen when ARXML or Fibex is missing `version_major` which probably means that it's not intended to be instantiated.

### E036: SOME/IP service instance `version_minor` missing

This typically happens when manually configuring a SOME/IP service instance and you forget to set the `version_minor`. This can also happen when ARXML or Fibex is missing `version_minor` which probably means that it's not intended to be instantiated.

### E037: Undefined socket on tap channel

This typically happens when configuring a tap channel with `mode: "selection"` and listing a socket name under sockets that doesn't exist in the channel's platform definition. Check that every socket name in the sockets list matches a socket defined in the platform configuration for that channel.

### E038: tap_config with mode 'selection' requires at least one socket

This typically happens when configuring a tap channel with `mode: "selection"` but forgetting to add at least one entry to the sockets list. In selection mode the tap captures traffic only for the explicitly listed sockets, so an empty list is invalid in this mode.

### E040: Socket endpoint not found

This happens when trying to instantiate an ethernet channel which is referring to a application endpoint that doesn't exist in the platform.

### E041: Network endpoint not found

This happens when trying to instantiate an ethernet channel which is referring to a network endpoint that doesn't exist in the platform.

### E042: ECU channel host doesn't match network endpoint

This happens when Ethernet ECU channel has a host configured that doesn't match one of the provided network endpoints. Avoid specifying `host` and instead rely on `provided_endpoints`. This can also occur if the `provided_endpoints` have different IP addresses which means they shouldn't be provided by the same ECU on the same channel.

### E043: ECU socket instance not on provided endpoint

This happens when ECU tries to instantiate a socket that isn't available on an endpoint provided by the ECU. Typically this is a problem in the instance and not in platform. For example in this case the instance tries to instantiate `app2` on ecu `a`, but it should probably be `app1` instead.

```yaml
platform:
  channels:
    ETH:
      type: ethernet
      endpoints:
        host1:
          sockets:
            app1:
              port: 30509
              type: udp
        host2:
          sockets:
            app2:
              port: 2001
              type: udp

  ecus:
    a:
      channels:
        ETH:
          config:
            type: ethernet
            provided_endpoints:
              - host1
ecus:
  a:
    channels:
      ETH:
        config:
          type: ethernet
          sockets:
            - app2
```

### E044: Ethernet channel with RemotiveBus driver doesn't specify VLAN id

This happens when the `remotivebus` driver is specified for an Ethernet channel that doesn't have a VLAN id specified for it. Set the correct VLAN id for the channel in the platform or use the default `bridge` driver instead of `remotivebus` if the VLAN tag isn't required.

### E050: model name must be lowercase

Behavioral models must use lowercase. This is because of a limitation in Docker.

### E051: No container specified for model

Behavioral models must have a container.

```
ecus:
  BCM:
    models:
      bcm:
        type: container
        container:
          build:
            dockerfile: ../special-python-runner.dockerfile
```

It's quite common to have the same dependencies for all python models and in this case you can specify a default dockerfile:

```yaml
settings:
  docker:
    python:
      build:
        dockerfile: ../python-runner.dockerfile
```

### E052: No container specified for mocks

RemotiveTopology no longer reports this code. It's listed for users of older versions.

** Deprecated since 0.7.0 **

Currently mocks must have a container configuration:

```yaml
settings:
  docker:
    mock:
      build:
        dockerfile: ../mock.dockerfile
```

### E053: Either dockerfile or image must be specified

When defining a container you can either use an existing image or use a dockerfile to build your custom container. In your dockerfile you can specify which base image you want to use.

Notice that this applies to all container configurations, i.e. both for mocks, models, ecus, and generic containers.

### E054: Container build `args` can only be used with dockerfile

The container build property `args` represents the build arguments which are available when building from a dockerfile. Don't specify `args` when only using `image`. Instead use `environment` if you want to specify environment variables that are available to the container.

### E055: Target can only be used with dockerfile

The container build property `target` decides which stage in a multi-stage dockerfile to use when building from a dockerfile. Don't specify `target` when only using `image`.

### E056: Dockerfile must be inside the context

When specifying both build context and dockerfile, then the dockerfile must be inside that context.

### E057: Both context and dockerfile missing

When specifying container build, then context and/or dockerfile must be specified.

### E060: Multiple lin `auto_config_boot_server` servers configured

RemotiveTopology no longer reports this code. It's listed for users of older versions.

When connecting RemotiveLabs LIN hardware, all LIN channels for a single ECU (RemotiveBroker) must use the same port number configured for `auto_config_boot_server`. To fix this issue check what other LIN channels are configured for the ECU and make sure they all use the same `auto_config_boot_server` port number. Remember that each ECU needs to use its own, unique port. Try running:

```sh
remotive topology show instance your-instance-file.instance.yaml
```

### E061: Lin channel has no master ECU configured

Verify that the LDF file includes a master ECU.

### E062: Lin has no `schedule_table` specified

The instance contains a LIN master, but it has no LIN schedule specified.

### E070: Access denied

The subscription server reported that it couldn't verify access to the RemotiveTopology feature in RemotiveCloud. Please verify that

- You have an active token with the RemotiveCloud server.
- Your organization has an active subscription for the RemotiveTopology feature.

Information on how to use the RemotiveCLI for access tokens and subscription can be found in [the RemotiveCLI help pages](https://developer.remotivelabs.com/docs/remotive-cli.md).

### E071: Access control failed

The client couldn't access the subscription server to check if the topology feature is available. Please verify that:

- There is working internet connection to https://cloud.remotivelabs.com
- You have the latest versions of the RemotiveCLI and the RemotiveTopology CLI.

If this is happening while running the topology, it could be because it was generated with an older version of the RemotiveTopology CLI.
Try to rebuild it with `remotive topology build ...`.

### E072: Analytics consent is required

You need to consent to analytics collection to use RemotiveTopology. If you have a topology feature subscription, it's included in the terms. If you're using RemotiveTopology anonymously, you're prompted when running the command the first time.

### E080: Recording session missing platform

To playback a recording session you must include a mapping to a platform. Normally the mapping is in a separate file:

```yaml
schema: remotive-recording-session:0.2

mapping:
  includes:
    - ./myvehicle-nnn.mapping.yaml
```

`myvehicle-nnn.mapping.yaml`:

```yaml
schema: remotive-recording-mapping:0.1

platform:
  - ../myvehicle.platform.yaml
```

But you can also keep the mapping inside the recording session:

```yaml
schema: remotive-recording-session:0.2

mapping:
  platform:
    - ../myvehicle.platform.yaml
```

### E081: Playback not supported for channel

First, ensure that you are using the latest version of RemotiveTopology! Workaround: exclude the channel from your platform, i.e. by creating a sub-platform.

Contact support@remotivelabs.com if you need playback on unsupported channel types!

### E082: File is missing required field

Recording session file has a missing field, e.g. the name field of a video can be easy to forget.

```yaml
files:
  - type: video
    location: front.mp4
    name: front
```

### E083: File has field with duplicate value

Typically occurs when recording session video name isn't unique, e.g. here both videos have the name "front":

```yaml
files:
  - type: video
    location: front.mp4
    name: front
  - type: video
    location: windscreen.mp4
    name: front
```

### E084: Ethernet channel with RemotiveBus is trying to connect a physical device to multiple networks

This happens when you specify a physical device on multiple different bridge networks with the `remotivebus` driver. A physical device can be attached to multiple networks, but only when they share the same `host_bridge_device`.

### E085: Multiple channels resolve to the same device name within the container

Each `remotivebus` channel creates a network device inside the container, named by the channel's `device`, or by a name derived from the channel name when `device` isn't set. This error occurs when two or more channels of the same container would create a device with the same name. The error lists the device name and the channels.

To resolve this issue, give each channel its own `device` name in your instance configuration:

```yaml
schema: remotive-topology-instance:0.18

channels:
  BodyCan0:
    type: can
    driver:
      type: remotivebus
      config:
        type: can
        device: bodycan0
  ChassisCan0:
    type: can
    driver:
      type: remotivebus
      config:
        type: can
        device: chassiscan0
```

### E086: Failed to apply `alias_for`

`alias_for` optimization is currently not supported for ECUs with Ethernet channels. Remove `alias_for` attribute from the ECU with Ethernet channels.

### E090: Trying to include topology instance as platform

A `platform.yaml` includes an `instance.yaml`. A platform can only include other platform files; an instance includes its platform, not the other way around:

```yaml
schema: remotive-topology-instance:0.18

includes:
  - ../platform/main.platform.yaml
```

### E091: Invalid meta database

A `.dbc` or `.ldf` signal database is paired with a meta database when a file with the same name plus `.meta.json` sits next to it, for example `my_db.dbc` and `my_db.dbc.meta.json`. The meta database adds E2E, SecOC, signal groups and the unused-bit pattern, see the [meta database json schema](https://developer.remotivelabs.com/docs/remotive-broker/apis.md#remotivebroker-meta-database-json-schema).

This error means the paired file exists but can't be used. The reason tells you which of these it's:

- the file can't be read
- the file isn't valid json
- `formatVersion` isn't the supported version e.g. (`0.1.0`)
- a field has the wrong shape, e.g. `frames` isn't an object or `groups` isn't a list
- a field has an invalid value, e.g. a `dataId` outside 0..65535, a group `range` with `size` 0, or SecOC lengths that don't fit inside the group

Fix the meta database rather than removing it: without it the database still loads, but the frames it protects are encoded and decoded without E2E or SecOC.

### E092: ECUs on channel use conflicting signal databases

This error occurs when ECUs on the same channel use different signal databases, see [using DBC in a platform](https://developer.remotivelabs.com/docs/remotive-topology/concepts/platform.md#using-dbc). To show everything that's on a channel in one place, for example all signals of the channel in [RemotiveStudio](https://developer.remotivelabs.com/docs/remotive-studio/topology.md), RemotiveTopology merges the ECU databases into a single view of the channel. This works when the databases agree, or when one is a subset of another, but fails when they define the same frame, signal, or field differently.

The error lists every channel where the databases conflict, and the databases its ECUs use. Under `conflicts`, each frame, signal, or field that differs is shown with the two values, for example:

```
E092: ECUs on channel use conflicting signal databases
  DriverCan0:
    databases=./databases/bcm.dbc ./databases/sccm.dbc
    conflicts:
      frames.MY_FRAME.payload_size=values differ: 40 and 64
      frames.OTHER_FRAME.signals.OtherSignal.length=values differ: 8 and 16
```

Here two ECUs on `DriverCan0` use the databases `bcm.dbc` and `sccm.dbc`, which give the frame `MY_FRAME` different payload sizes and the signal `OtherSignal` different lengths. This typically happens when the ECUs use different versions of the same database. Fix the databases so they agree.

If a channel shows `reason` instead of `conflicts`, its databases couldn't be combined for another reason, and `reason` holds the message.

### E093: ECU channel database missing

Check channel definition or ecu channel definition. Normally every channel should have a signal database.

In the rare scenario when you don't have or want to use a signal database you still need to specify a signal database for the TopologyBroker:

```yaml
schema: remotive-topology-instance:0.18

settings:
  topology_broker:
    channels:
      bodycan:
        database: ./empty.dbc
```

### E094: Channels have overlapping subnets

This typically happens when two or more ethernet channels are in reality the same. Notice that RemotiveTopology is case sensitive, e.g. `eth` and `ETH` are considered different channels.

### E095: Multiple channels use the same bridge device name

This typically happens when two or more ethernet channels are in reality the same. Notice that RemotiveTopology is case sensitive, e.g. `eth` and `ETH` are considered different channels.

### E096: Invalid subnet

This typically happens then the subnet includes host bits, for example `10.0.2.16/24` should be `10.0.2.0/24`.

## Unexpected errors

For the following errors or other unexpected problems you can contact support@remotivelabs.com for help.

### E900: Error when building broker config

This is an unexpected error that happened when generating configuration for RemotiveBroker. Verify the platform and instance configuration for the affected ECU.

### E901: Failed to generate ecu

This is an unexpected error that happened when generating docker compose configuration for a particular ECU. Verify the platform and instance configuration for the affected ECU.

### E902: Failed to generate channel

This is an unexpected error that happened when generating docker compose configuration for a particular channel. Verify the platform and instance configuration for the affected channel.

### E903: Failed to generate TopologyBroker config

This is an unexpected error that happened when generating configuration for the TopologyBroker. Verify the platform and instance configuration for the affected channel.
