Whenever the Kepware services are re-started, the existing UDT instances show uncertain values and even I am not able to write to the tags even though the read write mode is on in the Ignition designer.
The tags are coming from a simulator channel from the Kepware server.
The issue gets resolved when we restart the Ignition gateway or delete and recreate the UDT instances. However, this is not a reliable solution in production.
I am using Ignition 8.3.1 version. Please suggest what is going wrong over here. Thanks.
I don't know what your issue is, but I would first upgrade Ignition as there have been numerous fixes since the version you have installed, then see if you still have the issue.
Hi Michael. I did some troubleshooting. It seems that the tag write is taking effect at the kepware side, but the Ignition tags are not updated. In short the Ignition tags are still showing the old values. If I restart the tags or disable & enable it again, then I can see the latest values. I even tried subscribing/writing the values from gateway, it succeeded. The Ignition version is 8.3.3 and the kepware version is 6.18.
I recall reports of many, many issues with old Kepware. You need to upgrade Kepware.
v6.18 should be fine though. I've got lots of plants with that version or older installed, although it's being used with Wonderware. Once they switched to Ignition they stopped using it.
This likely isn't related but thought I'd mention it. When using Autosol for a DNP3 connection it has different syntax for read vs writing of a AnalogOut tags so I have to use both and then a derived tag to combine them. When I initially create the tags the read tag populates but the write tags show uncertain value until there is a write for the first time.
You might want to use my Integration Toolkit's DivertWrite tag action on the read tag so you don't need a write tag at all.
The CM MES Automation Manager is also running on the same Ignition Server. I realised that when the Automation Manager is running the Memory Usage hits 96-97 percent. That is where I face many issues. However, if I turn off the Automation Manager, memory is at 50 percent then I dont face these issues. My dev server has 16GB RAM. When I check in the performance tab, 1.5 GB is used by Ignition whereas close to 6.5 GB is used by the Automation Manager. I suspect memory being the issue. Can it be so? Shall I give it a shot to increase the memory of the server and retest? How much memory will you suggest in this scenario & what should be the safe & ideal memory usage limit in the production environment?
Thank you for all the support and prompt response!