Conditions in StateTick
A condition is a named boolean expression — a reusable rule like “the motor is running and not overloaded.” You build it from terms joined by operators, with NOT and parentheses for grouping, then reuse it across your control logic and map it to real hardware in a composite.
What is a condition?
A condition lives on the Generic Composer → Conditions page. Each one has a Name and an IF expression — an ordered list of terms and operators. A read-only Summary shows the whole expression as IF( … ).
Zoomed in, the editor is a Name, the IF expression built from term boxes and operators, and the Summary:
AND operator dropdown, delete buttons, and the Summary.Each term is a small box — a variable reference (equipment signal or global), a literal, or a placeholder function like a rising edge. You add a term with + and pick what it references from the Variable Picker. Operators (AND, OR, comparisons) sit between terms.
This guide, page by page
Terms →
Add terms from equipment signals and global variables, plus literals and comparisons.
The Variable Picker →
Every category the picker offers — equipment, globals, edges, aggregates, state, timers, queues.
Placeholders →
Rising/falling edges, value changes, array aggregates, composite state, timers.
Operators & Grouping →
AND/OR, comparisons, NOT, and wrapping terms in parentheses.
Composite Instances →
Map each generic term to a concrete equipment instance in a composite.
Full Example →
Build a condition end to end and map it onto a real machine.
Try it in StateTick
Build reusable conditions once, then map them to real hardware in every machine you design.
Get Started →