> 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/ehs/model-in-schematic-editor/configure-the-ehs-circuit-interfaces/use-i-o-summary-table.md).

# Use I/O Summary Table

## Overview

The **I/O Summary Table** is located in the right side panel, accessible by selecting the I/Os tab. This tool allows visualization of all **input sources** and **output destinations** that are available in the current setup.

<figure><img src="https://3212678799-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FABuoXNYgvaoO7wIe3bfO%2Fuploads%2Fgit-blob-442c58eb8892cef47668941f910858d4c0935adb%2FSE_manage_setups_dialog.png?alt=media" alt=""><figcaption></figcaption></figure>

The table is separated into three columns: Source, Parameter and Destination. Sources and Destinations are **physical I/Os** represented by the blue (analog I/O) and green (digital I/O) rounded boxes.

## Visualize the inputs and outputs

### **Filter out unused I/Os**

The **In use toggle button** allows the user to view only the input and outputs that are currently used and active.

<figure><img src="https://3212678799-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FABuoXNYgvaoO7wIe3bfO%2Fuploads%2Fgit-blob-8812ce0661859520b8a6ca3eeffcb2bbd030e8a5%2FSE_tableinusetoggle.gif?alt=media" alt=""><figcaption></figcaption></figure>

### **Filter results based on user search value**

By using the filter, users can search specifically for inputs, outputs or parameters that may be in the table. The filter is multi-word, which allows for specifying results.

The filter works for all categories, searching for any potential matches that include the text entered. In the example above, the user enters "di arm" which results in digital inputs with arm parameters to only be displayed. Numbers can also be entered.

<figure><img src="https://3212678799-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FABuoXNYgvaoO7wIe3bfO%2Fuploads%2Fgit-blob-40ce591b75e9a1046258c6f6db10e376007fab46%2FSE_filtertable.gif?alt=media" alt=""><figcaption></figcaption></figure>

### **Sort results**

The default sort for the table is by ascending sources. By clicking on the header of the category the user would like to sort, the sort is triggered. By clicking a second time on the same header, the sort is triggered in reverse (i.e from sources ascending to sources descending and vice versa).

Parameters can also be sorted, moving all in use inputs and outputs to the top of the table. Clicking twice sorts them at the top, but in descending direction.

<figure><img src="https://3212678799-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FABuoXNYgvaoO7wIe3bfO%2Fuploads%2Fgit-blob-15db7889502345d65c656b8c3346dfa468f778fc%2FSE_tablesort.gif?alt=media" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
All three different functionalities can be used together to visualize the inputs and outputs in various ways.
{% endhint %}


---

# 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/ehs/model-in-schematic-editor/configure-the-ehs-circuit-interfaces/use-i-o-summary-table.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.
