> For the complete documentation index, see [llms.txt](https://docs.mathewscompany.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mathewscompany.com/pinnacle-2020/pinnacle-20-or-20-controls/troubleshooting/plc-i-o-modules.md).

# PLC I/O Modules

The fourth of the five options under Troubleshooting is PLC I/O Modules. The PLC and I/O modules are located in the Low Voltage Cabinet. The number of I/O modules depends on the model dryer. On the bottom of the page, only the I/O modules equipped on the dryer will be lit up, and therefore able to be accessed. The grayed out options cannot be accessed as those modules are not equipped on the dryer. Also, the order in which the PLC and I/O modules appear, should match the actual arrangement in which they are physically installed in the Low Voltage Cabinet.

The first option at the bottom of the page is the CPU and is on all Pinnacle 20|20 dryers. The CPU allows up to 14 digital inputs, 10 digital outputs, 2 analog inputs and 2 analog outputs.

<figure><img src="https://content.gitbook.com/content/QuAD4cJGmByvZ0oa7oPk/blobs/hDbVa0NMw3ZvdlipfxVe/Screenshot%202024-10-09%20135620.png" alt=""><figcaption></figcaption></figure>


---

# 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://docs.mathewscompany.com/pinnacle-2020/pinnacle-20-or-20-controls/troubleshooting/plc-i-o-modules.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.
