Hi, folks,
Running into a small problem here.
I currently have two two redundant AB CLX processors talking to the SLC 5/05 via a built-in SLC Ethernet port (connected by copper to a switch and then via fiber to another switch, and then copper to the AB 1756-ENBT cards of the CLX processors). SLC is the master and reads/writes to the CLX via MSG instructions (16 total, with a maximum of 8 running at any given time).
The system is working OK, however, I get random (not periodic!) Ethernet hardware faults on the SLC (fault code A2h). AB manual states that this fault is unique to the SLC 5/04 - 5/05, and that this fault can be cleared by writing to the status file, but the communications would only restore once the power of the SLC is cycled.
Just curious, if anyone has ever had similar problem before and how it was corrected (if it was). I'm just not sure whether simple replacement of the SLC processor (as recommended by AB TechSupport) would help....
Any help is very much appreciated.
Thanks,
Alexei
Running into a small problem here.
I currently have two two redundant AB CLX processors talking to the SLC 5/05 via a built-in SLC Ethernet port (connected by copper to a switch and then via fiber to another switch, and then copper to the AB 1756-ENBT cards of the CLX processors). SLC is the master and reads/writes to the CLX via MSG instructions (16 total, with a maximum of 8 running at any given time).
The system is working OK, however, I get random (not periodic!) Ethernet hardware faults on the SLC (fault code A2h). AB manual states that this fault is unique to the SLC 5/04 - 5/05, and that this fault can be cleared by writing to the status file, but the communications would only restore once the power of the SLC is cycled.
Just curious, if anyone has ever had similar problem before and how it was corrected (if it was). I'm just not sure whether simple replacement of the SLC processor (as recommended by AB TechSupport) would help....
Any help is very much appreciated.
Thanks,
Alexei