> 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/requirements-features-and-limitations.md).

# Requirements, Features & Limitations

## Software requirements

The **CAN** driver is included by default with <code class="expression">space.vars.Software</code> and does not require any additional installation.

## Hardware requirements

CAN communication is supported through [**OP3411**](https://www.opal-rt.com/docs/pcie-cards-and-connector-kits/pcie-cards/op3411-kvaser-pcie-can-bus-kits.md) **Kvaser PCIe CAN interface cards**, with the appropriate model chosen based on the simulator platform and the required number of CAN channels.

To verify whether the PCIe card is already included in your system, refer to your **System Description Document**. If the card is not included, consult the **Hardware Modularity** section of your hardware platform documentation to identify the compatible Kvaser PCIe CAN cards available for your platform.

## License requirements

### Simulator license

[Verify that an active RT-LAB license](https://www.opal-rt.com/docs/rt-lab/licensing-reference/simulator-license.md) with the following features is installed on the simulator to run simulations using the CAN protocol:

| Feature Name     | Required Status     | Description                      |
| ---------------- | ------------------- | -------------------------------- |
| CAN              | enabled             | Enables CAN                      |
| CAN\_CHANNEL\_NB | 2 enabled (or more) | Number of activated CAN channels |

### Workstation license

A workstation license is **not** required to run simulations in <code class="expression">space.vars.Software</code> using the CAN protocol.

## Supported features

* Compliant with **ISO 11898‑1** and **ISO 11898‑2** standards.
* **CAN FD** is supported and can be enabled on a **per‑channel** basis.
* The number of active CAN channels is **configurable**, subject to hardware limitations.
* The **bit rate** of each CAN channel is individually configurable.
* **Silent mode** operation is supported.
* Message transmission and reception can be **enabled or disabled via the console** (cyclic transmissions are excluded).
* Transmission and reception buffers can be **cleared via the console**.
* Messages can be transmitted using a **fixed or dynamically assigned identifier**.
* Messages can be received using a **specific identifier filter** or in **promiscuous mode**.
* **Endianness** for each signal can be configured as **Intel (little‑endian)** or **Motorola (big‑endian)**.
* Messages support **1‑bit signal granularity**.
* A **gain and offset** can be applied to each signal for both transmission and reception.
* **Per‑channel statistics** can be monitored.
* **Transmission flags** are configurable for each transmitted message.
* **Reception flags** can be monitored for each received message.
* The **timestamp** of each received message can be monitored.
* **Simple signal multiplexing** is supported for both message transmission and reception.
* **DBC files with messages transmitted by multiple nodes** are supported.

## Limitations

* **Vector\_XXX nodes** can be imported via the DBC importer **but do not participate in CAN communication**.
* Only ISO 11898‑1 (CAN protocol) and ISO 11898‑2 (high‑speed CAN physical layer) are supported.
* A maximum of **4 CAN channels per Kvaser card** is supported on all platforms.
* Supported Classical CAN bit rates are **50, 62, 83, 100, 125, 250, 500, and 1000 kbps**.\
  CAN FD is supported with data phase bit rates of **up to 8 Mbps**.
* The maximum number of CAN frames that can be received within a single simulation time step is **20**, as defined by the *Buffer size* parameter.
* Although CAN data may use 64‑bit unsigned integers (`UINT64`), the maximum representable value is limited to the maximum value of a `double`, since the RT‑LAB user interface internally interprets and displays all data using double‑precision floating‑point format.
* Enabling the **Bus Load** feature introduces additional processing overhead and may reduce CAN communication performance.


---

# 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/requirements-features-and-limitations.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.
