> 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-how-it-works/selmo-training/chapter-3-the-advanced-standard-functions-in-selmo/3.3-mxic-manual-cross-interlock-in-manual-operation.md).

# 3.3 MXIC – Manual Cross Interlock in manual operation

#### Motivation

In manual operation, operators can trigger individual movements manually.\
But what happens when two axes depend on each other?\
What if a cylinder is extended while the other is still in the work area?

To prevent such conflicts, the **MXIC – Manual Cross Interlock**.

#### Principle of operation

Every zone that can be operated manually has a **button connection**.\
This button stands for manual operation – e.g. *"Cylinder 1 extend".*\
When the operator presses the button, Selmo automatically checks the conditions of other zones:\
Is Cylinder 2 retracted?\
Is no safety interlock active?

* If all conditions are met → the movement is allowed.
* If a condition is violated → the movement is blocked, and the reason appears on the HMI.

#### Example

A classic example is the interlock of two cylinders:\
Cylinder 1 may only extend if Cylinder 2 is to the rear.\
In the MXIC editor of Zone 1 the following is stored:\
*"Enable Button = Cylinder 2 Rear = TRUE"*\
If violated, no output is set; instead the HMI shows:\
*"Blocked – Cylinder 2 not retracted."*

#### Effect

MXIC turns manual operation from an unsafe test mode into a **controlled, traceable operating state.**\
The operator knows why something does not work, and the machine always remains in a safe state.

<figure><img src="/files/7fb0dba3b7de07a17798c5d20d737bad42429257" 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 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-how-it-works/selmo-training/chapter-3-the-advanced-standard-functions-in-selmo/3.3-mxic-manual-cross-interlock-in-manual-operation.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.