---
title: "Build your first OPC UA data source"
slug: "build-your-first-opc-ua-data-source"
updated: 2024-09-18T16:31:27Z
published: 2024-09-18T16:31:27Z
canonical: "support.tulip.co/build-your-first-opc-ua-data-source"
---

> ## 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.

# Build your first OPC UA data source

*Use this guide to learn how to bring OPC UA tags into Tulip*

**In this guide, you will learn:**

- **How to set up an OPC connector in Tulip**

If you have a functioning OPC UA server with tags that you would like to connect to Tulip, then you are ready to set up an OPC UC connector and create your first machine monitoring app.

## Setting Up An OPC UA Connector

          OPC UA Server Compatibility

          

OPC UA Servers differ in their implementation of the OPC UA spec. Tulip has been built for complete compatibility with PTC Kepware-compliant OPC UA servers, and may only support a subset of functionality for other OPC UA servers.

OPC UA servers implemented directly by PLCs often implement unique signatures for their OPC UA servers. Kepware has invested the time to build implementations to each of these server specs. [Learn more](https://www.ptc.com/en/products/kepware).

First, click into the **Machines** option under the **Shop Floor** tab on the Menu Bar.

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/How%20To%20Build%20Your%20First%20OPC%20UA%20Connector_194984052.png)

Then, click **Machine Data Sources** from the dropdown in the top left.

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/How%20To%20Build%20Your%20First%20OPC%20UA%20Connector_194984570.png)

Then, click **Create Connector** from the Machine Data Sources page.

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/How%20To%20Build%20Your%20First%20OPC%20UA%20Connector_194985045.png)

Name your Connector and hit **Save**.

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/How%20To%20Build%20Your%20First%20OPC%20UA%20Connector_462401069.png)

Then click the new connector from the list of OPC UA connectors.

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/How%20To%20Build%20Your%20First%20OPC%20UA%20Connector_462401712.png)

## Configuring the OPC UA Connector

After that, you will have 4 new fields to fill in:

- Running On
- Agent URL
- Security Mode
- Authentication Method

### "Running On" Field

For the **Running On** field, choose **Cloud Connector Host** unless you have a special setup that you have discussed with a Tulip representative.

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/How%20To%20Build%20Your%20First%20OPC%20UA%20Connector_462402840.png)

### Agent URL Field

For the **Agent URL** field, you should have a local TCP server with an IP address and port. If you are using a service like Kepware, this will be exposed in the UI. For example:

`opc.tcp://192.164.54.1:49320`

Then, if your server is local, you will need to add a redirect so that cloud services can access this IP address. Here’s an example of a redirect that is accessible in the cloud:

`207.172.213.113/opc:40534`

Depending on the OPC UA endpoint available at the indicated server, configure the **Security Mode** and **Authentication Method** fields.

### Security Mode field

Choose a Security Mode. Pick either **Sign** or **Sign&Encrypt** to sign or sign and encrypt the connection made between Tulip and the OPC UA server living at the indicated Agent URL.

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/How%20To%20Build%20Your%20First%20OPC%20UA%20Connector_462405531.png)

If choosing either **Sign** or **Sign&Encrypt**, you must then choose a **Security Policy** and provide both a **Private Key** .pem file and a **Certificate** .pem file in the text boxes that appear below:

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/How%20To%20Build%20Your%20First%20OPC%20UA%20Connector_462407597.png)

### Authentication Method field

Choose an **Authentication Method**. The **Anonymous** method opens a session on the OPC UA server without authentication. The **UserName** method authenticates a given user via the provided **Username** and **Password** fields.

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/How%20To%20Build%20Your%20First%20OPC%20UA%20Connector_462410779.png)

Similarly, you can generate a certificate and private key pair of .pem files for a user on your OPC UA server, select the “X509” method, and provide them in the “Certificate” and “Private Key” text boxes to authenticate.

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/How%20To%20Build%20Your%20First%20OPC%20UA%20Connector_462412634.png)

### Testing your Connection

Hit “Test” to see if you can successfully connect to the server.

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/How%20To%20Build%20Your%20First%20OPC%20UA%20Connector_462413977.png)

If the test is successful, then you are ready to set up a machine. Click "Save", and then go to the "Machine Types" page to set up your first category of machines.

---

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!

**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)

**Shop Floor**

The area of the platform responsible for moving applications into production. Under the shop floor, you can manage **Stations**, **Edge Devices,** and the app publication details such as which **Version** is accessible to users, which **Devices** are connected to the app, and which **Interface (display device)** the app is run on.

**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.