Learn how to set up triggers that integrate devices on the production floor.
"Device Triggers" are triggers that fire when an event happens in a sensor on the production floor that is connected to Tulip.
How to Add Device Triggers
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.
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:
Example Device Trigger
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
- Barcode Scanner (Dataman TCP)
- Barcode Scanner (Dataman 262)
- Bobe Box USB
- Bosch RFID
- Caliper or Depth Gauge
- Cognex Insight 2000
- Fluke 28x Multimeter
- Ingersoll Rand QX
- Omega HH806
- Pam CF
- Scale (Brecknel PS25)
- Scale (Brecknel 7010SB)
- Scale (Ohaus)
- Stealth Switch
- Temperature / Humidity Sensor (Lascar)
- Temperature / Humidity Sensor (Phidgets)
- Temperature Gun
- Torque Open Protocol
- USB Button
- 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.