QA67230 : OPC UA in 5580 and 5380 Logix Controllers added with v36 firmware
Has anyone had a chance to play with this yet? I don't have access to any 5580/5380's at the moment.
The node counts are not very exciting for anything but the high-end controllers.
| Model |
Supported OPC UA Nodes |
| ControlLogix |
|
| 1756-L81E |
no support |
| 1756-L81EP |
no support |
| 1756-L81ES |
no support |
| 1756-L82E |
600 |
| 1756-L82ES |
900 |
| 1756-L83E |
1200 |
| 1756-L83P |
1200 |
| 1756-L83ES |
1500 |
| 1756-L84E |
10000 |
| 1756-L84ES |
15000 |
| 1756-L85E |
15000 |
| 1756-L85EP |
15000 |
| CompactLogix |
|
| 5069-L306ER* |
no support |
| 5069-L306ERS |
no support |
| 5069-L310ER* |
300 |
| 5069-L310ERS |
300 |
| 5069-L320ER* |
300 |
| 5069-L320ERS |
300 |
| 5069-L330ER* |
300 |
| 5069-L330ERS |
300 |
| 5069-L340ER* |
600 |
| 5069-L340ERS |
600 |
| 5069-L350ER* |
600 |
| 5069-L350ERS |
900 |
| 5069-L380ER* |
900 |
| 5069-L380ERS |
1200 |
| 5069-L3100ER* |
2000 |
| 5069-L3100ERS |
4000 |
1 Like
We have a 1756-L83E we've been meaning to upgrade and test with but I think it got lost to the holiday madness.
I think I tested against these at the OPC interop event in Germany this October and there were no (major?) issues?
1 Like
We typically don't need any processor larger than the L83E. The kicker in all of this is that each "node" is at least a tag, but if you use UDTs or even worse, nested UDTs, the base tag also counts as a node. In other words, if you have a UDT with 4 member tags inside of it, each tag you create with it counts as 5 nodes according to the documentation I read. So the larger your UDTs the lower your "overhead", but I like to structure my tags with sub-UDTs for status, config, metadata, alarms, etc so we'd chew through these nodes pretty fast. I don't even think an L85E would be capable enough to handle the number of tags we would need for our gas plant projects.
Perhaps, but if I'm remembering correctly they expose UDTs the same way Siemens and others are doing, where they make it available as both a single structured composite value as well as breaking it out into individual nodes with their own values. Subscribing to just the structured value should only count as 1.
I do wish Ignition had a better way to represent structured values than a Document tag with the optional accessory derived tags doing jsonGet/jsonSet 
2 Likes
I have an L320ERM in my lab. I'll play with this next week. I'm curious how the OPC UA support loads the comms processor.
I haven't played with it yet, but as per the KB article, that's not how they're doing it. (Screenshot of appropriate section attached as well)
That supports what I said, that they expose it both ways, except I was thinking the count was MonitoredItems, and apparently the count is just the total number of exposed Nodes.
So yeah, that will put a damper on how much you can do with it.
1 Like
Presumably CIP traffic will be prioritized? I wonder how that works in practice.
Another part of the KB pertaining to the communications priority:
3 Likes
Hi,
Has anyone successfully configured the Logix v36 as an OPC client.
Based on their knowledge based these are the values that are need to be set,
But if I'm going to use it as a client then should I put the ENABLE_SERVER = 0
Thanks.
