Virtual Ports Modbus TCP Communication Issues

Hello folks, Im here because I’m being out smarted by a Waveshare RS 485 to Eth (B). I am successfuly getting data directly from an energy metering by plugging an RS 485 to USB adapter into my laptop. However, I need the data to get across the building so I am forced to use ethernet. I’ve got it set up so that the waveshare device (WS) is connecting to a ubiquiti cloud gateway to get an IP address, and the laptop accesses the internet through the same gateway.

I have two sscom windows open, one on COM4, the port connected to the usb hub, and as a TCP client. I should note that at this point the link light is blue, which in the WS wiki means “When the serial port sends data to the network port, the indicator light is blue and green at the same time. due to blue It is brighter, so if you see blue, it means that there is a serial port returning data to the network port. This can judge whether the device has a response to the command of the host computer, if there is no response, it indicates that the string The port baud rate is incorrect or the serial port is not connected properly“. When I send out messages in the USB sscom window, the active light flashes green, but not when I send messages in the TCP client window. The main issue is that they should be sending messages to each other, but the only IN message that occurs is when the TCP client window connects to the remote IP address.

I’m hoping someone here might be able to decipher what these mixed messages mean, and how I can make this thing work. I’ve tried following the guide on the wiki, but I hit errors left and right, and am in communication with the WS support team to figure them out.

1 Like

Im not sure if this is how the forum works, but I saw this post about a similar device, so if @Michael99645 or @Dan see this, I’d appreciate any ideas that might save this

1 Like

Hey @PineOwple,

Welcome to the forum!

You’re absolutely in the right place, and it looks like you’ve already made a great start with your troubleshooting.

I’m not super familiar with this product, so I could be wrong, but one of the first things to check is that the serial port settings match on both ends. From your screenshot, it looks like the COM2 device is set to 9600, 7E1, while the COM4 is using 9600, 8N1, that mismatch would definitely cause communication issues.