ControlLogix Devicenet Missing Node Identification

lostcontrol

Lifetime Supporting Member
Join Date
May 2009
Location
NeverSayNever
Posts
1,069
We have a 1756-L55 system, with 2x Devicenet scanners, 1 with 50+ nodes, the other with < 10 nodes.

90% of the time, this system functions ok, but on the reasonably regular occassion some of the nodes drop off the network, either by power failures or other issues.
To assist in debugging this issue in the future, we have thought about adding 'node status' indication to the HMI. What I am not sure of is how to retrieve this information from the scanner.

The scanner itself as a 124 element DINT array configured for Input/Output status monitoring/control.
There is a combination of node types, predominatly being 1791D-16BO modules, with some valve banks as well.

What is the best way to get the status of each node on the network, so that it can be displayed?
It looks like each module has 2x elements allocated, but I am not sure if any bits of the elements provide any status information or not?

Easy option would be to add in an 'always on' input to each node, but I am not sure what is available on each node. Reading the status seems like the better optoin.
 
Actually it's a lot easier than that.

In addition to the Input and Output Connections, the 1756-DNB has a Status connection of 32 double-words.

It includes a handful of useful status information such as the DeviceFailureRegister, which is a SINT[8] array where each bit represents a node address on DeviceNet. When there's a connection failure, the corresponding bit goes true.

Even more helpful is the DeviceStatus array, which is a SINT[64] array that contains an error code for any broken connection. You'll typically see a fault code 72 here for a powered-down device, or a 77 for a size mismatch.

There's even a 4-byte StatusDisplay array where each byte is the ASCII equivalent to what's on the dot matrix display on the front of the 1756-DNB. If you wanted to echo what's in on the DNB display in an HMI, that would make it easy.

There's also a Diagnostic Faceplate for FactoryTalk View SE/ME in the Samplecode website, that plugs right into the Status connection for the 1756-DNB.
 
Ken,

That is all excellent information. I overlooked the S register, if I had of looked a bit more I would of found it!

Even more helpful is the DeviceStatus array, which is a SINT[64] array that contains an error code for any broken connection. You'll typically see a fault code 72 here for a powered-down device, or a 77 for a size mismatch.
In which document would I find the error code explanations? I think I am going to add a table to the SCADA with the status indications, and maybe even the fault codes, so that it will assist the maintenance guys even more!
 

Similar Topics

Something i ran into that has me stumped, hopefully someone can explain. I have powerflex 70's connected to a L7 cpu using a 1788-en2dn. The...
Replies
5
Views
1,341
I am migrating an Allen-Bradley SLC based system to ControlLogix and need some help with DeviceNet addressing. The SLC system has a 1747-SDN and I...
Replies
3
Views
1,442
Devices had lost communication, upon checking PLC cabinet Device net was flashing E#78 n#1 thru 16 / 1756-en2t showed "cycle power to unit: assert...
Replies
21
Views
8,084
Hey folks What is the best online training to purchase for Control Logix and DeviceNet? I am not as proficient in those as I am RS 5 and RS 500...
Replies
2
Views
2,161
I am preping for an upgrade of our IFM ASi bus gatways that sit on a Devicenet string. I have 1 set up on a test rig in my office. Everything is...
Replies
16
Views
15,679
Back
Top Bottom