Question, can an overload Allen Bradley driver cause gateway memory leak?
We been restarting the gateways once a week to deal with the side effect of memory leak. We believe the issues is coming from an overloaded allen bradley driver which is causing the PLC comms core to Max out.
With that said, I conducted the following test in a demo environment(Not in Production):
I am using Factory talk linx gateway OPC instead of the ignition OPC allen bradley driver.
When I simulate the max load on the ftlinx gateway i get the following results:
The comms core percetage is the orange spikes you see between the red and green.
I did the same test using the ignition opc server(allen bradley driver) and the data looks very different for the PLC comms core. The PLC comms core hits 100%
Well... I doubt it, since you'd be the first of many using the Logix driver to experience this.
Also - what memory leak? Work with support, they can help you with capturing and analyzing heap dumps to see if there's a leak and what might be leaking.
However, I have seen before how using the ftlinx gateway drops the comms core from an allen bradley PLC, specially when not following best practices on how to prepare your plc tags.
I have not tried his driver. Might be worth trying. Thanks.
If you want to get in tags all the data from your cpu, use this instruction fromt the plant PAX library L_CPU_5x80.
Doing it with the GSV is possible, but a bit painful. THis AOI has all you need and separates the usage per core type. Just import the rung file and it works like magic.
I might see if I can pull out the relevant code into my own AOI if it's overly bloated like the rest of the PlantPAx AOIs. I avoid PlantPAx like the plague if I can.
If you are using PlantPax 5, you are utterly screwed. If you are using earlier PlantPax, and have the source code, you can mitigate the problem if you are using my driver. PlantPax of any version utterly screws the IA native driver.
Just downloaded the PlantPAx v4.10.06 to try to pull out what code they're using in the L_CPU_5x80 AOI and it's source protected, so nothing can make it more efficient and can't even see how they're reading it.
I did find in the manual for the processors some diagnostic CIP messages I can use to pull a lot of information, so will parse through it to see what is handy and what's not.