Phase Template: close-valve¶
Close a modulating control valve (write 0 to its command). It is the
counterpart to open-valve, a single-action building
block for composing custom recipes one device move at a time.
Where to find it¶
System endpoint → Equipment Library → Phases → select close-valve.
graph TD
Start([initial]) --> EX["execute<br/>target_valve.CMD := 0"]
EX --> Done([done])
See Phases for the diagram conventions.
What you see when it runs¶
| Element | Meaning |
|---|---|
| Active step | execute — the phase completes as soon as the write is issued |
| Bound modules | The concrete control-module instance the target_valve role resolved to |
HMI screenshot pending
An annotated capture of a running close-valve phase will be
added here.
Parameters¶
The template declares no parameters. Closing is always a write of
0 to the valve command.
Required control modules¶
| Role | Module type | Description |
|---|---|---|
target_valve |
analog-control | Valve to close |
Capability: reaction.
How it works¶
The phase has a single execute step. It writes 0.0 to
target_valve.CMD and the phase completes. The stopping, aborting,
and resetting charts repeat the close (idempotent). The holding and
restarting charts are deliberate no-ops, because the valve is already
in its safe state.
This is a single-action phase. It verifies nothing. Pair with a deviation alarm on the valve if a failed close matters. For an isolation that gates product safety, build a feedback-gated phase instead.
Used in recipes¶
No shipped reference recipe uses this template. It is a building block for composing your own.
Try it¶
- System endpoint → Recipes → create a draft recipe pairing
an
open-valvestep with aclose-valvestep on the same unit (e.g.target_valvebound tor1-solvent-valveonreactor-1) - Approve and start it from HMI endpoint → Batch Execution
- Watch the bound valve's faceplate:
CMDmoves to the open position, then back to0
Modify this template¶
Want to clone this and adapt it for your own equipment? Walk through Adaptation Guide for the full clone → rebind → deploy → run workflow, and Parameter Binding to understand how recipe values flow through to control-module tags.