Network connection

[JeffKiper]

OK I'm geeking out a little to far and I know it. 

Do you know how AB determines I:ConnectionFaulted ?  I mean under the hood not just that they set a bit that says I:ConnectionFaulted. 

Example the 525 drive don't have that tag. So I run a small AOI every 5 seconds to do a GSV that returns the MODULE EntryStatus.  The Status is Standby, .Faulted, .Validating, .Connecting, .Running, .Shutting down, .Inhibited, .Waiting, .Firmware Upgrade, .Configuring.

 

I use a XIO .INHIBITED and XIO .RUNNING to determine if the connection is good.

 

If the Connection is not Inhibited and is Running then we are OK.

If the Connection is Inhibited then don't I don't care.

Several 3rd party devices have the ConnectionFaulted tag.

[TimWilborne]

I'd be curious what if it would follow the GSV EntryStatus not equaling 16384.  Especially on a 3rd party device.  I have to go down to the PLC Lab tomorrow and might run some test.

[JeffKiper]

I was using the GSV and looking at the connection the doing an NEQ of 16384. Then I looked at the EntryStatus help file. Bits 12-15 in HEX give you those bits status values. Instead of just looking at the decimal value I broke it down. Does it matter? Probably not. I'm just geeking out and looking a making some fault logic that is quick to add to a controller.