Category Archives: Modbus RTU

Serial communication protocol. This is usually RS232 or RS485.

ACC Automation 2020 Yearly Review


Accelerate Learning …
Accelerate Machines…
Accelerate Knowledge…
ACC Automation
ACC Automation 2020 Yearly Review
What a difference a year makes! Social distancing, mask-wearing, hygiene, social circles, etc are just a few of the terms we hear every day in this Covid-19 world. Video conferencing with Zoom, Teams, and Google Meet are the norm in business today. Information is knowledge, and everyone wants to be able to see, control, and summarize production data on a regular basis. Technologies are merging and communicating like never before. What was impossible is now possible for the industrial plant floor. We are looking forward to the New Year and new possibilities for implementing your control solution.

Each year we like to take a few minutes and reflect on the past, current, and future of ACC Automation. You have helped us to build the site that you see today through questions, comments, and suggestions. Thank you. Keep on Reading!

Productivity 1000 PLC to Modbus TCP RTU BX-MBIO


We will now look at the productivity 1000 plc modbus tcp rtu communication to the BX-MBIO controller.
The Productivity 1000 PLC can communicate to a remote I/O (input and output) controller modules using the Modbus protocol for communications. The BX-MBIO provides both Modbus RTU and Modbus TCP interfaces. Modbus RTU is a serial communication and Modbus TCP is an Ethernet communication. Modbus RTU is supported over an RS-485 serial connection. Modbus TCP is supported over an Ethernet connection. They function as listening/replying devices (slave, server) and can connect with any mastering (master, client) device that communicates using the Modbus protocol.
Previously we looked at the BX-MBIO Modbus RTU TCP Remote IO Controller wiring and configuration.
Modbus RTU TCP Remote IO Controller BX-MBIO
BX-MBIO Hardware Video
BX-MBIO Powering and Configuring Video

productivity 1000 plc modbus tcp rtu
We will connect the Productivity 1000 PLC to the Modbus remote IO. This will be done using the Modbus TCP and Modbus RTU protocol. Ethernet and serial RS485 communication to the BX-MBIO unit will be the media.
The BX-MBIO remote I/O expansion units feature the following:
• RJ45 Ethernet port for communications via Modbus TCP
• RS485 serial port for communications via Modbus RTU
• Supports up to 8 additional Expansion Modules (Add the discrete or analog I/O you require)
• AC and DC powered units available
• AC powered units include an integral 24VDC auxiliary output power supply
• Power connector and serial port connector included
Let’s get started. Keep on Reading!

Click PLC to Modbus TCP RTU Remote IO BX-MBIO


The Click PLC can communicate to a remote I/O (input and output) controller modules using the Modbus protocol for communications. The BX-MBIO provides both Modbus RTU and Modbus TCP interfaces for remote IO. Modbus RTU is a serial communication and Modbus TCP is an Ethernet communication. Modbus RTU is supported over an RS-485 serial connection. Modbus TCP is supported over an Ethernet connection. They function as listening/replying devices (slave, server) and can connect with any mastering (master, client) device that communicates using the Modbus protocol.
Previously we looked at the BX-MBIO Modbus RTU TCP Remote IO Controller wiring and configuration.
Modbus RTU TCP Remote IO Controller BX-MBIO
BX-MBIO Hardware Video
BX-MBIO Powering and Configuring Video

We will connect the Click Ethernet PLC to the Modbus remote IO. This will be done using the Modbus TCP and Modbus RTU protocol. Ethernet and serial RS485 communication to the BX-MBIO unit will be the media.
The BX-MBIO remote I/O expansion units feature the following:
• RJ45 Ethernet port for communications via Modbus TCP
• RS485 serial port for communications via Modbus RTU
• Supports up to 8 additional Expansion Modules (Add the discrete or analog I/O you require)
• AC and DC powered units available
• AC powered units include an integral 24VDC auxiliary output power supply
• Power connector and serial port connector included
Let’s get started. Keep on Reading!

BRX Do-More PLC to Modbus TCP RTU Remote IO BX-MBIO

The BRX Do-More PLC can communicate to a remote I/O (input and output) controller modules using the Modbus protocol for communications. The BX-MBIO provides both Modbus RTU and Modbus TCP interfaces. Modbus RTU is a serial communication and Modbus TCP is an Ethernet communication. Modbus RTU is supported over an RS-485 serial connection. Modbus TCP is supported over an Ethernet connection. They function as listening/replying devices (slave, server) and can connect with any mastering (master, client) device that communicates using the Modbus protocol.
Previously we looked at the BX-MBIO Modbus RTU TCP Remote IO Controller wiring and configuration.
Modbus RTU TCP Remote IO Controller BX-MBIO
BX-MBIO Hardware Video
BX-MBIO Powering and Configuring Video
brx do-more plc modbus remote io
We will connect the BRX Do-More PLC to the Modbus remote IO. This will be done using the Modbus TCP and Modbus RTU protocol. Ethernet and serial RS485 communication to the BX-MBIO unit will be the media.
The BX-MBIO remote I/O expansion units feature the following:
• RJ45 Ethernet port for communications via Modbus TCP
• RS485 serial port for communications via Modbus RTU
• Supports up to 8 additional Expansion Modules (Add the discrete or analog I/O you require)
• AC and DC powered units available
• AC powered units include an integral 24VDC auxiliary output power supply
• Power connector and serial port connector included
Let’s get started. Continue Reading!

Modbus RTU TCP Remote IO Controller BX-MBIO

We will be looking at the Modbus remote IO BX-MBIO-M controller. This is the Do-More Modbus Remote I/O supported protocol unit. We will discuss the hardware and then connect and configure the unit to work with our existing BRX Do-more PLC. Let’s get started.

The BX-MBIO Modules are remote I/O controller modules that provide a remote input and output (I/O) using the Modbus protocol for communications. They provide both Modbus RTU and Modbus TCP interface. Modbus RTU is a serial communication and Modbus TCP is an Ethernet communication. They function as listening/replying devices (slave, server) and can connect with any mastering (master, client) device that communicates using the Modbus protocol.
Modbus RTU is supported over an RS-485 serial connection. Modbus TCP is supported over an Ethernet connection. Any Modbus RTU master and Modbus TCP client that adheres to the Modbus.Org standards, and support the function codes listed can communicate with the BX-MBIO.
The remote I/O expansion units feature the following:
• RJ45 Ethernet port for communications via Modbus TCP
• RS485 serial port for communications via Modbus RTU
• Supports up to 8 additional Expansion Modules (Add the discrete or analog I/O you require)
• AC and DC powered units available
• AC powered units include an integral 24VDC auxiliary output power supply
• Power connector and serial port connector included
Modbus RTU TCP Remote IO Controller BX-MBIO

Continue Reading!

C-More EA9 HMI to Solo and Click PLC Controllers




The cmore EA9 HMI has an event manager that can be used to trigger actions based on various events.
C-More EA9 HMI Solo and Click PLC controllers
We will be adding a Click PLC to our headless RHMI cmore EA9 program that we created last time to communicate to the solo process temperature controller. The Solo will be connected via RS485 using the Modbus RTU protocol. Using the Modbus TCP protocol we will connect the Click PLC to the Ethernet port. Using the event manager we will be writing the set value (SV) and present value (PV) of the solo process temperature controller to the Click PLC. We will also allow the Click PLC to write the SV into the solo. This is in addition to the writing of the set value via remote apps and the solo itself. Let’s get started. Continue Reading!

C-More to Solo Process Temperature Controller




The cmore EA9 HMI can connect to the Solo process temperature controller using the built-in RS485 serial communication port. This will connect up to 32 solo units back to the HMI for display and control.
C-More EA9 HMI Series Headless RHMI to Solo Process Temperature Controller
We will be setting up our headless RHMI c-more EA9 to communicate to the Solo process temperature controller. Using the information that we have discussed previously, we will set up data logging, file transfer protocol (FTP), bitmaps, etc.
C-More EA9 HMI Series Headless RHMI to Solo Process Temperature Controller
We will also set up an object library of the Solo 4896 process temperature controller. This will consist of a bitmap, numeric display, numeric edit, indication lights, and up and down increment. The system will then be controlled using the remote applications discussed last time. Let’s get started. Continue Reading!

Stride MQTT Gateway to Adafruit IO

MQTT protocol is used for machine to machine (M2M), internet of things (IoT) communication. This publish/subscribe messaging is used where limited device resources are available or network bandwidth is low. The MQTT protocol provides small size, low power usage, minimized data packets, and efficient distribution of information to one or many receivers.
MQTT Communications - Overview
The Stride MQTT Gateway is an industrial 4.0 hardware component (IIoT – Industrial Internet of Things) that provides isolation and can easily interface with existing Modbus RTU and Modbus TCP communication protocols.
Stride MQTT Gateway to Adafruit IO
We will again be connecting a Stride MQTT Gateway to a Solo process temperature controller with Modbus RTU(RS485). The MQTT Gateway will communicate to the Adafruit IO Broker. The broker can display, log, and allow us to control the data. This is done in an easily configured interface. Let’s get started. Continue Reading!

Stride MQTT Gateway Click PLC Modbus RTU TCP

MQTT protocol is used for machine to machine (M2M), internet of things (IoT) communication. This publish/subscribe messaging is used where limited device resources are available or network bandwidth is low. The MQTT protocol provides small size, low power usage, minimized data packets, and efficient distribution of information to one or many receivers.
Stride MQTT Gateway Click PLC Modbus RTU TCP
The Stride MQTT Gateway is an industrial 4.0 hardware component (IIoT – Industrial Internet of Things) that provides isolation and can easily interface with existing Modbus RTU and Modbus TCP communication protocols.
Stride MQTT Gateway Click PLC Modbus RTU TCP
We will be connecting a Stride MQTT Gateway to a Click PLC (Ethernet) via Modbus TCP. Previously we connected the Solo process temperature controller with Modbus RTU(RS485). We will leave this connection in place and add the Click PLC. The MQTT Gateway will communicate with HiveMQ Broker. MQTTBox Client will then read and write to the Click PLC and Solo process temperature controller. Let’s get started. Continue Reading!

Stride MQTT Gateway to Modbus RTU TCP

MQTT protocol is used for machine to machine (M2M), internet of things (IoT) communication. This publish/subscribe messaging is used where limited device resources are available or network bandwidth is low. The MQTT protocol provides small size, low power usage, minimized data packets, and efficient distribution of information to one or many receivers.
Stride MQTT Gateway to Modbus RTU TCP
The Stride MQTT Gateway is an industrial 4.0 hardware component (IIoT – Industrial Internet of Things) that provides isolation and can easily interface with existing Modbus RTU and Modbus TCP communication protocols.
Stride MQTT Gateway to Modbus RTU TCP
We will be connecting a Stride MQTT Gateway to a Solo process temperature controller via Modbus RTU. (RS485) The MQTT Gateway will communicate to a Mosquitto Broker. Google MQTTLens (MQTT Client) will then read and write to the Solo process temperature controller. Let’s get started. Continue Reading!