devicenet inputs being maintained in program

merlin00724

Member
Join Date
Oct 2007
Location
cincy, OH
Posts
45
hey everyone, long time since my last post.

my issue is we have a bank of valves on devicenet with a controllogix controller. when we have a device failure like no comms, bus off, etc the inputs in the logic are maintained at their last state. for example, a valve is closed and making the closed prox and this prox input is true in the program. if you unhook the cable going to the valve, the input stays true in the program. the DV scanner of course displays node# and e78, but the input stays true in the logic therefor not faulting and alarming the valve on our scada.

I think this is a parameter on each device in the dnet program. maybe parameter 2 and/or 3?? I'm not sure though. can someone help me out?

thanks!!!
 
Welcome back to the Forum !

What you describe is normal operation for a DeviceNet system (and really, for most PLC I/O systems I'm familiar with).

Input data always stays at the last value before the connection was interrupted, so that the control system at least knows what the value *was* previous to the connection failure. If it set the value to zero on connection failure, you would lose that critical bit of data.

I've seen some programmers who make their networked I/O more DCS-like by changing every boolean value into an integer: "0" is BAD, "1" is FALSE", and "2" is TRUE.

I just use the connection failure diagnostic data when I need to take action based on a disconnected sensor. Most DeviceNet scanners have a 64-bit connection status table, and the modern ControlLogix/CompactLogix ones have a table of integer values that give the connection status or status code (like the 72/78 you see when a device gets disconnected).

Most DeviceNet output devices can be configured for how you want them to take action when the network connection is interrupted (or when the PLC goes to PROG mode), but the state of the input data in the controller's Input data table is the DeviceNet Scanner module's decision, and it always holds the last state.
 

Similar Topics

Hi, I am looking to migrate some of our Electronic Overloads off of a Troublesome Devicenet Segment. Is there any documentation confirming the...
Replies
5
Views
99
We've run into an old system that we are upgrading which is still running Steeplechase with Citect using Devicenet to Wago. I had some experience...
Replies
4
Views
146
Sigh, DeviceNet noob... I have a 1756-L55, with a DeviceNet module, and 10 PF700 all commanded with DeviceNet. One of the PF700's blew up...
Replies
3
Views
133
Good day Forum Members I got a older Lincoln welder and hoping to make it work at our shop. Welder in question is the Lincoln Power Wave 455M...
Replies
4
Views
207
Hello Friends We have 10 Powerfocus 4000 with DeviceNet, We need to backup the configuration, the Powerfocus is detected but as unrecognized...
Replies
0
Views
106
Back
Top Bottom