> 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/library-blocks-reference/target-inputs-and-outputs/target-input-analog.md).

# Target Input, Analog

## Description

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-4093dbd3b38b46b1df3c8d7ab34f9ead0a4964c8%2Fimage%20(1050).png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

The **Target Input, Analog** blocks, located in the **Target Inputs And Outputs** library, provide 8-, 32-, and 64-channel analog input configurations that map inputs to outputs.

The 8-input block, is slightly different to the other two, includes per-channel source selection (between input sensors and input pins) and per-channel gain and offset.

$$
y=(u+Offset) \times Gain
$$

The 32-input and 64-input blocks forward their inputs directly to their outputs without modification.

## Mask parameters

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-4cef6cbd8180dda358e65ae4b42e064a065c6a95%2Fimage%20(1051).png?alt=media" alt="" width="563"><figcaption><p>8-input block</p></figcaption></figure>

32-input and 64-input blocks have no parameter

<table><thead><tr><th width="239.60003662109375">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Description</strong></td><td>Free-form field to document the block.</td></tr><tr><td><strong>Signal source</strong></td><td>Selects the source for y[1..8]: uu[1..8] input sensors or u[1..8] input pins.</td></tr><tr><td><strong>Gain</strong></td><td>Per-signal gain applied to the selected source.</td></tr><tr><td><strong>Dc offset compensation</strong></td><td>Per-signal offset applied to the selected source.</td></tr></tbody></table>

## Inputs

<table><thead><tr><th width="240.39996337890625">Input</th><th>Description</th></tr></thead><tbody><tr><td><strong>u[1..8] or uu[1..8]</strong></td><td>Input pins or Input sensors (8-input block only).</td></tr><tr><td><strong>uu[1..32]</strong></td><td>Inputs (32-input block).</td></tr><tr><td><strong>uu[1..64]</strong></td><td>Inputs (64-input block).</td></tr></tbody></table>

## Outputs

<table><thead><tr><th width="240.39996337890625">Output</th><th>Description</th></tr></thead><tbody><tr><td><strong>y[1..8]</strong></td><td>Selected source (uu or u) with optional per-channel gain and offset (8-input block).</td></tr><tr><td><strong>y[1..32]</strong></td><td>Direct pass-through of uu[1..32] (32-input block).</td></tr><tr><td><strong>y[1..64]</strong></td><td>Direct pass-through of uu[1..64] (64-input block).</td></tr></tbody></table>

## Signals available for monitoring and external I/O connections (via sensors form)

All block inputs and outputs are available as signals for monitoring and for external I/O connections.


---

# 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/library-blocks-reference/target-inputs-and-outputs/target-input-analog.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.
