"Device Triggers" are triggers that fire when an event happens in a sensor on the production floor that is connected to Tulip.
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.
They can be accessed from the ""Machines and Devices" option in the "Step" tab of the Context Pane:
Here's an example:
"device" "barcode scanner" outputs at "this station"
"Data Manipulation" "Store" "Device Output" "data" location: "new_variable"
List of All Device Triggers
Here's a list of all device triggers that are available by default in Tulip. These are available under the "When" option in the Trigger Editor:
Analog Voltage Input
Barcode Scanner (Dataman TCP)
Barcode Scanner (Dataman 262)
Bobe Box USB
Caliper or Depth Gauge
Cognex Insight 2000
Fluke 28x Multimeter
Ingersoll Rand QX
Scale (Brecknel PS25)
Scale (Brecknel 7010SB)
Temperature / Humidity Sensor (Lascar)
Temperature / Humidity Sensor (Phidgets)
Torque Open Protocol
Serial Barcode Scanner
See this guide to the Ohaus scale to get an example of a device trigger.
Here's how to use the "Dataman TCP" driver
Here's how to use Torque Tool Open Protocol in Tulip.