ModBus with TRV00210

If I understand correct, you use the TRV00210 as a RS485 Modbus RTU interface for your circuit breakers and then convert the Modbus signal to Modbus over TCP/IP using the EDW-100.

Divide your problem in two steps:
1. Modbus RTU-communication
2. Conversion to TCP/IP

1. According to the documentation that I can find, the TRV00210 uses a RS485 interface, so try to communicate with the TRV00210 using another RS485 capable Modbus RTU device. Be aware of the following:
- The TRV00210 uses 8N2 serial protocol format out of the box, not 8N1
- Don't forget to use the Modbus station address you set with the rotary switches on the TRV00210

2. When the Modbus RTU communication is working OK, then consider 3 options for TCP/IP conversion using the EDW-100:
a. The EDW-100 acts as a TCP server
Setup the EDW-100 in "TCP Server" mode.
Citect uses the MODBUS driver and connects to the EDW-100 in TCP-mode (set -T option in Citect port special options). Please test if Citect can handle network interruptions longer than 30 seconds in TCP mode, because I had problems with that.

b. The EDW-100 acts as a UDP server
Citect uses the MODBUS driver and connects to the EDW-100 in UDP-mode (set -U option in Citect port special options). This is a reliable mode for the EDW-100 in combination with Citect using various serial protocols over TCP/IP. Citect recovers from network interruptions fine in UDP mode.

c. The EDW-100 acts as a protocol converter (Modbus RTU -> Modbus TCP gateway)
Set up the EDW-100 in "Gateway Server" mode and use Citect's MODNET driver or one of the variants.
I have not tested this mode yet, so please report back any findings you have when testing this.

In all cases the Citect drivers handle the TCP/IP packets themselves, so you don't have to install the virtual comm port software that comes with the EDW-100.
Do not forget to set the Modbus station address in Citect's I/O Device form. This is NOT documented in the driver's help! The help says that you should leave the address field empty, but this is incorrect!

Best regards,

Patrick van Dijk
CCSE v6.1 / v7

Im sorry to respond so late, but it has been on my todo list witch has been pretty full lately.

Thank you verry much for your fast response, it helped it was the hidden 2 stopp bits that was the problem.
Strange is that the support and the experts on those hardwares here in Sweden could not tell me this, and they just told me
what the documentation did aswell, that its supposed to be auto detecting the parameters for communications. Luckely for me it started working when i manually changed it to 2 stopbits in my EDW100.

When it came to all your options on how to redirect the communication thru the EDW100, i tryed them all out. I did only get one of them to work together with Citect. And that was with the TCP-Server mode, the one that ive always used when connectiong ModBUS interfaces thru EDW's to citect.

As said, i did try the others out with your instructions but with 0 results.
I didnt have the time at the point to go thru it more therow.

Thanks again for your fast response and your help.