Professional OPC
Development Tools

logos

Online Forums

Technical support is provided through Support Forums below. Anybody can view them; you need to Register/Login to our site (see links in upper right corner) in order to Post questions. You do not have to be a licensed user of our product.

Please read Rules for forum posts before reporting your issue or asking a question. OPC Labs team is actively monitoring the forums, and replies as soon as possible. Various technical information can also be found in our Knowledge Base. For your convenience, we have also assembled a Frequently Asked Questions page.

Do not use the Contact page for technical issues.

Value updates comes out of order in MonitoredItemChanged

More
21 Jan 2016 12:32 #3803 by Hustveit
Hi,

I will create a ticket with Kepware and see what they say.
Thank you for your help.

Regards
Bard Hustveit

Please Log in or Create an account to join the conversation.

More
21 Jan 2016 12:29 #3802 by support
I am convinced that our component delivers the values to you in the order the server has provided them, and with the timestamps as sent by the server. Therefore I suggest that you ask Kepware whether they acknowledge or admit the server behavior you described.

If they don't, we would have to analyze the communication between the client and the server (using some tool, e.g. Wireshark), and then conclude which side is at fault.

Best regards

Please Log in or Create an account to join the conversation.

More
21 Jan 2016 11:43 #3800 by Hustveit
Hi,

I'm using EasyUAClient version 5.34. Running against a KepwareEX OPC server.

I have one installation where I'm getting values out of order in the MonitoredItemChanged event.
I log every value changed I get from the OPC server, and I noticed that the the last value I had on the client did not match what was the current value on the OPC server. When I started looking at the ServerTimestamp values they where not in the correct order either.

Below is log from where this happens. RT = is when i recive the MonitoredItemChanged event. ST = ServerTimestamp. The problem is with the two Weight values where the last one have a ServerTimestamp that is earlier than the first one.

2016-01-20 14:33:43 467 DEBUG Bhs f6acc74a-cfde-46ad-a05e-cf4f70b28496 [Weight] Value=0, RT=14:33:43.4585, ST=14:33:42.8237
2016-01-20 14:33:43 477 DEBUG Bhs f6acc74a-cfde-46ad-a05e-cf4f70b28496 [E2_ActiveMove] Value=False, RT=14:33:43.4675, ST=14:33:42.1674
2016-01-20 14:33:43 483 DEBUG Bhs f6acc74a-cfde-46ad-a05e-cf4f70b28496 [Weight] Value=31, RT=14:33:43.4838, ST=14:33:42.1674
2016-01-20 14:33:43 62 DEBUG Bhs f6acc74a-cfde-46ad-a05e-cf4f70b28496 [E2_ActiveMove] Value=True, RT=14:33:43.6217, ST=14:33:43.4799
2016-01-20 14:33:43 63 DEBUG Bhs f6acc74a-cfde-46ad-a05e-cf4f70b28496 [E3_ActiveMove] Value=True, RT=14:33:43.6314, ST=14:33:43.4799

Should this be possible? Could this have anything to do with the OPC server?

Regards
Bard Hustveit

Please Log in or Create an account to join the conversation.

Moderators: support
Time to create page: 0.055 seconds