> 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/pe-add-on-simulink/hardware-configurations-reference/pxie-7868r/ehsx64_quad_im_saturation_io_7868r.md).

# eHSx64\_Quad\_IM\_Saturation\_IO\_7868R

## Specifications

<figure><img src="https://2999842053-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fe9Kk9pJCHht2LLBSxPap%2Fuploads%2Fyy649xsMCbCanhpreV5h%2Fimage.png?alt=media&amp;token=b94c086a-b919-4286-b1ef-15d7e6ebfa98" alt="" width="244"><figcaption></figcaption></figure>

## I/O Capabilities

This configuration requires the following FPGA boards. Please refer to the linked product page for additional information.

<table><thead><tr><th width="199.77777099609375">Quantity</th><th>FPGA Board</th></tr></thead><tbody><tr><td>1</td><td><a href="http://www.ni.com/en-us/support/model.pxie-7868.html">PXIe-7868R</a></td></tr></tbody></table>

The PXIe-7868R supports the following features:

<table><thead><tr><th width="201.55560302734375">I/O Type</th><th>Details</th></tr></thead><tbody><tr><td><strong>Analog Input</strong></td><td>6 CH, 1MS/s, 16-bit, +/- 10V Input Signal Range, Differential<br>Tunable Gain, Offset, and Min/Max Saturation</td></tr><tr><td><strong>Analog Output</strong></td><td>18 CH, 1MS/s, 16-bit<br>User-defined mapping to Analog Outputs available with tunable Gain, Offset, and Min/Max Saturation.<br>- Measurements<br>- Sinewaves<br>- CPU (VeriStand)<br>- Machines</td></tr><tr><td><strong>Digital Input</strong></td><td>32 CH, 80MHz, 3.3V TTL (Connector 1)</td></tr><tr><td><strong>Digital Output</strong></td><td>16 CH, 10MHz, 3.3V TTL (Connector 0)<br>User-defined mapping to Digital Outputs available with tunable Polarity.<br>- CPU (VeriStand)<br>- Encoders<br>- PWMs<br>- Digital Inputs</td></tr></tbody></table>

## Modeling Capabilities

This configuration includes a pre-compiled firmware/bitfile which contains the following features:

| Features                                 | Low Latency Support |
| ---------------------------------------- | :-----------------: |
| **1x eHSx64 Solver**                     |         Yes         |
| **4x IM with Saturation Machine Solver** |         Yes         |
| **1x Encoder / machine**                 |         Yes         |
| **1x Resolver / machine**                |         Yes         |
| **32x Sinewave Generators**              |          No         |
| **16x PWM Generators**                   |         Yes         |
| **12x Sinusoidal PWM Generators**        |          No         |
| **18x Analog Outputs**                   |          No         |
| **6x Analog Inputs**                     |          No         |
| **16x Digital Outputs**                  |          No         |
| **32x Digital Inputs**                   |          No         |
| **32x Waveform Acquisition Channels**    |          No         |
| **Telemetry Channels**                   |          No         |

In features with **Low Latency Support**, data is transferred between the FPGA and Real Time VeriStand Channels through the Low Latency FPGA Communication Processes. For more information related to communication processes in the Power Electronics Add-On, refer to **Processor Assignments**.


---

# 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/pe-add-on-simulink/hardware-configurations-reference/pxie-7868r/ehsx64_quad_im_saturation_io_7868r.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.
