Babel Buster BB3-6101-MQ Modbus to MQTT IoT Gateway

        Babel Buster BB3-6101-MQ Modbus to MQTT IoT Gateway

        Control Solutions’ Babel Buster BB3-6101-MQ Modbus to MQTT Gateway turns any Modbus device into a Thing on the Internet of Things using the MQTT protocol. 

        • $739.00

        Control Solutions’ Babel Buster® BB3-6101-MQ 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 BB3-6101-MQ 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 BB3-6101-MQ 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 BB3-6101-MQ will decide if and when to publish that data to the MQTT broker (server). You can also configure the BB3-6101-MQ 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.

        Cloud Not Required!

        The BB3-6101-MQ is also suitable for stand-alone remote monitoring use. The BB3-6101-MQ includes alarm monitoring with email notifications using its internal secure email client, local data logging with CSV files emailed to you instead of sending data to the cloud, and a real time scheduler for date and time scheduling.

        Feature Highlights
        • MQTT Client supporting AWS IoT Core
        • Simple template based setup of MQTT Publish and Subscribe
        • Modbus RTU Master or Slave
        • Modbus TCP Client and Server
        • Secure local email client
        • Local data logging
        • Real time scheduler
        • Local user programming with Script Basic
        • User HTML support for adding custom web pages
        • Configure via secure web pages
        • IPv4 and IPv6 support
        • FCC, CE Mark, UL 916 Listed

        Full product information, data sheet, online user guide, tutorial videos, and more available by clicking here.

        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 BB3-6101-MQ, 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 BB3-6101-MQ 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 BB3-6101-MQ is analyze and visualize the data. The graph illustrated above represents data published by an BB3-6101-MQ, and the steps taken to get this graph – without writing any program code – are outlined in the user guide.

        The data flow in the BB3-6101-MQ 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.

        The BB3-6101-MQ can be Modbus RTU master or slave (user selectable), and Modbus TCP client and server (concurrently). Maps created via templates in the BB3-6101-MQ’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 BB3-6101-MQ also supports character strings as a series of registers having two ASCII characters per register.

        BB3-6101-MQ Works Equally Well as Stand-Alone Remote Monitoring Device

        The BB3-6101-MQ includes a secure local email client that will directly email you notifications of alarm events. The event rule template has all of the same power and flexibility as the MQTT publish template. You can implement stand-alone remote alarm monitoring on multiple data points, and send different notifications to different people.

        The email message template lets you fully customize the message that is sent. You can use any email account including Gmail to send emails from the BB3-6101-MQ. The template includes variables which insert real time data from the BB3-6101-MQ as the email is sent.

        The BB3-6101-MQ includes local data logging capability that can be used instead of sending data to the cloud. You select which data points are logged to a local CSV file. This file is then emailed to you periodically. You select logging rate and when files should be sent. You also have the option of logging at a slower rate most of the time, but then log faster when an event of interest is in progress.

        The Babel Buster IoT Gateway becomes more useful when control functions can be combined with monitoring. One element of control that is often useful is the ability to schedule things to happen at certain times on certain days. The scheduler makes that possible.

        Scheduling is done in a very generic and simple way. A register you select will change value according to a schedule you provide. From there, you can use the client to write that register to some external Modbus device to cause action according to your schedule.

        • MQTT Client supporting AWS IoT Core
        • Simple template based setup of MQTT Publish and Subscribe
        • Secure local email client for stand-alone notifications
        • Local data logging for stand-alone remote monitoring
        • Real time scheduler
        • 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
        • Optional RS-232 transceiver for Modbus RTU
        • Powered by 10-30VDC or 24VAC 50/60 Hz
        • Power Consumption: 0.1A @ 24VDC
        • DIN rail mounting, 100mm H x 70mm W x 60mm 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
        • Listed to UL 916 and (Canadian) C22.2 No. 205-M1983

        Maximum Object Counts and System Capacities for BB3-6101-MQ

        BB3-6101-MQ allows user allocation of memory resources. Memory capacity will not support maximum counts of everything possible, but maximum count limits are set high so that you can allocate resources where you need them.

        • Maximum Modbus registers 2000
        • Maximum IoT Thing Attributes 100

        • Maximum Modbus RTU device count 240
        • Modbus RTU read map count 1000
        • Modbus RTU write map count 1000

        • Maximum Modbus TCP device count 200
        • Modbus TCP Client read mapcount 1000
        • Modbus TCP Client write map count 1000

        • Maximum event rules 1000
        • Maximum weekly scheduler events 1000
        • Maximum on-demand scheduler events 1000

        Footer navigation