The MGate 5134 is an industrial Ethernet gateway for converting Modbus RTU/ASCII/TCP to PROFINET network communications. To integrate existing Modbus devices onto a PROFINET network, use the MGate 5134 as a Modbus client to collect data and exchange data with the PROFINET host. All models are protected by a rugged and compact metal housing, are DIN-rail mountable, and offer built-in serial isolation. The rugged design is suitable for industrial applications such as factory automation, power, oil and gas, water and wastewater, and other process automation industries.
The MGate 5134 gateways are provided with a web console to make configuration easy without having to install an extra utility. In addition, HTTPS encryption of communication ensures higher network security. In most data-acquisition applications, configuration of devices with Modbus commands can be time-consuming and increase costs. The MGate 5134 gateways provide offline configuration via a CSV file to help complete the Modbus settings quickly. The gateways also come with a GSDML export function to enable export of these files so that they can be imported to PROFINET PLCs. The MGate gateways provide software-configurable pull high/low and termination resistor settings for RS-485 2-wire to reduce efforts by eliminating the need to open the chassis.
The MGate 5134 gateways provide a variety of maintenance functions to reduce troubleshooting time and cost, including LED indicators, protocol diagnostics, traffic monitor, and tag view. These tools help you capture and check data to easily identify the root cause of issues, especially during the installation stage. The MGate gateways also come with status monitoring and fault protection functions. The status monitoring function notifies a PLC/DCS/SCADA system when a Modbus device gets disconnected or does not respond, in which case the process PLC/DCS gets the status of each end device and then issues alarms to notify operators. The fault protection function executes actions pre-defined by the user when a host gets disconnected to prevent the end devices from going offline for long periods of time..