6/8/2019 2:20 AM | |
Joined: 5/14/2013 Last visit: 2/11/2025 Posts: 13 Rating:
|
Hi, i'm having a very similar problem, i have a PLC S7-1200 as "master" in a Modbus TCP/IP Network, and i have another PLC s7-1200 as "slave", the first PLC is like 10 Km away from the second, i have antennas to build the network, so i can see the two PLC in a LAN network (i connect my PG in any switch of the network and i can see everything, and i can download the projects in all the plc with tia portal) i use MB_CLIENT and MB_SERVER Blocks, everything works fine, until we have a major problem of communication as 2 Hr with out energy in my antennas, the master PLC now is incompatible device (I cant see it with TIA portal 15 it says incompatible device, I cant see it with my WinCC runtime, I cant see it with web server, i cant see it with my other PLC) But it don't go to STOP state, is runing, only all the communications fail, the only way to reestablish all is turn off the power of the master PLC then turn ON, and everything solves, then i check the diagnostic buffer and only register the lack of energy, but no other event. I have other project but with 13 PLC as slave, and one central PLC and it happen the same thing. In the same project in the past, i done first the communication with Tsend, TRecive, Tcon instruction but it happend the same thing I'm thinking to do the hardware restart when i stop getting response from the other PLC in some time , but there is a way to solve this problem with out doing that?. Thanks. ------------------------------------------------------------------------------------------ |
Last edited by: MRCordova at: 06/08/2019 21:58:40Last edited by: The Helping Hand at: 06/11/2019 07:33:28New subject after splitting Last edited by: The Helping Hand at: 06/11/2019 07:39:35 |
|
6/11/2019 5:41 PM | |
Joined: 7/7/2010 Last visit: 3/20/2025 Posts: 15738 Rating:
|
To avoid these types of problems, I recommend changing to UDP with a watchdog and time-of-day added to the data being sent / received. In this way, both PLCs know when the last valid communication was from the other PLC and can act accordingly. UDP is blind and assumes the other device receives. In this way, it does not fault the connection (which you have to monitor and restart automatically upon failure for other protocols) if the remote device goes offline.
|
science guy |
|
This contribution was helpful to
1 thankful Users |
Follow us on