> 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/automation-api-and-scripting/rt-lab-api/c-rt-lab-api-reference/functions-reference/opalsetnumbervalues.md).

# OpalSetNumberValues

<table data-header-hidden><thead><tr><th width="199.77777099609375"></th><th></th></tr></thead><tbody><tr><td><strong>Group</strong></td><td>Model Configuration, Acquisition</td></tr><tr><td><strong>Description</strong></td><td>Sets number of values to be acquired for each signal of the specified acquisition group. This constitutes a unit of acquisition in which there are no breaks. Acquired data for this group is considered available when all numValues have been acquired.<br>The change is persistent and is used in subsequent runs of the model. The change affects any application acquiring data from this group.</td></tr><tr><td><strong>Required Control</strong></td><td>Acquisition Control</td></tr><tr><td><strong>Usage</strong></td><td>int <strong>OpalSetNumberValues</strong>(unsigned short acqGroup,unsigned short numValues unsigned short valueType);</td></tr><tr><td><strong>Input</strong></td><td><ul><li><strong>acqGroup:</strong> Acquisition group (numbering starts at 0).</li><li><strong>numValues:</strong> number of values to be acquired for each signal of the specifiedacquisition group.</li><li><strong>valueType:</strong> always 0.</li></ul></td></tr><tr><td><strong>Output</strong></td><td>None</td></tr><tr><td><strong>Return value</strong></td><td><ul><li><strong>EOK:</strong> Success.</li><li><strong>EPERM:</strong> System control had not been granted to this client.</li><li><strong>EINVAL:</strong> invalid acquisition group or valueType not supported or the number of values is out of range.</li><li><strong>EBADF:</strong> Model not specified by previous OpalConnect or OpalSetCurrentModel.</li><li><strong>EIO:</strong> Error sending the request or receiving the reply.</li><li><strong>EACCES:</strong> Error saving parameters to .probe file.</li><li><strong>OP_API_MODEL_IO_TIMEO UT:</strong> Timed out waiting for reply from model.</li></ul><p><strong>Examples</strong></p><ul><li><strong>OP_API_MODEL_IO_ERROR:</strong> Model is missing some or all processes or subsystems.</li></ul></td></tr><tr><td><strong>Examples</strong></td><td>None</td></tr><tr><td><strong>Related items</strong></td><td>None</td></tr></tbody></table>


---

# 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/automation-api-and-scripting/rt-lab-api/c-rt-lab-api-reference/functions-reference/opalsetnumbervalues.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.
