MGate MB3180/MGate MB3280/MGate MB3480

Features and Benefits 

• Supports Auto-Device Routing for easy configuration
• Supports route by TCP port or IP address for flexible deployment
• Convert between Modbus TCP and Modbus RTU/ASCII
• 1 Ethernet port and 1, 2, or 4 RS-232/422/485 ports
• 16 simultaneous TCP masters with up to 32 simultaneous requests per master
• Easy hardware setup and configuration 

Overview

The MB3180, MB3280, and MB3480 are standard Modbus gateways that convert between Modbus TCP and Modbus RTU/ASCII protocols. Up to 16 simultaneous Modbus TCP masters are supported, with up to 31 RTU/ASCII slaves per serial port. For RTU/ASCII masters, up to 32 TCP slaves are supported.

Standard Modbus network integration

The three standard MGate™ models (MB3180, MB3280, and MB3480) are designed for easy integration of Modbus TCP and RTU/ASCII networks. With these models, Modbus serial slave devices can be seamlessly incorporated into an existing Modbus TCP network, and Modbus TCP slaves can be made accessible to serial masters. The MB3180, MB3280, and MB3480 offer features that make network integration easy, customizable, and compatible with almost any Modbus network.

High density, cost effective gateway

The MGate™ MB3000 gateways can effectively connect a high density of Modbus nodes to the same network. The MB3280 can manage up to 62 serial slave nodes, and the MB3480 can manage up to 124  serial slave nodes. Each RS-232/422/485 serial port can be configured individually for Modbus RTU or Modbus ASCII operation and for different baudrates, allowing both types of networks to be integrated with Modbus TCP through one Modbus gateway.

Auto-Device Routing for Easy Configuration (Patent Pending)

Moxa’s Auto-Device Routing function helps eliminate many of the problems and inconveniences encountered by engineers who need to configure large numbers of Modbus devices. A single mouse click is all that’s required to set up a slave ID routing table and configure Modbus gateways to automatically detect Modbus requests from a supervisory control and data acquisition (SCADA) system. By removing the need to manually create the slave ID routing table, the Auto-Device Routing function saves engineers significant time and cost.

New Technology Automates Arduous Routing Setup in Modbus Gateways

When a lot Modbus devices need to be monitored and controlled, engineers usually have to spend a lot of time planning the topology of these devices and segmenting them into different subgroups. Moreover, they are also weighed down by the mundane task of keying in hundreds of Modbus slave IDs to set up each Modbus gateway’s Modbus slave ID routing table. Thus, engineers are constantly on the lookout for solutions that address this pain point when setting up multiple Modbus devices. This white paper takes a closer look at different routing technologies and their pros and cons, as well as a new technology that helps save time and costs when configuring and managing a large number of Modbus devices.

How to Architect Your Systems to Get the Most Out of Your Modbus Devices

The migration of all industrial applications to Ethernet is unquestioned. But, before network engineers can inch closer toward all-systems-go, they need to overcome several challenges. The most pressing one is to ensure that there is no breakdown in communication between serial devices and SCADA hosts. It is no secret that plenty of solutions are available on the market. The immediate question is which solution fits your network’s requirements the best.

In this white paper, we will look at four challenges that arise when linking up Modbus-supported devices to SCADA systems. We will also provide solutions for different scenarios to address your concerns.