> 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/multiplexed-can-messages.md).

# Multiplexed CAN Messages

## Overview

CAN signal multiplexing allows **multiple signals to share the same memory range** within a CAN message payload. This reduces the number of messages required by selecting different signal sets based on a **multiplex value** during runtime.

* **Multiplexer signal**\
  A signal whose value selects which group of signals is active.
* **Multiplexed signals**\
  Signals that are transmitted or received only when the multiplexer signal matches a specific value.

Each multiplexed signal is associated with a **multiplex value** defined in its multiplexer mode.

## Supported multiplexing types

Two multiplexing types exist in CAN:

* Simple signal multiplexing
* Extended signal multiplexing

**Only simple signal multiplexing is currently supported**, with the following constraints:

* One multiplexer signal per message
* Each multiplexed signal has exactly one multiplex value

## Behavior and visualization

* Overlap detection is **disabled** for multiplexed messages because overlapping signals are expected.
* The **Frame Viewer** does not report overlap errors for multiplexed signals.
* All signals are displayed in the configuration, but **only the signals matching the current multiplex value are transmitted or received**.

## Example behavior

In the example shown:

* Signals `BCS_HS_Load_01` to `BCS_HS_Load_04` are associated with multiplex value **0**
* Signals `BCS_HS_Vout_01` to `BCS_HS_Vout_04` are associated with multiplex value **1**
* `BCS_HS_Card1_Selection` is the multiplexer signal

During execution:

* If the multiplexer signal value is **0**, the data frame includes:
  * The multiplexer signal
  * Signals associated with value 0
  * Signals marked as **Normal**
* If the value is **1**, the corresponding group is selected instead

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


---

# 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/multiplexed-can-messages.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.
