adccommunitymod (AutomationDirect) asked a question.
CLICK Communications error.
Created Date: August 12,2016
Created By: Tom@Pton
**** This post has been imported from our legacy forum. Information in this post may be outdated and links contained in the post may no longer work.****
I have a couple CLICKs set up on a LAN and would like to stop the program sequence if the communications is lost or one of them goes offline for whatever reason. Pulling the Ethernet cable produces no errors that I have found. Nor does using the Success flag. Suggestions?
Created Date: August 12,2016
Created by: Tom@Pton
I have a couple CLICKs set up on a LAN and would like to stop the program sequence if the communications is lost or one of them goes offline for whatever reason. Pulling the Ethernet cable produces no errors that I have found. Nor does using the Success flag. Suggestions?
Created Date: August 12,2016
Created by: kewakl
Can one Click (master?) generate a heartbeat for the other and the other clear the bit. Master would see the heartbeat cleared and set the bit again.
If either Click notices the signal ON or OFF for longer than TimeOut, HALT!
Created Date: August 12,2016
Created by: Tom@Pton
Can one Click (master?) generate a heartbeat for the other and the other clear the bit. Master would see the heartbeat cleared and set the bit again.
If either Click notices the signal ON or OFF for longer than TimeOut, HALT!
?That is close to what I have. Right now the N Click needs to know what the status of the S Click is and if communications are lost, the N must stop. If the North stops, we don't care, well, very much anyway. I thought there might be something simpler I was missing.
Created Date: August 12,2016
Created by: kewakl
I 've heard people talk of using an incremental numeric, transmitting this (new) value, if the value stay the same too long, stop your actions.
Basically the same thing, but an incremented value can provide a bit of a timestamp.
Created Date: August 12,2016
Created by: OpZed
Look at the system bits SC90 to SC95 for information about the local Ethernet port. SD41 might be also be useful.
Created Date: August 12,2016
Created by: Mike Nash
If you need to know the other PLC is still executing the logic (Run mode) the heartbeat/watchdog might be better than some status bit regarding communications.
Created Date: August 13,2016
Created by: Tom@Pton
If you need to know the other PLC is still executing the logic (Run mode) the heartbeat/watchdog might be better than some status bit regarding communications.
The heartbeat/watchdog works well. Removing either network cable or power flags an alarm on the other, as does switching either to OFF. Loss of power to the router flags alarms on both.
Now to incorporate it.
Thanks to all.