Device Triggers are used when a trigger action is based on information being collected from sensors on the production floor.  

Using Triggers, you can add external devices from Tulip’s device list to apps. Additional conditions can be added to the trigger based on the data collected from the device.

In general, Tulip recognizes three types of device events that trigger an action:

  • A simple device signal (e.g. barcode scanner output)
  • A GPIO signal (e.g. pin changes)
  • An Analog to Digital (ADC) event (e.g. change in voltage) 

Device output can be stored in variables, initiate a specific action or do both.

Note: A device output might be a single value (e.g. a number) or multiple values (e.g several analog outputs). When you create logical conditions with device outputs, use the variable data and not the variable name.

To complete a trigger you may create a condition, but always need to create an action. In general you can use the device activation to initiate actions (e.g. go to a specific step), to save the output data as a variable or to do both. 


See this guide to the Ohaus scale to get an example of a device trigger.

Did this answer your question?