---
title: "Use Edge Devices as a machine data source"
slug: "use-edge-devices-as-a-machine-data-source"
updated: 2022-12-13T21:24:11Z
published: 2022-12-13T21:24:11Z
canonical: "support.tulip.co/use-edge-devices-as-a-machine-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.

# Use Edge Devices as a machine data source

*Learn more about using Tulip Edge Devices as a native Machine Data Source in Tulip*

As of OS50, Tulip Edge Devices can now be used natively in Tulip as a Machine Data Source. In this article, we describe the steps needed to acquire a compatible Tulip Edge Device and set it up as a Machine Data Source. Once complete, you will be able to create custom tags in Node RED and map them to Machine Attributes.

#### Step 1: Purchase a Tulip Edge Device with Node-RED

Both Edge IO and Edge MC support Node-RED.

To learn more about the differences between these device, you can read more [here](https://tulip.co/products/edge-devices/).

To buy an Edge Device, you can follow the links here:

- [Buy Edge IO](https://tulip.co/products/buy-edge-io/)
- [Buy Edge MC](https://tulip.co/products/buy-edge-mc/)

#### Step 2: Set up your Edge Device

Next, you will want to physically set up your Edge Device and register it to your Tulip account.

Edge IO:

- [Setting up Edge IO](https://support.tulip.co/docs/setting-up-an-edge-io)
- [Register your Edge IO](https://support.tulip.co/en/articles/5648114-how-to-register-an-edge-io)

Edge MC:

- [Setting up Edge MC](https://support.tulip.co/en/articles/3996151-setting-up-an-edge-mc)
- [Register your Edge MC](https://support.tulip.co/en/articles/4840687-how-to-register-an-edge-mc)

**Step 3: Enable Node-RED**

[This article](https://support.tulip.co/en/articles/5648044-using-node-red-with-edge-io) describes how to enable Node-RED on your Edge Device and log into the Node-RED editor. Note that the steps are the same for Edge IO and Edge MC.

#### Step 4: Create Tulip Tags and map to Machine Attributes

At this point, you should be ready to configure your Edge Device as a data source in Node-RED!

[This article](https://support.tulip.co/en/articles/how-to-send-data-to-machines-from-edge-devices-using-node-red-and-tulip-tags) walks though how to configure your Node-RED flow to have custom tags, view the Edge Device as a data source in the Machines page, and map the tags to attributes.

If you do not see the Tulip Tag node, you may need to upgrade the device firmware to OS50 or greater. Check out [this article](https://support.tulip.co/en/articles/3320836-how-to-manage-gateways-within-tulip) for instructions on how to update to the latest firmware release.

**Edge Devices**

**Edge Devices** are any hardware intended to connect physical things to the cloud. This can include entirely mechanical devices, older machines without network functionality, PLCs, and more.

Tulip sells the **Edge IO** and **Edge MC** that interface directly into **Triggers** in a breeze, but Tulip can also support other Edge Devices.

**Node-RED**

**Node-RED**is an open-source flow-based logic language that runs natively on **Edge IO**and **Edge MC.**The Node-RED community has developed 3500+ libraries to interface with just about anything!

**Machine Attribute**

**Machine Attributes**are setpoints and actual values for different parameters of your **Machine.**Attributes can be mapped to OPC-UA datasource Tags.

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

**Edge IO**

**Edge MC** is a Tulip-developed **Edge Device**. run **Node-RED**flows on dedicated hardware with built-in security and stability.

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

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