mrdegold
Lifetime Supporting Member
My problem of the moment (Well at least the one I’m hoping you can help with.) is.
I have Allen Bradley SLC 5/05 Processors on an ethernet network I am using some message (MSG) commands across the ethernet mostly for equipment status information. We have 5 or 6 so processors running this instruction. All were running fine I thought when I started to look into including the functionality from one machine to another I found that one of these message commands was in continuous error. I am getting mostly two types of errors
1st) D5 – Connection timed out by network
2nd) D8 - Connection was broken
As best as I can tell the Processor that is initiating a MSG read (SLC 1) is working fine I've traced the action of the MSG instruction using the status bits. It looks like everything from SLC 1 is working correctly. I am thinking that it is the Processor that is being read from (SLC 2) that is the problem. SLC 2 is on the network I know this because I can Ping the address and am currently running a trend using RS trend from SLC 2.
We are doing some maintenance work today that will require SLC 2 to be powered down. I am hoping that when SLC 2 is powered back up the Message instruction error will go away.
I think what I’m shooting for from this community is a plan B. In case the cycle power idea does not work.
As always thanks for the help
Michael
I have Allen Bradley SLC 5/05 Processors on an ethernet network I am using some message (MSG) commands across the ethernet mostly for equipment status information. We have 5 or 6 so processors running this instruction. All were running fine I thought when I started to look into including the functionality from one machine to another I found that one of these message commands was in continuous error. I am getting mostly two types of errors
1st) D5 – Connection timed out by network
2nd) D8 - Connection was broken
As best as I can tell the Processor that is initiating a MSG read (SLC 1) is working fine I've traced the action of the MSG instruction using the status bits. It looks like everything from SLC 1 is working correctly. I am thinking that it is the Processor that is being read from (SLC 2) that is the problem. SLC 2 is on the network I know this because I can Ping the address and am currently running a trend using RS trend from SLC 2.
We are doing some maintenance work today that will require SLC 2 to be powered down. I am hoping that when SLC 2 is powered back up the Message instruction error will go away.
I think what I’m shooting for from this community is a plan B. In case the cycle power idea does not work.
As always thanks for the help
Michael