> 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/understand-can-driver-channels-buses-and-nodes.md).

# Understand CAN Driver Channels, Buses & Nodes

In the CAN configuration, it is important to distinguish between **physical hardware elements** and **logical (software) abstractions**.

A **CAN channel** represents an **independent hardware CAN interface** (i.e., one CAN controller with its own timing, arbitration, and error handling). On Kvaser PCIe CAN interface cards, each channel corresponds to one independent CAN bus connection from a protocol perspective. The **maximum number of channels is fixed by the hardware** and equals the number of CAN controllers implemented on the card.

A **CAN connector** is the **physical connector** used to expose one or more CAN channels. Depending on the Kvaser card model, **multiple CAN channels may be multiplexed onto a single physical connector**. For example, the *Kvaser PCIEcan 4xCAN v2* provides **four independent CAN channels through a single 26‑pin HD D‑SUB connector**, with each channel mapped to a specific set of pins. In such cases, a breakout cable is used to access each channel separately. As a result, the number of connectors does **not** necessarily match the number of channels.

A **CAN bus**, in the <code class="expression">space.vars.Software</code> CAN driver, is a **logical (virtual) bus used for modeling and configuration purposes**. It does not represent an additional physical CAN bus or connector. Instead, a bus is a software construct used to group CAN messages and nodes and to define how they are organized within the model. **Multiple logical buses may be defined and mapped to the same physical CAN channel**, but all such buses still share the same underlying physical CAN bus and arbitration domain.

**Nodes** defined under a bus are **logical CAN nodes** used to represent ECUs or functional entities within the model. These nodes do not correspond to independent physical CAN controllers. They do not have separate arbitration, error states, or acknowledgment behavior. From the perspective of the CAN network, all messages transmitted through a given channel originate from a **single physical CAN node**, regardless of how many logical buses or nodes are configured.

In summary:

* **Channels** are **hardware CAN controllers**, fixed by the interface card.
* **Buses** are **software abstractions** used to organize messages and nodes.
* **Nodes** are **logical representations** of ECUs within the model.
* Multiple buses and nodes can be associated with a single channel, but they all communicate over the **same physical CAN bus**.


---

# 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/understand-can-driver-channels-buses-and-nodes.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.
