> 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/hypersim/configure-ios/communication-protocol-ios/can/configure-can/import-autosar-xml-files.md).

# Import AUTOSAR XML files

### Launch CANdb Importer

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

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

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

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-6a0db57f4acff9e23cf9a7066045a424597d953f%2Fdr-hyp-can-import-btn.jpg?alt=media" alt=""><figcaption></figcaption></figure>

### Select file type

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

### Select buses

After loading the ARXML file, all CAN buses defined in the file are listed.

* Enable the buses required for the simulation.
* For each selected bus, a corresponding internal configuration (DBC‑like) is generated.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-a315a61bf602c0a66029c0a0e4db6a23eb46fdb0%2Fdr-hyp-can-arxml-buses.jpg?alt=media" alt="" width="480"><figcaption></figcaption></figure>

### Configure nodes

For each selected bus:

* Select a bus from the dropdown list to display its nodes.
* 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://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-a5da3682998e1c65bc9cd4ba73a42c8e8071e7e3%2Fdr-hyp-can-arxml-buses-nodes.jpg?alt=media" alt="" width="480"><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 displayed and 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 to be received from physical nodes are enabled by default but may be disabled if not needed.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-8925639c9fdffb6c8cbca9da786cb1717a2b8799%2Fdr-hyp-can-arxml-msg.jpg?alt=media" alt=""><figcaption></figcaption></figure>

### Finish the import

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

### Review the CAN configuration

The [configuration view](https://www.opal-rt.com/docs/hypersim/configure-ios/communication-protocol-ios/can/configure-can.md#configure-the-general-settings) displays all **simulated nodes**, **enabled messages**, **associated signals**, and **corresponding buses**.


---

# 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/hypersim/configure-ios/communication-protocol-ios/can/configure-can/import-autosar-xml-files.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.
