Hi, I am having some significant problems with ignition.
I have made a number of other posts regarding database issues etc, none of which have yet been resolved. My latest issue is that I am getting random changes in data in the PLC, which I know are caused by ignition, but are not appearing in the audit trail. In addition to this, I am getting random firing of events, events that change setpoints. This all seems to happen when restarting the primary gateway of the redundant configuration, or sometimes during communications loss.
While nothing is happening ignition-wise, no changes happen in the PLC. However, when a reboot of ignition happens or any sort of comms loss happens, data randomly and throughout the entire PLC memory becomes corrupted.
I have also seen some other events trigger from another client (i am running multiple clients) that I wasn’t even working on get fired during these times also, although this is relatively rare. But definately happening, as I am looking at such an event right now (I have custom events logging).
This is very worrisome, as it is changing setpoints for alarms all over the place, and it seems ignition is not even aware it is happening. I am using the Modbus/TCP driver with 17 connections to the PLC as recommended by inductive support to get the throughput required from an M580.
Any ideas would be much appreciated.