> 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/signal-generator.md).

# Signal Generator

## Introduction to Signal Generator

The **Signal Generator I/O interface** allows the user to configure the various OPAL-RT analog and digital I/O boards.

The Signal Generator is primarily used to generate test signals without requiring changes to the model topology. Supported signal types include sawtooth, sine, square, triangular, and time-based signals. It provides additional debugging and validation options during model development and testing.

The Playback feature enables the replay of recorded datasets in the simulation model. Data captured in an OPREC file or stored in a CSV file can be injected as input signals to model blocks. This functionality is frequently used for model validation, testing, and debugging by reproducing real or previously recorded operating scenarios.

## Example applications

A user can record the inputs and outputs of a custom PSCAD block, replay the recorded inputs in HYPERSIM, and compare the outputs from both tools to verify that the implementation and mathematical behavior are equivalent.


---

# 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/signal-generator.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.
