Data Ops
Integrate with your existing systems
Capture machine attributes by connecting Tulip to your OPC UA server or your MQTT broker with pre-built connectors to Highbyte, Litmus, HiveMQ, etc.
Edge connectivity. Self-service, fast, customizable.
More integrations. Lower cost. Infinite possibilities. All with Tulip’s connectivity options and edge devices.
Data Ops
Capture machine attributes by connecting Tulip to your OPC UA server or your MQTT broker with pre-built connectors to Highbyte, Litmus, HiveMQ, etc.
Device drivers
Connect USB devices and torque controllers directly to your work stations with device drivers. No additional edge devices required.
Powerful machine monitoring and connectivity with USB, GPIO and ADC. $600
Wireless connectivity with USB, Node-RED, and native OPC UA. $150
Connect any machine to the cloud with current sensors to integrate real-time utilization data into your operations. $375
Configurable LED light strips for pick-to-light, place-to-light, and more. Requires Edge MC or Edge IO. Edge IO comes with the ability to connect up to 2 light strips.
Spend less time configuring, and more time solving problems. No coding required.
Connect the machines, devices, sensors that matter to break down silos and create a unified operation
Integrate specialized, legacy, or innovative equipment with advanced capabilities
Not always. USB devices (scanners, calipers, scales) connect directly to your computer or tablet with Tulip's device drivers. Edge devices are for machines, sensors, wireless placement, and protocols your PC can't reach.
Edge IO enables high-frequency vibration and current monitoring with 3rd party sensors via the ADC input. Edge IO also has inputs for GPIO, break beam sensor support, and two integrated light strip channels. Edge MC is smaller and covers a subset of options Edge IO offers, including USB devices, OPC UA, Node-RED, serial, and TCP/IP.
The I/O Gateway is no longer available for purchase. Edge IO is its replacement and covers the same OPC UA, sensor, GPIO, and light kit use cases.
Three steps: add the machine connection, standardize its attributes so data reads the same across sources, then define the attributes and machine states you want on your dashboards.
Yes. Machine attributes, machine states, and downtime reasons are all configurable, even across machines using different protocols.
Yes. OEE and OPE both, with real-time dashboards and equipment status views. Because you can combine machine data with operator context, you can go beyond OEE to explain why a number moved.
Node-RED is low-code, flow-based programming built into Tulip's edge devices. You don't need it for supported devices and machines; it's there when you want to reach something custom.
Yes. Any device event or measurement can fire a trigger, so apps can advance a step, flag an out-of-spec reading, or light a bin automatically.
Yes. Tulip's platform includes enterprise-grade security and GxP validation features that extend to edge-collected data.
Yes. Light Kit connects to the platform through an Edge MC or an Edge IO. Edge IO can also drive up to two light strips directly, without the Light Kit device.
Up to eight, across eight channel outputs. Additional strips are available in 1m × 30 LED (THLS130), 1m × 60 LED (THLS160), and 2m × 60 LED (THLS260) configurations.
The set up of the light kit is straightforward, without any coding. Set bin size, color, and behavior, and then connect the lights to your apps with triggers. Ready-made pick-to-light apps are available in the Tulip Library.
Tulip edge devices are built for industrial environments, are device and software agnostic, and stay in lockstep with platform releases, so your software won't outgrow your hardware.