Arming and Manual Override

Arming

1. Nothing arms itself. Power-up, a preset change, a terminal reconnect and leaving test or config mode all leave every tile disarmed.
2. There are two ways to arm: tap the tile on the AUTO page, or press the AUX-N "Arm Auto" function you assigned to an armrest or joystick button.
3. Arming can start movement immediately. If a FOLLOW sensor is already active when you arm it, its outputs engage at once. The tile turning green is the cue.
4. Armed states are never saved. After a power cycle everything is manual again.

Manual Always Wins

The moment you use a manual control that overlaps an armed tile, that tile is disarmed. This is called kick-out.

All of these count as manual control:

• A joystick or AUX-N button press
• An AUX-N toggle, switched on or off
• A screen button, momentary or toggle
• The TEST function in config mode
• Manual control from the web interface

Three things follow from that:

• Automation never resumes by itself. Re-arming is always a deliberate press.
• Manual control is never blocked, limited or delayed by the automation, including BLOCK and INTERLOCK. Manual is manual, auto is auto.
• Manual controls that do not overlap an armed tile change nothing. Working a function the automation is not running leaves the automation alone.

Shared Service Channels

Some machines run everything through one common valve, such as a hydraulic dump or enable valve. Without a way to say so, touching that valve by hand would cancel every automatic function on the machine, because every tile overlaps it.

Mark that channel as SERVICE. Manual use of a service channel then no longer cancels unrelated automation. Only the tile whose own channels you touched is disarmed.

• A marked channel shows amber on the setup page and carries a * after its label, for example CH8*.
• The mark is stored per preset and applies machine-wide.
• One honest limit: a manual button that drives only service channels cannot be attributed to a single tile, so it still disarms every overlapping tile.

Interlock

A tile can be set to INTERLOCK. If two of that tile's sensors demand movement at the same time, for example both the lift and the lower proximity sensor, the outputs drop immediately and nothing moves until they disagree again.

That is a pause, not a fault. When the conflict clears, the surviving demand takes over automatically. Nothing needs resetting.

A tile that is armed but deliberately not moving shows amber, whether that is an interlock conflict or a MAX ON trip.

INTERLOCK protects the automation. It does not stop the operator driving either channel by hand.

STOP

The STOP soft key, or the AUX-N STOP function, is a latched interlock.

• Press once and all outputs are forced off and held off. No source can energize a relay: not the automation, not a screen button, not even a physically stuck input.
• Press again to release.
• After releasing STOP nothing resumes on its own. A button still held across the release has to be let go and pressed again.
• STOP also disarms every tile.

STOP is an operator interlock, not an emergency stop, and it is separate from the ISOBUS bus-wide stop.

When Automation Stops on Its Own

The 10 second window on terminal loss is deliberate. Terminals pause their status messages for several seconds during normal redraws, and a shorter watchdog would cut outputs mid-work on a perfectly healthy connection.

Relay Protection

Two hard floors apply to every automation-driven switch, and no setting can defeat them:

• 100 ms minimum ON time
• 100 ms minimum rest before re-engaging

Worst case from the input side is therefore five switching cycles per second.

Neither those floors nor your MIN ON setting ever delay an OFF for safety reasons. STOP, a BLOCK input, an interlock conflict, kick-out, a preset load and connection loss all release the relay immediately.