> 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.md).

# Configure CAN

When working with communication protocols, it is recommended to begin by configuring the protocol through the **I/O Interfaces** section in <code class="expression">space.vars.Software</code> before proceeding with other steps.

## Configure the CAN I/O interface

{% stepper %}
{% step %}

### Add a new I/O interface

In RT-LAB Project Explorer, right-click **I/O Interfaces**, select **New I/O Interface**, and choose **CAN**. Double-click the newly created interface to begin configuration.
{% endstep %}

{% step %}

### Import CAN configurations (optional)

The **CANdb Importer** wizard simplifies the creation of CAN configurations by importing **nodes, messages, and signal definitions** from CAN database files that conform to the [Vector standard](https://www.vector.com/int/en/products/products-a-z/software/candb/).

See the supported file types below and follow the **corresponding import workflow** for each format:

* [**DBC** – Classical CAN database files](https://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/can/configure-can/import-classical-can-database-files-dbc.md)
* [**ARXML** – AUTOSAR XML files containing CAN definitions](https://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/can/configure-can/import-autosar-xml-files.md)
  {% endstep %}

{% step %}

### Configure the general settings

In the **Folders** list, click **General** and configure the general settings.

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

Click the newly added **CANr** in the **I/O Interface Configuration** window and configure the general settings.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-c82c12b255d57142eef2557345af229e49eba5e8%2Fdr-hyp-can-general.jpg?alt=media" alt=""><figcaption></figcaption></figure>

{% endif &}

<table><thead><tr><th width="170">Parameter</th><th>Value (Description)</th></tr></thead><tbody><tr><td><strong>Hardware</strong></td><td>Specifies the type of <strong>CAN hardware</strong> connected to the simulator. Only Kvaser is available.</td></tr><tr><td><strong>Use an RT core for asynchronous computation</strong></td><td><strong>Checked:</strong> A dedicated real‑time CPU core is reserved for CAN communication.<br><strong>Unchecked:</strong> CAN communication runs on <strong>core 0</strong>.</td></tr><tr><td><strong>Verbose</strong></td><td><strong>Checked:</strong> The complete CAN configuration is displayed during model loading.<br><strong>Unchecked:</strong> Configuration details are not displayed.</td></tr><tr><td><strong>Reverse gain/offset computation</strong></td><td><p>Controls the order in which <strong>gain</strong> and <strong>offset</strong> are applied when converting values between the RT‑LAB model and CAN messages.</p><p><strong>Checked:</strong><br>When transmitting (model → CAN), the driver applies the <strong>gain first</strong>, then the <strong>offset</strong>. <code>can_value = (model_value × gain) + offset</code><br>When receiving (CAN → model), the driver applies the <strong>offset first</strong>, then the <strong>gain</strong>. <code>model_value = (can_value − offset)/gain</code></p><p><strong>Unchecked:</strong><br>When transmitting (model → CAN), the driver applies the <strong>offset first</strong>, then the <strong>gain</strong>. <code>can_value = (model_value − offset)/gain</code><br>When receiving (CAN → model), the driver applies the <strong>gain first</strong>, then the <strong>offset</strong>. <code>model_value = (can_value × gain) + offset</code></p></td></tr><tr><td><strong>Enable queue length extension</strong></td><td><p><strong>Checked:</strong> Allows configuration of the queue length:</p><ul><li><strong>Queue length:</strong> Buffer size used to synchronize CAN data between the driver and the model. The queue must be large enough to accommodate the number of CAN frames exchanged within one model time step. If the model time step is increased, the queue length may need to be increased accordingly to avoid data loss (for example, increasing the time step from <strong>1 ms to 10 ms</strong> may require increasing the queue length from <strong>25 to 250</strong>).</li></ul><p><strong>Unchecked:</strong> The default queue size is used.</p></td></tr><tr><td><strong>Monitor message flags, error counters and statuses</strong></td><td><strong>Checked:</strong> Exposes <strong>message</strong> flags, error counters, and status connectable points for all messages. In <strong>Dashboards</strong>, new <strong>Simulator Channels</strong> for <strong>message</strong> flags, error counters, and statuses are available. These channels can be mapped to an <strong>OpInput</strong> blocks allowing them to be monitored directly from the model during execution.<br><strong>Unchecked:</strong> These connectable points are not exposed.</td></tr><tr><td><strong>Transmit rate factor</strong></td><td>Multiplier applied to the model time step to determine the cyclic transmit rate.</td></tr><tr><td><strong>Enable reverse gain/offset computation on channel basis</strong></td><td><p><strong>Checked:</strong> The <strong>reverse gain/offset computation</strong> setting defined at the channel level overrides the global gain/offset reversal setting.</p><p><strong>Unchecked:</strong> The <strong>global gain/offset reversal setting</strong> is applied, and channel‑level settings are ignored.</p></td></tr><tr><td><strong>Enable virtual mode</strong></td><td><p><strong>Checked:</strong> The model can be executed even if this I/O interface is not compatible with the system’s hardware configuration. This mode is useful for troubleshooting, model preparation, or developing configurations when the hardware is not available.</p><p><strong>Unchecked:</strong> The model requires a compatible hardware configuration, and the I/O interface communicates with the physical hardware during execution.</p></td></tr></tbody></table>
{% endstep %}

{% step %}

### Manage channels: add, remove, rename, or reorder

Click **Channels(x)** and use:

* **+** icon to add channels
* **–** icon to remove channels
* **Arrow** icons to reorder channels

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-e0d2cb0c4aff35016aea61674b364860fe130da4%2FDR-rtlab-can2.png?alt=media" alt="" width="493"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Configure the channel(s) settings

Click a channel under the **Channels** to configure its settings. Repeat for each additional CAN channel required to communicate with external CAN buses or devices.

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

<table><thead><tr><th width="145">Parameter</th><th width="545">Value (Description)</th></tr></thead><tbody><tr><td><strong>Channel ID</strong></td><td><p>Binds the configuration to a <strong>physical CAN channel</strong> on the hardware interface. Channel IDs are <strong>zero‑based in the interface configuration</strong>, while hardware channels are <strong>one‑based</strong>. For example:</p><ul><li><strong>Channel ID 0</strong> configures <strong>hardware Channel 1</strong></li><li><strong>Channel ID 1</strong> configures <strong>hardware Channel 2</strong>, and so on.</li></ul><p>When a new channel is added, the default ID is <strong>0</strong>; ensure the ID is set to match the intended physical hardware channel.</p></td></tr><tr><td><strong>Enable CAN FD</strong></td><td><strong>Checked:</strong> Configures the channel in <strong>CAN FD mode</strong>, allowing messages with payloads of up to <strong>64 bytes</strong>. All nodes on the same bus must use a matching <strong>arbitration bit rate</strong>. Classical CAN messages can still be transmitted and received.<br><strong>Unchecked:</strong> The channel operates in <strong>Classical CAN</strong> mode only.</td></tr><tr><td><strong>Arbitration bit rate (only when CAN FD is enabled)</strong></td><td><p>Supported preset values are <strong>1 Mbps (SP 62.5%)</strong>, <strong>500 kbps (SP 62.5%)</strong>, and <strong>500 kbps (SP 80%)</strong>.</p><p>A custom bit‑rate and sampling‑point combination can be configured by selecting <strong>Custom</strong> and filling in the required fields:</p><ul><li><strong>Arbitration time segment 1 (TSEG1):</strong> Number of time quanta from the end of the sync segment to the sampling point during the arbitration phase.</li><li><strong>Arbitration time segment 2 (TSEG2):</strong> Number of time quanta from the sampling point to the end of the bit during the arbitration phase.</li><li><strong>Arbitration synchronization jump width (ASJW):</strong> Maximum adjustment of the bit timing to maintain synchronization; must be ≤ min(TSEG1, TSEG2).</li><li><strong>Arbitration prescaler:</strong> Clock prescaler value used to derive the time quantum for the arbitration phase.</li></ul></td></tr><tr><td><strong>Bit rate</strong></td><td><p>Selects the nominal bit rate based on the desired setup (e.g., cable length and bus behavior). Supported preset values range from <strong>50 kbps to 1 Mbps</strong> for Classical CAN and <strong>500 kbps to 8 Mbps</strong> for CAN FD, with predefined sampling points. A custom bit‑rate and sampling‑point combination can be configured by selecting <strong>Custom</strong> and filling in the required fields:</p><ul><li><strong>Frequency:</strong> Desired nominal bit rate in <strong>kbps</strong>; not available for <strong>CAN FD</strong>.</li><li><strong>Time segment 1 (TSEG1):</strong> Number of time quanta from the end of the sync segment to the sampling point.</li><li><strong>Time segment 2 (TSEG2):</strong> Number of time quanta from the sampling point to the end of the bit.</li><li><strong>Synchronization jump width (SJW):</strong> Maximum bit‑timing adjustment used to maintain synchronization.</li><li><strong>Bit sampling points:</strong> Number of samples per bit during the arbitration phase; always <strong>1</strong> for CAN FD data rates and not configurable.</li><li><strong>Prescaler:</strong> Clock prescaler used for the <strong>data phase</strong>; available only for <strong>CAN FD</strong>.</li></ul></td></tr><tr><td><strong>Use extended mode</strong></td><td><strong>Checked:</strong> Enables <strong>extended CAN frames</strong> (29‑bit identifiers), allowing message IDs in the range <strong>0 to 536 870 911</strong>.<br><strong>Unchecked:</strong> Uses <strong>standard CAN frames</strong> (11‑bit identifiers), allowing message IDs in the range <strong>0 to 2047</strong>.</td></tr><tr><td><strong>Use silent mode</strong></td><td><strong>Checked:</strong> The channel operates in <strong>listen‑only mode</strong> and does not transmit any CAN messages.<br><strong>Unchecked:</strong> The channel can transmit and receive CAN messages normally.</td></tr><tr><td><strong>Monitor bus load</strong></td><td><strong>Checked:</strong> Exposes the <strong>Bus Load</strong> connectable point. In <strong>Dashboards</strong>, a new <strong>Simulator Channel</strong> named <strong>Bus Load</strong> is available. This channel can be mapped to an <strong>OpInput</strong> block allowing to monitor the current CAN bus utilization (%) directly from the model during execution:<br><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-231af56b360032705448974b73c34d779c2a3e08%2Fimage%20(336).png?alt=media" alt=""><br><em>Enabling this option may reduce CAN communication performance.</em><br><strong>Unchecked:</strong> Bus load monitoring is disabled.</td></tr><tr><td><strong>Enable transmission control</strong></td><td><strong>Checked:</strong> Exposes the <strong>Enable Transmission</strong> connectable point for the channel. In <strong>Dashboards</strong>, a new <strong>Simulator Channel</strong> named <strong>Enable Transmission</strong> (for the channel) is available. This channel can be mapped to an <strong>OpOutput</strong> block allowing to enable or disable message transmission for the channel directly from the model during execution:<br><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-8626b7547fe2d83e9629c1b9b2b5c8452d0c68d6%2Fimage%20(337).png?alt=media" alt=""><br><strong>Unchecked:</strong> Transmission on the channel is always enabled.</td></tr><tr><td><strong>Enable reception control</strong></td><td><strong>Checked:</strong> Exposes the <strong>Enable Reception</strong> connectable point for the channel. In <strong>Dashboards</strong>, a new <strong>Simulator Channel</strong> named <strong>Enable Reception</strong> (for the channel) is available. This channel can be mapped to an <strong>OpOutput</strong> block allowing to enable or disable message reception for the channel directly from the model during execution:<br><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-ccf5c679c27c8e7a82768219d90ba1bcff841cf1%2Fimage%20(338).png?alt=media" alt=""><br><strong>Unchecked:</strong> Reception on the channel is always enabled.</td></tr><tr><td><strong>Record channel data</strong></td><td><strong>Checked:</strong> CAN data for this channel is <strong>logged</strong> during execution.<br><strong>Unchecked:</strong> Channel data is not recorded.</td></tr><tr><td><strong>Monitor channel flags, error counters and statuses</strong></td><td><strong>Checked:</strong> Exposes <strong>channel</strong> flags, error counters, and status connectable points for this channel. In <strong>Dashboards</strong>, new <strong>Simulator Channels</strong> for this <strong>channel</strong> flags, error counters, and statuses are available. These channels can be mapped to an <strong>OpInput</strong> blocks allowing them to be monitored directly from the model during execution.<br><strong>Unchecked:</strong> These connectable points are not exposed.</td></tr><tr><td><strong>Reverse gain/offset computation for this channel</strong></td><td>This parameter is available only when <strong>Enable reverse gain/offset computation on a channel basis</strong> is checked in the <strong>General</strong> settings.<br>For more information, refer to <a href="#configure-the-general-settings"><strong>Reverse gain/offset computation</strong></a><strong>.</strong></td></tr></tbody></table>

#### Gain and Offset Specification

The gain and offset computation is described in the next two figures.

The driver operations are within the blue boxes, the OpInput and the OpOutput represent the standard data points coming from and going to the model and the CAN-BUS subsystem represents the real CAN network.

* If reverse gain/offset computation option is **disabled** the operations are as follows.

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

\* If reverse gain/offset computation option is \*\*enabled\*\* the operations are as follows.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-4fcbba5fa2fc3f45c65a43ac6792ba14987b8d7a%2Fdr-rtlab-can-gain-2.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Manage buses: add, remove, rename, or reorder

Click **Buses** and use:

* **+** icon to add buses
* **–** icon to remove buses
* **Arrow** icons to reorder buses

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

{% hint style="info" %}
When a bus is created using the **DBC importer wizard**, the **Filename** parameter displays the associated DBC file. This field is empty if the bus is not configured through the wizard.
{% endhint %}
{% endstep %}

{% step %}

### Manage nodes: add, remove, rename, or reorder

Expand a bus to reveal its **Nodes** and use:

* **+** icon to add nodes
* **–** icon to remove nodes
* **Arrow** icons to reorder nodes

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-345b68a4289e7041bebfd612308a29cf8aeb178f%2FDR-rtlab-can5.png?alt=media" alt="" width="534"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Configure the node(s) Channel ID

Click a node under the **Nodes** folder to configure its **Channel ID**.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-76e4a85849537a7ce4b35edd225f0ee7544516a6%2FDR-rtlab-can6.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Manage CAN messages: add, remove, rename, or reorder

Expand a node to reveal its **Messages** and use:

* **+** icon to add data points
* **–** icon to remove data points
* **Arrow** icons to reorder data points

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-f7fca07fbc39849ba222f20d8886768154ed7fa9%2FDR-rtlab-can7.png?alt=media" alt="" width="552"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Configure CAN messages

1. Expand **Messages** to display all available messages, then select a message to configure its parameters.

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

{% tabs %}
{% tab title="Mode = Transmission" %}

<table><thead><tr><th width="170">Parameter</th><th>Value (Description)</th></tr></thead><tbody><tr><td><strong>Mode</strong></td><td><strong>Transmission:</strong> The message is sent on the CAN bus.</td></tr><tr><td><strong>Use dynamic ID</strong></td><td><strong>Checked:</strong> The CAN ID is controlled at runtime from the console via a connectable <strong>ID</strong> signal.<br><strong>Unchecked:</strong> The CAN ID is fixed and defined by the <strong>CAN ID</strong> parameter.</td></tr><tr><td><strong>CAN ID</strong></td><td>Defines the message identifier and therefore its <strong>priority on the CAN bus</strong>. Lower values have higher priority (ID = 0 is the highest priority).</td></tr><tr><td><strong>Specify DLC</strong></td><td><p><strong>Checked:</strong> The <strong>Data Length Code (DLC)</strong> is manually configured:</p><ul><li><strong>Data length code:</strong> Available values depend on the channel type: up to <strong>8 bytes</strong> for Classical CAN or <strong>64 bytes</strong> for CAN FD.</li></ul><p><strong>Unchecked:</strong> The DLC is automatically computed from the defined message signals. This option is automatically enabled when importing from <strong>DBC or ARXML</strong> files.</p></td></tr><tr><td><strong>Channel ID</strong></td><td>Identifies the <strong>physical CAN channel</strong> on which the message is transmitted or received. This parameter is <strong>read‑only</strong> and is inherited from the <strong>channel ID of the node</strong> that contains the message.</td></tr><tr><td><strong>Enable cyclic transmission</strong></td><td><p><strong>Checked:</strong> The message is transmitted periodically based on the <strong>Transmit rate</strong> parameter:</p><ul><li><strong>Transmit rate (ms):</strong> Cyclic transmission period. If the rate is lower than the model time step, the message is transmitted at every time step.</li><li><p><strong>Enable dynamic transmit rate:</strong></p><ul><li><strong>Checked:</strong> Exposes the <strong>Transmit Rate</strong> connectable point. In <strong>Dashboards</strong>, a new <strong>Simulator Channel</strong> named <strong>Transmit Rate</strong> is available. This channel can be mapped to an <strong>OpOutput</strong> block allowing to control the <strong>Transmit Rate</strong> directly from the model during execution:<br><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-da88e5dea1834e8fc00f7a228382a91c7bf1cf3e%2Fdr-can-transient-rate.png?alt=media" alt=""><br>The <strong>Enable Message</strong> for that message connectable point is no longer exposed.</li><li><strong>Unchecked:</strong> The transmit rate is fixed and defined by the <strong>Transmit Rate</strong> parameter.</li></ul></li><li><p><strong>Enable transmit rate resynchronization:</strong></p><ul><li><strong>Checked:</strong> Changes to the dynamic transmit rate are applied immediately on the rising edge of the Resynchronization Signal.</li><li><strong>Unchecked:</strong> Changes take effect after completion of the current transmit cycle.</li></ul></li><li><p><strong>Force enable message:</strong></p><ul><li><strong>Checked:</strong> Exposes the <strong>Enable Message</strong> back, allowing to enable or disable message transmission directly from the model.</li><li><strong>Unchecked:</strong> The message is always enabled for transmission while cyclic transmission is active.</li></ul></li></ul><p><strong>Unchecked:</strong> The message uses the default transmission rate derived from the model time step and the <strong>Transmission Rate Factor</strong> set in the general settings.</p></td></tr></tbody></table>
{% endtab %}

{% tab title="Mode = Reception" %}

<table><thead><tr><th width="170">Parameter</th><th>Value (Description)</th></tr></thead><tbody><tr><td><strong>Mode</strong></td><td><strong>Reception:</strong> The message is received on the CAN bus.</td></tr><tr><td><strong>Use promiscuous mode</strong></td><td><strong>Checked:</strong> The message is updated with the contents of <strong>all CAN frames</strong> received on the selected channel, regardless of their identifier.<br><strong>Unchecked:</strong> Only CAN frames matching the configured <strong>CAN ID</strong> are processed.</td></tr><tr><td><strong>CAN ID</strong></td><td>Specifies the CAN identifier used to <strong>filter received frames</strong> when promiscuous mode is disabled. Only messages with this identifier update the signal values.</td></tr><tr><td><strong>Buffer size</strong></td><td>Defines the <strong>maximum number of CAN frames</strong> that can be received and processed within a single calculation step. Separate buffer connection points (e.g., flags, signals, IDs) are created for each buffered frame.</td></tr><tr><td><strong>Channel ID</strong></td><td>Identifies the <strong>physical CAN channel</strong> on which the message is transmitted or received. This parameter is <strong>read‑only</strong> and is inherited from the <strong>channel ID of the node</strong> that contains the message.</td></tr></tbody></table>
{% endtab %}
{% endtabs %}

2. Use the signal definition table (bottom section) to describe how individual data elements are encoded within the CAN message payload. Use:

* **+** icon to add signals
* **–** icon to remove signals
* **Arrow** icons to reorder signals

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

{% hint style="info" %}
The **Frame Viewer** (upper right section) provides a visual **8 × 8 bit‑level representation** of the 64‑bit (8‑byte) CAN payload. Each row represents one **byte** of the CAN frame. Each column represents a **bit position** within the byte. Colored blocks show how individual signals are packed into the CAN frame. This visualization helps verify **bit alignment, signal size, and ordering**, and is especially useful when working with tightly packed or mixed‑size signals.

When **CAN FD** is enabled, the viewer still shows the first **64 bits** for visualization, even though the payload may be larger.

Selecting a signal highlights the **bit range** it occupies in the frame, with an arrow indicating the **start and end bit positions**. Signal **endianness** affects how bits are mapped and may change the highlighted range. Hovering over a cell displays the name of the signal occupying that bit.

The Frame Viewer also highlights **overlapping signals**, where multiple signals share the same bit range. Such overlaps may lead to incorrect data encoding or decoding and should generally be avoided.
{% endhint %}

3. Configure the encoding of each signal in the CAN message payload and save your changes:

<table data-header-hidden><thead><tr><th width="170"></th><th></th></tr></thead><tbody><tr><td><strong>Name</strong></td><td>Unique identifier for the signal. Used by RT‑LAB to create a connectable <strong>Simulator Channel</strong> in the <strong>CAN Interface (Dashboards)</strong>, which can be mapped to an <strong>OpInput</strong> or <strong>OpOutput</strong> block for runtime control or monitoring from the model.</td></tr><tr><td><strong>Type</strong></td><td><p>Defines the data type of the signal:</p><ul><li><strong>Bit:</strong> Single‑bit signal (1 bit).</li><li><strong>Unsigned:</strong> Unsigned integer value (1 to 64 bits).</li><li><strong>Signed:</strong> Signed integer value (1 to 64 bits).</li><li><strong>Float:</strong> Single‑precision floating‑point value (32 bits).</li><li><strong>Double:</strong> Double‑precision floating‑point value (64 bits).</li></ul></td></tr><tr><td><strong>Multiplexer mode</strong></td><td><p>Defines how the signal participates in message multiplexing:</p><ul><li><strong>Multiplexer Signal:</strong> Carries the multiplex selector value</li><li><strong>&#x3C;Integer value>:</strong> Signal is active only for the specified multiplex value.</li><li><strong>Normal:</strong> Signal is not multiplexed.</li></ul><p>Refer to <a href="https://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/can/configure-can/multiplexed-can-messages.md">Multiplexed CAN Messages</a> for detailed explanation.</p></td></tr><tr><td><strong>Custom type</strong></td><td>Available only for <strong>Transmission</strong> messages. Default is <strong>None</strong>. When set to <strong>Rolling counter</strong> or <strong>CRC8_SAE_J1850</strong>, no connection point is created for the signal.</td></tr><tr><td><strong>Start bit</strong></td><td>Bit position at which the signal starts within the CAN frame payload.</td></tr><tr><td><strong>Size (bits)</strong></td><td>Number of bits used by the signal, ranging from <strong>1 to 64 bits</strong>, depending on the selected type.</td></tr><tr><td><strong>Endianness</strong></td><td>Bit ordering of the signal within the CAN frame: <strong>Intel (little‑endian)</strong> or <strong>Motorola (big‑endian)</strong>.</td></tr><tr><td><strong>Initial value</strong></td><td>Initial physical value assigned to the signal at model initialization.</td></tr><tr><td><strong>Min</strong></td><td>Minimum physical value the signal can represent. This value depends on the signal type and size in bits.</td></tr><tr><td><strong>Max</strong></td><td>Maximum physical value the signal can represent. This value depends on the signal type and size in bits.</td></tr><tr><td><strong>Gain</strong></td><td>Scaling factor applied to the signal value during transmission or reception.</td></tr><tr><td><strong>Value offset</strong></td><td>Offset applied to the signal value during transmission or reception.</td></tr></tbody></table>
{% endstep %}

{% step %}

### Save the configuration

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-44bd03ce3c41f8ba5c990b61c29b38c9b80ae5f2%2FDR-rtlab-save.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}


---

# 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.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.
