> 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/get-started/run-your-integration-project.md).

# Run Your Integration Project

## How I/O testing works

Your system includes custom I/O test models designed to verify the simulator’s I/O functionality. These models use loopback connections, where signals generated by the simulator are output through an output module and fed back into an input module to confirm correct operation. This process ensures the system can accurately generate, output, measure, and input signals.

For simple setups, such as a single AO (Analog Output) module and AI (Analog Input) module, loopback testing is straightforward: connect the AO module’s output to the AI module’s input using a loopback cable. The same principle applies to DO (Digital Output) and DI (Digital Input) modules. When using a DO module, ensure the loopback cable is properly powered. For detailed information, refer to the **System Description Document** included on the **CD** or **USB** drive with your system.

For more complex setups, such as systems with multiple AO or DO modules but only one AI or DI module, testing can be performed sequentially. Begin by connecting the first AO module to the AI module and verifying its operation. Additional AO modules can then be tested one at a time, as needed. Note that some test models may only work with specific I/O modules (e.g., the first AO module). If you are unsure, [contact our support team](https://www.opal-rt.com/contact-technical-support/).

Although the model used in this guide may differ from the one included with your system, the general components and procedures are similar. Specific details about I/O pin assignments and module configurations are provided in your **System Description Document**.


---

# 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/get-started/run-your-integration-project.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.
