> For the complete documentation index, see [llms.txt](https://infosys.selmotech.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://infosys.selmotech.com/selmo-solution/selmo-solution-en/selmo-structure-and-standard/selmo-technical-standard-and-structure/description-selmo-plc-code/hardware-zone-control.md).

# Hardware zone control

This section relates to the status of the associated sequences i.e. whether they are all in the manual mode or in the automatic mode of the zone. A zone automatic output is also used to start all associated sequences that are in automatic mode when an automatic-start button for that zone is pressed.

Each hardware zone contains a continuously monitored zone (T.C.M.Z.). A continuously monitored zone is an area of the PLC software that contains logic which is continuously monitored. Emergency-stop buttons, circuit breakers, safety doors, etc. should be located in this area of the program.

The T.C.M.Z. contains faults that apply to more than one sequence to prevent these faults from appearing redundantly in every sequence.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://infosys.selmotech.com/selmo-solution/selmo-solution-en/selmo-structure-and-standard/selmo-technical-standard-and-structure/description-selmo-plc-code/hardware-zone-control.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.