The scope of this article consists of infrastructure sequence diagrams between the Tulip platform components and Tulip machines connected via Machine data sources.
Audience:
Tulip solution developers
I.T. engineers
The purpose of this article is to inform the audience of their Tulip solution's dependencies on:
reliable connectivity to Tulip cloud infrastructure
performant and reliable local network infrastructure
reliability and performance of connected systems
Tulip-Internal Latency - As a back-of-the-napkin approximation, assume each instance of 'Tulip-Internal Latency' is approximately 100 milliseconds.
Tulip App Machine Trigger with Machine Data Source connected via On-Premise Connector Host (OPCH)
Tulip Automation triggered by Machine with Machine data source connected via OPCH
Did you find what you were looking for?
You can also head to community.tulip.co to post your question or see if others have solved a similar topic!
Machine Data Source
A Machine Data Source is a connection configuration that enables Machines to receive real-time data from physical equipment. Machine Data Sources use protocols like OPC-UA or MQTT to connect to PLCs, sensors, and other industrial equipment, mapping their data to Machine Attributes in Tulip.
ex. An OPC-UA Machine Data Source connects a CNC mill to Tulip, streaming spindle speed and feed rate data.
On-Premise Connector Host (OPCH) Tulip Connector Hosts are designed to allow your Tulip Apps to interface with external systems such as databases, APIs, and machines.
On-Premise Connector Hosts (OPCH) sit within your network and allow Tulip to interface with SQL databases and APIs that aren't accessible to the cloud.
