---
title: "Mocks"
description: "Mock an ECU in RemotiveTopology so it sends its cyclic signals on its channels, and combine mocks with behavioral models for larger ECUs."
source: https://developer.remotivelabs.com/docs/remotive-topology/usage/ecus/mocks
last_updated: 2026-11-20
---

# Mocks

A mock provides a restbus simulation of the ECU. The mock sends the frames that the ECU sends according to the signal databases, at their cycle times, so the bus looks as it does in the vehicle. Mocking several ECUs around a device gives you a restbus for the rest of the vehicle, so you can test the device in a realistic bus environment.

A mock starts out by sending the default value of all cyclic signals where the ECU is the sender. Your test cases, or other code, can then control the values to simulate different scenarios, see [Controlling mocks](https://developer.remotivelabs.com/docs/remotive-topology/usage/test.md#controlling-mocks). If the code that controls a mock gets complicated, write a [behavioral model](https://developer.remotivelabs.com/docs/remotive-topology/usage/ecus/behavioral-models.md) instead.

By default a mock is created for all channels that the ECU is connected to:

```yaml
ecus:
  FLCM:
    mock: {}
```

You can also specify what channels you want to mock. This is useful when you want to exclude certain channels from the simulated environment, for example to use less CPU and memory.

```yaml
ecus:
  FLCM:
    mock:
      channels:
        BodyCan:
```

Mock ECUs are only needed for ECUs that are sending signals. If you have an ECU that's only receiving signals, then you shouldn't create a mock. To make sure the ECU isn't instantiated you can use `external`:

```yaml
ecus:
  FLCM:
    external: {}
```
