> 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/connect-the-hardware.md).

# Connect the Hardware

## Connect devices using a CAN bus

CAN communication operates over a **shared CAN bus** using a differential two‑wire physical layer (CAN\_H and CAN\_L). To establish communication between CAN nodes (ECUs, controllers, simulators, or gateways) and simulated CAN nodes in the Simulink model, connect all devices and the simulator **OP3411** **Kvaser PCIe CAN card channels connector** to the same CAN bus using **standard CAN cabling**, ensuring proper bus topology and termination.

**One OP3411** **Kvaser PCIe CAN card channel connector can handle one or more simulated CAN nodes.**

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

## Configure bus wiring and termination

For reliable CAN communication, the physical layer must follow standard CAN wiring rules:

* All devices must be connected to the **same CAN bus segment** (linear bus topology).
* The bus must be terminated with **120 Ω resistors at both physical ends** of the CAN bus.
* Stubs should be kept as short as possible to minimize signal reflections.
* CAN\_H and CAN\_L wiring must be consistent across all nodes.

Improper termination or wiring may result in communication errors, bus instability, or complete loss of communication.

## Configure bit rate and CAN mode

All CAN nodes on the same bus must be configured with **identical communication parameters**:

* The **nominal bit rate** must be the same for all nodes (e.g., 125 kbps, 500 kbps, 1 Mbps).
* If **CAN FD** is used, all nodes must support CAN FD and be configured with compatible **data phase bit rates**.
* Classical CAN and CAN FD nodes **cannot exchange CAN FD frames** unless all nodes support CAN FD and it is enabled.

Ensure that the selected bit rates are supported by both the CAN interface hardware and all connected devices.


---

# 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/connect-the-hardware.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.
