I was wondering if anyone has dealt with - Detecting PLC failures in Ignition?
We have Allen Bradley devices connected to Ignition and I am able to get their Conception status in Ignition via - Is Connected Tag Under Diagnostics.
Yeah, I see that. It would figure that Rockwell wouldn’t make it easy.
You would need to use a fault handling routine in the PLC. Shane Welcher has a video covering how to do this. He has a few stumbles as he goes through it, but in my opinion, it’s okay, because it shows some common issues that can happen while setting one up.
A fault routine won’t really help here. I suspect the issue is the reliance of the driver on the first-hop ethernet encapsulation connection to yield the “IsConnected” status, which will improperly remain true when the backplane connection from the EN?T to the processor breaks. The “Status” won’t update when the connection is down, which I would call a bug.
I understand that recent versions of the driver have enhanced the detection of connection problems, but I haven’t experimented with that or even noted what versions it applies to… @Kevin.Herron ?
The most reliable way to assess both processor and connection health is to subscribe to tags that are constantly changing due to ladder logic. If changes stop coming in, the connection is broken or the PLC isn’t in Run mode anymore. (I like reading an LINT containing the utc wallclock microsecond time obtained in ladder by a GSV.)