Hi, I’m still trying to improve performance between my Omron NJ PLC and Ignition. The current procedure for populating the Omron NJ Driver tag table is outlined here: https://docs.inductiveautomation.com/display/DOC/Omron Currently if i do an export from the PLC, I end up with ~18000 tags in the…

I have noticed considerable improvement in performance by adding another Omron NJ Driver device, and pointing it to the same PLC. Also, the PLC’s Ethernet Card that is used to communicate with Ignition was under a 4ms task. Moving this to a 100ms task also helped improve comms considerably. I imagi…

Ignition only polls tags that are subscribed to. There's no negative impact (other than some small amount of memory) when you import all the tags. It just makes them available for browsing. The NJ doesn't implement the necessary services for us to browse tags or learn about the UDTs so the driver…

[image] Kevin.Herron: The reality is that the NJ's EtherNet/IP implementation is not very good in the case where you need to subscribe to a lot of tags. Kevin, is there any roadmap ahead involving doing any improvements to the NJ driver? It's at the point now in the project where plant is goi…

Sometimes there’s not a good answer within a traditional query/response driver. Before you panic, though, try creating multiple driver instances pointing at the same PLC. Spread your subscribed tags amongst those drivers. If performance doesn’t improve, you’ve hit the PLC’s query/response communi…

Thanks for the response Phil. I’ve increased the concurrency in the device settings to start with. I think there has been some improvement but only time will tell. Is there any way to determine the max value i can bump this up to? (currently at 8) I intend to test multiple devices too, if i can’t …

If your UDTs are under 496 bytes each, or can conveniently be broken into chunks that fit, you can fairly quickly add buffer copies to send the data to the output buffer of virtual I/O modules. When the packet arrives in my module, the assembly can be configured to place the data in the right place…

Can you tell me where you adjusted these settings. We are experiencing equivalent delays in communication between Ignition and an Omron controller. This device is an NX102-9000 Omron controller.

Hi there, Settings are under the Device Connections under the OPC UA configuration page in the Ignition Gateway. If you edit your device connection, there is a “concurrency” setting that you can try increase to get more performance gains. [image]

Inductive Automation Forum

Omron NJ Driver performance optimization

Ignition

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled