Do-More peer link to ThinkNdo WINPLC ?

[davidbgtx]

Can Do-More do peer link with  ThinkNdo on a WINPLC? Please say yes, can't replace all my WINPLC's at once that need to talk to each other.

[BobO]

Would love to say yes, but I would be lying.

Does T&D support Modbus/TCP?

[davidbgtx]

T&D documentation doesn't state that (that I can find), but I log data to a SQl database with KepServerEX from T&D WINPLC using converted T&D tags to modbus addressing. So I tried a MRX and "IT JUST WORKS" (don't even need KepServer as a "go between". Haven't tried MWX yet, but it should work as well. Need 1 Do-More to read/write a few tags (about once per second)to each of about 24 WINPLC's (to start, will gradually decrease as I replace WINPLC's with Do-Mores'), do you think it will "bog down" the Do-More?

[BobO]

Bog down at once per second? No. To be most efficient, create a Modbus/TCP Client for each target. If you use the same client for each connection, the controller has to connect and disconnect from each T&D device, which causes a bunch of unnecessary overhead.

[davidbgtx]

Bog down at once per second? No. To be most efficient, create a Modbus/TCP Client for each target. If you use the same client for each connection, the controller has to connect and disconnect from each T&D device, which causes a bunch of unnecessary overhead.

Thanks for advice, I would have thought just the opposite and only used 1 Modbus/TCP client. Seems this old dog, still has some new tricks to learn.

[BobO]

There is some additional overhead to servicing the Do-more client drivers, but it ends up being far less than establishing and terminating a TCP connection to each client each time you talk to it.