How To Articles > How to Transfer Data from MQTT to Azure IoT

How to Transfer Data from MQTT to Azure IoT

Open Automation Software can be used to transfer data from MQTT devices to an Azure IoT hub, locally or over a network. This tutorial walks you through downloading and installing OAS, configuring an MQTT and an Azure IoT driver, configuring MQTT and Azure IoT tags and implementing Data Route.

Step 1. Download and Install the Open Automation Software and Start the OAS Service

If you have not already done so, you will need to download and install the OAS platform. Fully functional trial versions of the software are available for Windows, Windows IoT Core, Linux, Raspberry Pi and Docker on our downloads page.

On Windows run the downloaded Setup.exe file to install one or more of the Open Automation Software features. Select the default Typical installation if you are not sure what features to use or the Custom installation if you want to save disk space on the target system. When prompted agree to the End User License Agreement to continue the installation.

For more detailed instructions and video tutorials, visit the installation guide for your system:
Windows Installation | Linux Installation | Raspberry Pi Installation | Dockers Installation

When the installation is finished the OAS Service Control application will appear. Use this application to start the 4 Services. If this is the first time installing the software it will automatically enter Runtime with an example Tag Configuration.

Step 2. Configure Your MQTT Data Source

First, you will need to open the Configure OAS application from the program group Open Automation Software.

Select Configure >> License from the top menu and verify that MQTT is one of the available Drivers in the lower left of the form. The demo license will have this by default. If you do not see MQTT available, contact support@openautomationsoftware.com to update your license.

Select Configure >> Drivers from the top menu.

Select localhost or the remote service you wish to modify with the Select button to the right of the Network Node list.

The Configure Drivers Screen will appear. Select MQTT from the Driver dropdown box.

Enter a meaningful Driver Interface Name that you will refer to this physical connection when defining Tags with a MQTT Data Source.

Enter the IP Address of the broker. The default port is 1883.

Enter the User Name and Password if required.

Set the Keep Alive Time. The default is 60 Seconds.

Set the Reconnect Time. The default 10 Seconds. If the connection to the broker is lost the Reconnect Time determines how long to wait before attempting to reconnect.

For more detailed instructions on configuring your MQTT data source, click here to see our Getting Started MQTT tutorial or watch the video tutorial below:

Step 3. Configure Your Azure IoT Data Source

First, you will need to open the Configure OAS application from the program group Open Automation Software.

Select Configure >> License from the top menu and verify that Azure IoT is one of the available Drivers in the lower left of the form. The demo license will have this by default. If you do not see Azure IoT available, contact support@openautomationsoftware.com to update your license.

Select Configure >> Drivers from the top menu.

Select localhost or the remote service you wish to modify with the Select button to the right of the Network Node list.

The Configure Drivers Screen will appear. Select Azure IoT from the Driver dropdown box.

Enter a meaningful Driver Interface Name that you will refer to this physical connection when defining Tags with an Azure IoT Data Source.

Enter the Azure IoT Device ID you want to use.

Enter the Azure IoT Connection.

Enter the Azure IoT Hub URL.

Select the preferred Azure IoT Transport. Typically it is AMQP.

Click the Add Driver button above the Driver list in the left pane to add the Driver Interface as an available selection when defining Tags in the next step.

For more detailed instructions on configuring your Azure IoT data source, visit our Getting Started Azure Iot Data Hub tutorial or watch the video tutorial below:

Step 4. Configure Your MQTT Tags

OAS provides multiple ways to add and define tags:

Manually add and define Tags using the Configure OAS application. …learn more…
CSV Import and Export …learn more…
Programatically …learn more…
One Click Allen Bradley …learn more…
One Click OPC …learn more…

To add a Tag manually:

In the OAS Configure Application, select Configure >> Tags from the top menu.

Select localhost or the remote service you wish to modify with the Select button to the right of the Network Node list.

Click on the Add Tag button located at the top of the Tag browser on the left portion of the screen.

A dialog box will appear. Enter a name for your new tag and click ok.

A configuration screen will appear for your new tag. Select your data source type in in the Data Source dropdown box.

Specify the correct data type in the Data Type dropdown box.

Click Apply Changes at the bottom right of the window.

For more detailed instructions on configuring your tags, click here to see our Getting Started Tags tutorial.

Step 5. Repeat Step 4 with Your Azure IoT Tags

Step 6. Configure the Target Tab of the Source Tags

Select one of your source tags.

Select it’s Target tab.

Enable Write to Target

Select the Target Type (Tag, OPC, Azure IoT, Azure IoT Edge, or MQTT) from the dropdown.

Select the destination for the value to be sent. If Tag is selected then select Browse and select the desired tag from the localhost system or optionally a remote system for transfer over a network.

Local: TagName.Value

Remote: \\192.168.0.1\TagName.Value

If OPC Item is selected select browse and select the OPC Server and Item

If Azure IoT is selected then select the Driver Interface.

If MQTT is selected then select the Driver Interface and Topic.

Enter the desired float value Deadband field. Enter 0 for no deadband.

If you want to specify a desired update frequency for the target check Write Continuously and enter the desired frequency. If Write Contentiously is unchecked the the target will be updated every time the source tag changes.