- #KEPWARE SLOW CLIENT POLLING HOW TO#
- #KEPWARE SLOW CLIENT POLLING UPDATE#
- #KEPWARE SLOW CLIENT POLLING SOFTWARE#
I would appreciate any comments or education from people here who are experienced with UA.
#KEPWARE SLOW CLIENT POLLING UPDATE#
This seems to suggest a disconnect between the UA server and the HMI client in terms of coordinating compatible update rates.
#KEPWARE SLOW CLIENT POLLING SOFTWARE#
I have further found that if I eliminate from the UA server configuration every available update time larger than 100 ms (which I believe is the minimum that the WinCC Advanced RT can handle), I can then set whatever update rates that the HMI engineering software permits and it will update at the acquisition cycle rate. Apparently since my server made several update rates available, the highest of which was 10 seconds,I was seeing update rates of 10 seconds instead of what I configured the acquisition cycle to be in the HMI. With a bit of experimentation, I have discovered that my HMI application updates no faster that the slowest available update rate configured in the OPC UA server.
#KEPWARE SLOW CLIENT POLLING HOW TO#
I would appreciate any suggestions as to how to resolve this problem. This client seems to have no problem seeing the tags update at the actual rate the changes occur in the controller, so I guess the problem is in the WinCC Advanced application. Let me poke around a bit and see if I can get a better result. To test whether this is a server or a client problem, I ran on my programming PC the OPC UA sample client provided by OPC Foundation. You can’t really expect to see every change because you’re dealing with so many overlapping polling cycles here (kepware polling PLC, OPC subscription evaluation, ignition client/designer polling gateway), but that’s looking a little slower than I’d expect. The other two number tags remain unchanged (since they are not programmed to)but are configured to refresh every 2 seconds in the HMI client. The polling will only be done in response to a client request, so if none of a relays children are asking for a site, it wont go upstream to check for the site, even if its polling period has expired.
In the HMI application, I have the boolean tag and the string configured to update every 500 ms, but this is not occurring. The downside to polling too frequently is that it can drive unnecessary load into the parent. However, the tags only update every 9 or 10 seconds. This makes it easier to see on each update than a toggling bit would be by itself.Īll 4 tags are visible to the client. At the same interval, the string text "rotates" in the following manner: In the controller program, the boolean value cycleson and off every 200 ms. The client is communicating via OPC UA with a server on a 3rd party controller, a Schneider LMC600 motion controller, in case anyone is interested.įour (4) tags are communicated over OPC UA, a boolean, an integer (16-bit), a string value (7 characters), and a floating point value. Although my engineering software is V13, I am compiling for V12 which is the runtime version on the device. Today I set up a simple HMI client using WinCC Advanced (TIA Portal) for a runtime client on an IPC277D.
0 kommentar(er)
