Integrate serial based process control systems with high capacity Ethernet networks.
Modbus to fixed Ethernet
Modbus to TCP gateways allow you to utilise existing Ethernet networks, reducing installation costs in industrial setups. They connect to Modbus RTU/ASCII devices via a serial port (e.g., RS-485) and then encapsulate the Modbus data into TCP/IP packets (Modbus TCP format) before sending it over the local or wide area IP network.
Modbus with WiFi
These converters encapsulate serial Modbus data into TCP/IP packets and transmit them over WiFi, to Modbus TCP compatible systems. They eliminate the need for long cable runs, making them ideal for large facilities or remote locations.
CANBus TO Modbus
These gateways facilitate the connection of newer CANbus based sensors and equipment to existing Modbus infrastructures without requiring a system overhaul.
They act as a translator between real time, high speed, and fault tolerant CANbus and Ethernet or serial based Modbus syatems. In mixed protocol environments, these gateways ensure that sensor readings, diagnostic codes, or control signals from a CANbus network can be accessed by a Modbus based SCADA system.
Modbus Notes
Modbus TCP / RTU integration
Since its inception in 1979 Modbus has become a widely used communication protocol in the field of industrial automation. Originally based on serial interfaces (RS232 and RS485) Modbus RTU enjoys widespread use throughout many different industries. Since then Ethernet has become the network of choice and many industrial devices now have native Ethernet interfaces. Modbus TCP is used over Ethernet and most SCADA networks have adopted this as their protocol of choice but there are challenges when it comes to connecting Modbus TCP and Modbus RTU networks together.
This document identifies common scenarios and looks at each can be overcome.
- Log in to post comments