Machine triggers interpret events from Machine Attributes to set the Machine State and manipulate values in the Activity History for a machine. Triggers wait for events to fire then they check various values and compare them inside clauses to determine whether to perform actions. Machine Triggers are a component of a Machine Type and can be deleted by removing from the Machine Type or by deleting directly while editing the trigger.
Name | Description |
---|---|
Event | The event that the trigger executes in response to. See below for possible events. |
Clauses | The logical operation the trigger performs before deciding if it should execute an action in response to the event. See below for possible clauses. |
Values | Existing data inside the Tulip system. An example value could be: "if the Tulip variable X is greater than 3" where X is the value. See below for possible values. |
Actions | What the trigger does. Many actions are possible in the Tulip system. See below for possible actions. |
An event can result from multiple sources. Possible sources and examples below:
Source | Example |
---|---|
A machine outputs any attribute | When machine outputs any attribute |
A machine outputs a specific attribute | When machine outputs specific attribute spindle speed |
Time Interval | Every 30 seconds |
Clauses allow users to define a series of boolean logic expressions (if/then statements) that must all evaluate to true before a given action is performed in response to a trigger event. A user can define a series of comparisons and then decide to execute a number of actions if any the statements evaluates to true of if all of the statements evaluate to true.
Values can be any data-store that is maintained in the context of a machine. Values can come from a number of sources, including:
ID | Name |
---|---|
QA-T256 | Machine Monitoring : 04 - Machine Type |
QA-T783 | Machine Monitoring : 19 - Copy/cut/paste machine type triggers |
QA-T1140 | Machine Monitoring : 11 - Activity fields |