Waveshare 24962 Dual-Channel RS485 to Ethernet Serial Server

Connect the server to your network and access its web configuration interface via its default IP address. Navigate to the 'Protocol Conversion' settings and select 'Modbus TCP Gateway' mode. Map the local RS485 port parameters (baud rate, parity) to match your Modbus RTU slave devices. Define the TCP port for Modbus TCP masters to connect to. Save and reboot the device; it will now translate Modbus TCP requests from the network into Modbus RTU frames on the serial bus, and vice-versa, enabling seamless integration with SCADA software like Ignition or WinCC.

For transparent transmission, log into the device's web UI and set the operating mode to either 'TCP Server' or 'TCP Client'. In Server mode, define a listening port; any TCP client can connect to this port to send/receive raw serial data. In Client mode, configure the remote server's IP and port to which the serial server will connect. Match the serial port baud rate and data format to your connected device. This creates a virtual serial tunnel over IP, useful for legacy software using Virtual COM Port (VCOM) drivers or custom socket-based applications without protocol conversion overhead.

Yes, the module includes a built-in MQTT client. In the configuration interface, enable MQTT Gateway mode and enter your broker's address, port, and credentials. Define data parsing rules, such as extracting values from specific serial data frames or Modbus registers. You can configure the topic structure and payload format (e.g., JSON). The server will then establish a connection to the broker and periodically publish sensor data, allowing easy integration with platforms like Node-RED, Home Assistant, or AWS IoT Core for real-time monitoring and dashboarding.

Each of the two RS485 channels operates on a completely separate hardware interface with its own isolation and transceiver chip. They are configured independently via the web interface, allowing different baud rates, parity settings, and operating modes per channel. For example, Channel A can be a Modbus TCP gateway for a sensor network, while Channel B operates in transparent TCP Client mode for a separate PLC. This dual independence prevents data collision and timing issues, making the device suitable for consolidating two distinct serial networks onto one Ethernet infrastructure.