> 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/cmde-add-on/model-and-simulation/configure-devices-within-a-ring/device-section/bq79xxx.md).

# BQ79XXX

The **BQ79XXX** is a virtualized integrated circuit designed to mimic the behavior of different real cell monitoring devices. Within the VeriStand project, it is represented as a **Device** item in the configuration tree and is emulated on the FPGA of the Real-Time target upon project deployment. The **BQ79XXX** device in the **Ring** supports different models, which enables the monitoring of a variable number of battery cells and GPIOs according to the model selected under device type.

## Section Channels <a href="#section-channels" id="section-channels"></a>

Expand the **Device** section in the configuration tree to display the following VeriStand channels. Channel values can be dynamically modified during execution.

<table><thead><tr><th width="149.888916015625">Channel Name</th><th width="79.6666259765625">Type</th><th width="90.22216796875">Format</th><th width="69.88885498046875">Units</th><th>Description</th></tr></thead><tbody><tr><td><strong>Enable</strong></td><td>Input</td><td>Binary</td><td> </td><td><p>Enables or disables the emulated device during execution.</p><ul><li><strong>0</strong> - Device is disabled and bypassed for Daisy Chain transmission.</li><li><strong>1</strong> - Device is enabled. Normal operation.</li></ul><p>Default value: 1</p></td></tr><tr><td><strong>CRC Check</strong></td><td>Input</td><td>Binary</td><td> </td><td><p>Enables or disables the cyclic redundancy check (CRC) of the command packet error code (PEC) and data packet error code (DPEC) of the Daisy Chain transmissions received by the emulated device.</p><ul><li><strong>0</strong> - No CRC check is performed.</li><li><strong>1</strong> - CRC checking is enabled. Normal operation.</li></ul><p>Default value: 1</p></td></tr><tr><td><strong>Port A Enable</strong></td><td>Input</td><td>Binary</td><td> </td><td><p>Enables or disables transmission on the Port A side of the emulated device. Use this channel to simulate a fault in the communication.</p><ul><li><strong>0</strong> - Transmission is disabled on the Port A side of the device.</li><li><strong>1</strong> - Transmission is enabled. Normal operation.</li></ul><p>Default value: 1</p></td></tr><tr><td><strong>Port B Enable</strong></td><td>Input</td><td>Binary</td><td> </td><td><p>Enables or disables transmission on the Port B side of the emulated device. Use this channel to simulate a fault in the communication.</p><ul><li><strong>0</strong> - Transmission is disabled on the Port B side of the device.</li><li><strong>1</strong> - Transmission is enabled. Normal operation.</li></ul><p>Default value: 1</p></td></tr><tr><td><strong>Specific Device Channels</strong></td><td>Input/Output</td><td>Hexadecimal</td><td> </td><td>The BQ79XXX is able to emulate different models and populates extra channels depending on the one chosen. <br>To see the channels added to a given model, please refer to the model-specific page.</td></tr></tbody></table>

## SPI Mode

The SPI Mode of the BQ79XXX device is user configurable at the **Ring** level.

## Supported Commands

The BQ79XXX device supports the following Daisy Chain commands:

| Command             |
| ------------------- |
| Single Device Read  |
| Single Device Write |
| Stack Read          |
| Stack Write         |
| Broadcast Read      |
| Broadcast Write     |


---

# 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/cmde-add-on/model-and-simulation/configure-devices-within-a-ring/device-section/bq79xxx.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.
