> For the complete documentation index, see [llms.txt](https://www.opal-rt.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/can/configure-can/import-classical-can-database-files-dbc.md).

# Import Classical CAN database files (DBC)

### Launch CANdb Importer

From the **CAN I/O Interface**, click **CANdb Importer** to launch the import wizard.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-542f1491496a1c9db38fe0122e101995d986a9d9%2FDR-rtlab-can-importer.png?alt=media" alt=""><figcaption></figcaption></figure>

### Select file type

Select **DBC** as the CANdb file type in the importer wizard and browse for the file.

### Create a bus

Click **Create new** and enter a name for the CAN bus.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-9f8c14312a269c99380fdc53fcafd068ac45db3a%2FDR-rtlab-can-importer2.png?alt=media" alt=""><figcaption></figcaption></figure>

### Select DBC file

Choose the DBC file using the file browser. The file is now linked to the newly created bus. A dialog is displayed if parsing errors are detected.

Fix all DBC file errors before moving forward.

### Configure nodes

After a successful import:

* Enable the nodes to include in the simulation.
* Assign each node a **type**:
  * **Physical:** Represents a real ECU on the CAN network.
  * **Simulated:** Represented by the simulator and able to exchange messages with physical nodes. **At least one simulated node must be enabled to proceed.**

{% hint style="info" %}
Communication between simulated nodes is only possible if they are physically connected (e.g., loopback).
{% endhint %}

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-83eae190b6b528b45d953e61d21232debab231ac%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
The **Physical** and **Simulated** buttons allow setting all nodes to the same type.\
Only **Simulated** nodes appear in the final configuration.
{% endhint %}

### Select messages

Messages are grouped by node:

* Messages from physical nodes are enabled by default and cannot be modified.
* Messages from simulated nodes can be enabled or disabled.
* Messages expected from physical nodes are enabled by default.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-8ff38907af2a8beaa5b2a06acc7c18d89b9055e1%2FDR-rtlab-can-importer4.png?alt=media" alt=""><figcaption></figcaption></figure>

{% endif% }

### Finish the import

Click **Finish** to close the wizard and return to the CAN configuration.

{% hint style="info" %}
The importer supports DBC files where a message has **multiple transmitting nodes**.
{% endhint %}

### Review the CAN configuration

The [configuration view](https://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/can/configure-can.md#configure-the-general-settings) displays all **simulated nodes**, **enabled messages**, **associated signals**, and **corresponding buses**. If multiple buses are created, they can be accessed using the **Select bus** button. If the result is not as expected, verify the following:

* **Nodes:** The CAN database file defines nodes correctly (e.g., a valid `BU_` line in DBC files).
* **Messages**
  * The messages you expect to see are **enabled**.
  * Messages belonging to **physical nodes** are enabled by default and cannot be modified.
  * Messages expected to be received from physical nodes are enabled as needed.
* **Signals**
  * The parent message of each signal is enabled.
  * Signals follow supported formats (including multiplexed, signed/unsigned, and Intel/Motorola definitions).
* **Buses**
  * The correct bus is selected when multiple buses are present.
  * The bus containing the imported configuration is enabled.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/can/configure-can/import-classical-can-database-files-dbc.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
