> 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/system-configuration.md).
# System Configuration
The third of the five options under Troubleshooting is System Configuration. This page is broken into two sections, Dryer Configuration at the top and System Configuration at the bottom.
The Dryer Configuration lists the serial number and the model of the dryer that is loaded in the control.
The System Configuration lists the PLC and HMI versions. This is important information given both the PLC and HMI will develop newer, more enhanced versions of the software as time passes.
It also provides a place where the type of grain being dried can be selected. It is important that the proper grain is selected in order to receive accurate information from the moisture sensors.
Other parameters that can be changed on this page is the date, time, temperature units, discharge units, grain density and the language.
A check box is provided to allow the dryer to be operated remotely by way of M-C Trax. When operating from a remote location, this box must be checked. When a change is made remotely, a pin will be required to be entered. This pin must match the Remote Access 4-Digit pin shown on this page of the HMI.
---
# 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/system-configuration.md?ask=&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.
