Electrical Engineering Stack Exchange is a question and answer site for electronics and electrical engineering professionals, students, and enthusiasts. It only takes a minute to sign up.
Sign up to join this community
The requirement is to read many different Modbus devices by different masters.
Since this can't be done through RS485, so the following image is the solution coming to me.
My questions are:
1.Is it possible to use a normal switch (like 20$) to support those devices which use Modbus-TCP?
2.Is there any possible risk of this solution?
Modbus/TCP can be handled by a simple unmanaged Ethernet switch. I have used this numerous times, although I reserve the "cheap" switch for bench testing and use an industrial quality switch (temperature rating, redundant power, status output) in the final product.
It's difficult to quantify risk as you have asked, since I have no knowledge of your application. If it's for lab use, then I see no risk.
Note that Modbus/TCP is not deterministic. If timing (or guaranteed "on time") is important, Modbus/TCP might not be appropriate. This comes into play when you are doing something like feedback control, where the Modbus/TCP is in the feedback and final control paths. Again, not knowing your application I won't chase this thought further.
I have used gateways before and they work, although can be pricey. Anybus X is one I've used but I'm not necessarily recommending it.
A good alternative to a dedicated gateway is to use the same type CPU as in the PLCs and write a small program to handle this function. It gives you more flexibility and the hardware probably costs less than the gateway. I've done this on several projects and now will only use a dedicated gateway if my PLC doesn't support the other protocol.
