rhymefactory
New Member
Hello everyone,
recently I started working with some PLCs who have Linux installed as an operating system. In general, I managed to solve the request from our customer, but I am looking for a way to improve things.
Our customer have a PC with an IP address of 192.168.100.9/16 - on that PC a SCADA system is running which acts as a Modbus/TCP Client. It has to connect IP address 192.168.101.100/16 on which a Modbus/TCP Server is running.
PLCs have IP addresses 192.168.101.81/16 and 192.168.101.82/16 and they act as a reduntant control solution (in case one of them stops or losses power or network connection, the other one takes over the process).
So, what I came up with is: when one of the PLCs is primary (controls the process), I add additional IP address (192.168.101.100/16) using ip addr command and activate Modbus/TCP Server on that PLC. After that, I send a ping from 192.168.101.100/16 to 192.168.100.9. If this is a first time SCADA is connecting, it usually takes up to 7 seconds.
If there is a switchover to the backup PLC, on the primary PLC I delete the 192.168.101.100/16 (to avoid having two same IP addresses on the network), I add this 192.168.101.100/16 to the backup PLC and send a ping from it to SCADA. In the case of switchover, it takes around 17 to 20 seconds for this to take effect and SCADA will again connect to the IP 192.168.101.100/16.
I would like to improve this switchover time to be as low ass possible.
Is there a way to add a routing option on both PLCs so that I don’t have to add and delete IP addresses, but to have PLCs listen to requests from 192.168.100.9/16 to 192.168.101.100/16, and then to route this traffic from 192.168.101.100/16 to both 192.168.101.81/16 and 192.168.101.82/16?
In that way, at a switchover I would just have to activate Modbus/TCP Server on the PLC which controls the process and that’s it.
Thank you for the support.
BR,
rhymefactory
recently I started working with some PLCs who have Linux installed as an operating system. In general, I managed to solve the request from our customer, but I am looking for a way to improve things.
Our customer have a PC with an IP address of 192.168.100.9/16 - on that PC a SCADA system is running which acts as a Modbus/TCP Client. It has to connect IP address 192.168.101.100/16 on which a Modbus/TCP Server is running.
PLCs have IP addresses 192.168.101.81/16 and 192.168.101.82/16 and they act as a reduntant control solution (in case one of them stops or losses power or network connection, the other one takes over the process).
So, what I came up with is: when one of the PLCs is primary (controls the process), I add additional IP address (192.168.101.100/16) using ip addr command and activate Modbus/TCP Server on that PLC. After that, I send a ping from 192.168.101.100/16 to 192.168.100.9. If this is a first time SCADA is connecting, it usually takes up to 7 seconds.
If there is a switchover to the backup PLC, on the primary PLC I delete the 192.168.101.100/16 (to avoid having two same IP addresses on the network), I add this 192.168.101.100/16 to the backup PLC and send a ping from it to SCADA. In the case of switchover, it takes around 17 to 20 seconds for this to take effect and SCADA will again connect to the IP 192.168.101.100/16.
I would like to improve this switchover time to be as low ass possible.
Is there a way to add a routing option on both PLCs so that I don’t have to add and delete IP addresses, but to have PLCs listen to requests from 192.168.100.9/16 to 192.168.101.100/16, and then to route this traffic from 192.168.101.100/16 to both 192.168.101.81/16 and 192.168.101.82/16?
In that way, at a switchover I would just have to activate Modbus/TCP Server on the PLC which controls the process and that’s it.
Thank you for the support.
BR,
rhymefactory
