> 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/safety-circuit.md).
# Safety Circuit
The last of the five options under Troubleshooting is Safety Circuit. The Safety Circuit page gives an illustration of the components within the safety circuit and their status.
Again, this screen will look slightly different from dryer model to dryer model given the components that are equipped or not equipped on the dryer. From this page, Control Power can be turned on or off, just as it can be from the Control Page. However, if the safety circuit is not satisfied, Control Power will not be able to be turned on.
Components with green globes next to them indicate components that are good and satisfying that part of the safety circuit. However, if a globe next to the component appears grayed out as opposed to green, that indicates that there is a break in the safety circuit at that particular component. Furthermore, if there is an issue with a component, all components downstream will appear grayed out as well. It is best to check the component that is first in line where the globe is gray. For instance, if the motor overloads are grayed out, the high limits and linear limits (if equipped) will appear grayed out as well. First start troubleshooting the motor overloads, which are upstream from the High Limits and Linear Limits. It is very likely once the issue with the motor overloads are solved, the all other components downstream will glow green as well, satisfying the safety circuit. If not, move on to the next grayed out component downstream and troubleshoot.
---
# 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/safety-circuit.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.
