> 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/less-than-hwzone_name-greater-than/less-than-hwzone_name-greater-than_control/gate-fortress-fault-detect.md).

# Gate/Fortress fault detect

The following PLC code is used to check the T.C.M.Z for gate faults. To allow manual movement with gates open, the Gate Fortress Fault output must be inhibited. This is accomplished by using the confirmation of the opened safety door (from the previous PLC code) to mask the Gate Fortress Fault signal that is sent to all sequences within the zone in which a manual function is being performed.

Copy

```
// Gate/Fortress Fault Detect
   {region "Description Gate/Fortress Fault Detect"}
   (*
   The following plc code is used to check the TCMZ for gate faults.
   In order to allow manual movement with gates open, it is necessary to inhibit the gate fault output. 
   This is achieved by using the zone confirm flags (from the previous plc code) to mask the TCMZ gate/fault signal sent to all sequences within the zone in which a manual function is being actioned. 
   *)
   {endregion}
    
   GVL_<HwZone_name>.stHwzIf.xGateFortressFaultTcmz := GVL_<HwZone_name>.stHwzIf.xGateFortressFault AND NOT GVL_<HwZone_name>.stHwzIf.xGateSectionConfirm;
```

<\*\*\*>Variable name, comment and data type are automatically taken from the Studio

<br>


---

# 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/less-than-hwzone_name-greater-than/less-than-hwzone_name-greater-than_control/gate-fortress-fault-detect.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.