Control Solutions’ Babel Buster MQ-61 Modbus to MQTT Gateway turns any Modbus device into a Thing on the Internet of Things. Gain instant access to a wide range of machine learning and AI capabilities, a wide range of data storage and analytics, and a variety of event handling and notification capabilities.

The MQ-61 includes everything necessary to connect to Amazon Web Services (AWS) IoT support using MQTT. Once the IoT connection is made, your Modbus data can make its way to an AWS database, AWS notification services (e.g. email alerts), and a variety of analytics tools including QuickSight which makes it quite easy to quickly graph your data.

The Babel Buster MQ-61 Modbus to MQTT gateway will poll one or more Modbus RTU and/or Modbus TCP devices, collecting data from the list of registers you provide. Based on rules you create, the MQ-61 will decide if and when to publish that data to the MQTT broker (server). You can also configure the MQ-61 MQTT client to subscribe to data coming from the MQTT broker, which you can then write out to Modbus devices to manage setpoints and the like.

MQ-61 Modbus IoT Gateway data flow

Feature Highlights
• MQTT Client supporting AWS IoT Core
• Simple template based setup of MQTT Publish and Subscribe
• Modbus RTU RS-485 Master or Slave
• Modbus TCP Client and Server
• Local user programming with Script Basic
• Configure via secure web pages
• IPv4 and IPv6 support

Babel Buster MQ-61 Modbus to AWS IoT Gateway

Babel Buster MQ-61 Modbus to MQTT IoT Gateway

Order code: MQ-61
List price: $524.00
Retail price: $419.00

 Buy MQ-61 Online Now!

 Save Even More
Sign Up for Wholesale

Babel Buster MQ-61 is an AWS Qualified Device


Allow Any Modbus Device to Play as a "Thing" on the Internet of Things!

The MQTT “publish” action in the Modbus to MQTT gateway, in controls terms, is most closely associated with sensors. Your hardware has collected sensor data, and you want to send that sensor data to a server or to other control devices. To send that data, you “publish” it to the MQTT broker.

The MQTT “subscribe” action, in controls terms, is most closely associated with actuators. The “subscribe” action would also be associated with control setpoints. You can never force data into a device via MQTT. The device, in our case the MQ-61, must subscribe to the source of data effectively asking to be informed of changes. Once you have subscribed to an MQTT source of data, then when received, you can use that data to control actuators or update setpoints.

The MQ-61 Modbus to MQTT IoT Gateway is capable of more than just transferring data between Modbus devices and the MQTT broker. It includes Script Basic built in to provide easy-to-use local programming for data analysis and local decision making. This capability is referred to as Edge Computing in IoT terminology.

One of the many things you can do with data that has been published to the AWS MQTT broker by the Babel Buster MQ-61 is analyze and visualize the data. The graph illustrated above represents data published by an MQ-61, and the steps taken to get this graph - without writing any program code - are outlined in the user guide.

The data flow in the MQ-61 Modbus to MQTT gateway is illustrated below. Data is collected from Modbus devices by the Modbus engine which stores that data in local registers or data objects. The Modbus data is automatically updated on a continual basis. Meanwhile, the IoT engine is looking at its set of publish and subscribe rules to decide when to publish data from the local registers to the MQTT broker. These rules are also created by the user and data will be published according to the criteria set up by the user.

MQ-61 IoT Gateway internal data flow

The MQ-61 can be Modbus RTU master or slave (user selectable), and Modbus TCP client and server (concurrently). Maps created via templates in the MQ-61’s web UI will read and write other Modbus devices, copying their data to local registers when read, or sending data from local registers to those devices when written. Holding registers can be integer, unsigned integer, or IEEE 754 floating point, single or double precision. The MQ-61 also supports character strings as a series of registers having two ASCII characters per register.

MQ-61 Modbus to MQTT Gateway Easily Connects Your Modbus Device to Amazon Web Services

The MQTT publish and subscribe “rules” are created with an easy to use template in conjunction with setup on the AWS side. A diagnostic page is also provided where you may view the most recently published data, and publish arbitrary JSON formatted data for testing purposes.

Configuration screen shot from MQ-61 Modbus IoT Gateway

The MQ-61 allows the serial port to be used for a proprietary serial protocol instead of Modbus RTU. This effectively makes it a proprietary protocol to MQTT converter. When used for interpreting a proprietary protocol, a Script Basic program would be written to send and receive via the serial port as applicable, and interact with the local Modbus registers under user program control.

Modbus screen shot from MQ-61 Modbus IoT Gateway

Interface to a Modbus RTU alphanumeric display device has never been easier. The MQ-61 recognizes a series of Modbus holding registers as a single character string. The built-in Script Basic includes richly featured character string manipulation and recognizes the series of registers as a single character string.

MQ-61 interfaces to ASCII displays

Configuration of the gateway is done via the secure web pages served by the internal web server. You simply fill in templates. The entire configuration is saved in the internal Flash file system in XML format. This file may be exported to replicate additional copies of the configured device, or for backup.

Click the link below to view a demo copy of the entire Web UI in the MQ-61.

 MQ-61 Demo Web


MQ-61 Modbus to MQTT Gateway Features

• MQTT Client supporting AWS IoT Core "Out of the Box"
• Simple template based setup of MQTT Publish and Subscribe
• Modbus RTU RS-485 Master or Slave
• Modbus TCP Client and Server
• Modbus TCP over Ethernet 10/100BaseT
• Up to 2000 local registers
• 16, 32, 64-bit integer, 32 or 64-bit IEEE 754 floating point, Mod10
• ASCII character string support (UTF-8)
• Supports Modbus “coils”, input registers, holding registers
• Modbus register mapping configured via web interface
• Modbus (master) polling interval configurable per point
• Local user programming with Script Basic
• Configure via web pages, HTTP and/or secure HTTPS
• Flash file system for XML configuration files, SSL certificates
• Online help, Quick Help section at bottom of every web page
• Password protection for web log-on and ftp
• Field upgradeable firmware upload via ftp
• DHCP or static IP address, IPv4 and IPv6 support
• Hardened EIA-485 transceiver for Modbus RTU
• Powered by 10-30VDC or 12-24VAC 50/60 Hz
• Power Consumption: 0.1A @ 24VDC
• Panel mount, 70mm H x 131mm W x 38mm D
• Pluggable screw terminal block for power & RTU network
• Operating temperature -40°C to +85°C; Humidity 5% to 90%
• FCC Class A, CE Mark

MQ-61 Modbus to MQTT Gateway Video Library

Watch these videos for an introduction to configuring the gateway. It's easier than reading!

Introduction to the MQ-61 Modbus to MQTT Gateway

MQ-61 Modbus Overview

MQ-61 MQTT Publish to the Cloud

MQ-61 MQTT Subscribe to the Cloud

Generating Notifications with MQ-61

Getting Started with MQ-61 and IoT Analytics

Our most extensive technical support is provided by the same engineering staff that developed the products. Your personal attention from this staff is available via the support ticket system.

No user/password is required to open a new ticket. Once you open a ticket, you will immediately receive an email with your ticket number. Your ticket number becomes your login to review your ticket(s) later. Click the Support Ticket icon anywhere you see it. (If you do not get an email with your ticket number, within minutes, check your junk folder, spam settings, etc, and try again if necessary.)

 Open a Ticket