**Optimizing Wonderware Intouch and Kepware: Addressing Timing Challenges with Simultaneous Tag Writing** I am currently facing a significant challenge within my Wonderware Intouch application, which integrates with Kepware to manage the transfer of approximately 2,200 tags to a CompactLogix processor over an Ethernet connection. The core issue lies in the timing for writing these tags "simultaneously." The duration for this process varies unpredictably, stretching anywhere from 5 to 25 seconds. This inconsistency creates potential complications in our operations, specifically if the production cycle begins before the recipe has been fully updated. To tackle these communication inefficiencies, I am actively working to enhance the data transfer protocols based on insights from Kepware. However, I remain concerned about the substantial delay and its unpredictable nature, which I suspect is largely influenced by the client's network environment—something outside of my control. I have reached out to both Wonderware and Kepware for assistance, but I have yet to find a viable solution. Ideally, the implementation of a handshaking mechanism or a monitoring system for the Kepware/Intouch status would be ideal. This could provide real-time feedback on whether all tags have been written and prevent the next cycle from starting until the update is complete. Without resorting to adding a blanket 30-second delay for each recipe transfer, I am exploring alternative options. One thought was to append an additional parameter to the end of the recipe that I could read back from the PLC to confirm transfer completion. However, I am uncertain whether recipe parameters are always transmitted sequentially. Does anyone have insights or recommendations that could help address this timing issue?
In the _Statistics folder, each channel features essential system tags that track pending read and write queue counts. To access this information, you must activate channel diagnostics. Once enabled, you can monitor the number of write operations in the write queue and the speed at which they are being processed. This insight is vital for optimizing your system's performance and understanding queue management effectively.
Thank you, Fred! I successfully located those tags and will conduct further testing tomorrow.
What are the advantages of choosing Kepware over Wonderware's DA Server?
We utilize Microsoft's Remote Desktop Services, allowing up to three users to simultaneously log in and operate InTouch software. According to our worldwide distributor, it is more cost-effective to purchase all InTouch licenses without I/O capabilities and then acquire a single Kepware license separately.
Fred_Loveless commented: There exist pending read and write queue count tags, classified as system tags, for each channel within the _Statistics folder. To access these tags, it's essential to enable channel diagnostics. Once activated, you will gain insight into the number of pending writes in the queue and the speed at which they are being processed. Fred, I can monitor the pending read and write counts using the OPC Quick Client, but I'm having trouble accessing them in my InTouch application. Interestingly, I can successfully retrieve details about failed reads and writes. Should I expect to also access the pending counts through the InTouch application?
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.