---
title: "Using Edge IO to Run OPC UA"
slug: "using-edge-io-to-run-opc-ua-1"
updated: 2024-07-15T18:15:23Z
published: 2024-07-15T18:15:23Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.tulip.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Use edge devices to run on prem connector host

*Run your On Prem Connector Host on an Edge IO.*

The On-Prem Connector Host is a service that lives within your network that proxies trafic to the Tulip cloud for data that is not accessible to the broaded internet. More details on the OPCH are available here: [Overview of On-Premise Connector Hosts](/r230/docs/overview-of-on-premise-connector-hosts)

Running this on your Edge Device will significantly reduce your time to value, simplifying the infastructure required to run this service.

## Preparation

First, make sure your:

- Edge Device is fully [set up](https://support.tulip.co/docs/setting-up-an-edge-io) and [registered](https://support.tulip.co/docs/how-to-register-an-edge-io)
- OPC UA server or MQTT broker is set up

## Creating Machine Data Source

1. Head over to the **Machine** page on your Tulip account.

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Using%20Edge%20IO%20to%20Run%20OPC%20UA_403289431.png)

1. On the **Machine** page, select the dropdown to locate the **Machine Data Sources** option.

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Using%20Edge%20IO%20to%20Run%20OPC%20UA_403287310.png)

1. In the top right, select **Create Connector**.

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Using%20Edge%20IO%20to%20Run%20OPC%20UA_403288747.png)

You can fill out your OPC UA data as described in [this article](https://support.tulip.co/docs/how-to-build-your-first-opc-ua-connector) However, instead of running on the Cloud Connector Host; you can run on your Edge IO. The final configuration might look something like this:

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Using%20Edge%20IO%20to%20Run%20OPC%20UA_403291512.png)

## Further Reading

- [Intro to Machine Monitoring](https://support.tulip.co/docs/intro-to-machine-monitoring)
- [How to Create Your First Machine Trigger](https://support.tulip.co/docs/how-to-create-your-first-machine-trigger)

---

Did you find what you were looking for?

You can also head to [community.tulip.co](https://community.tulip.co/?utm_source=intercom&utm_medium=article-link&utm_campaign=all) to post your question or see if others have faced a similar question!

**Machine**

A **Machine**is a digital representation of a physical datasource. Machines have **Attributes**that are updated through an OPC-UA Connector or the Tulip API.

**Connectors**

**Connectors** enable real-time connectivity between your Tulip solution and a transactional system (e.g. an ERP). The output of a Connector Function can be used in Tulip Apps, Automations, and Functions.

- **HTTP Connectors** utilize HTTP API endpoints.
- **SQL Connectors** can enable connectivity with certain SQL databases.
- **MQTT Connectors** can connect to MQTT brokers for machine monitoring.

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/connector.gif)

**Connector Host**

Tulip **Connector Hosts**are designed to allow your Tulip Apps to interface with external systems such as databases, APIs, and machines. **On-Prem Connector Hosts**sit within your network and allow Tulip to interface with SQL databases and APIs that aren't accessible to the cloud.

**Edge IO**

**Edge IO** is a Tulip-developed **Edge Device**. Interface with digital inputs directly from **Triggers**, flip digital outputs, run **Node-RED**flows, and more!

**Edge IO**can also act as a **Connector Host**or OPC-UA Broker