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.

Data Quality Issues - OPCLabs client and Softing's OPC server

More
06 Jul 2016 14:15 - 06 Jul 2016 14:17 #4201 by bojan
Hi OPCLabs,
After the help you provided and analysis with OPC server vendor some improvements to the server and its settings have been made.

We await for updated server version.

Thank you for your support!
Last edit: 06 Jul 2016 14:17 by bojan. Reason: clarification

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

More
27 Jun 2016 17:50 #4176 by support
No, there definitely isn't any difference between what the demo client does, and WriteMultipleItemValues.

Look for misconfigurations in your app or in the analyzer.

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

More
27 Jun 2016 17:16 #4174 by bojan
Hi OPCLabs,
We run OPC Analyzer, and configured it to connect to the OPC server as shown in attached image.
We modified our app to point to OPC Analyzer:
OPC ServerDescriptor created using: MachineName: localhost, ProgrId: OpcTestLab.OpcAnalyzer.1
opcda://localhost/OpcTestLab.OpcAnalyzer.1, {ItemId=SamleID}, 230
However no traffic is traced on our writes, and data is there. Maybe because of WriteMultipleItemValues?

We see it catches single writes and reads from Demo Client.
Attachments:

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

More
27 Jun 2016 14:56 #4172 by support
Memo from the phone discussion: Happens relatively frequently. It appears that the old value is retained (no value written). Connect to Softing INat... OPC server. Suggested that attempting to write a Quality etc. should not be done - not related to the issue. Sending OPC Analyzer instructions and link over email.

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

More
27 Jun 2016 14:13 - 27 Jun 2016 14:55 #4171 by support
Can you verify the written value directly on the server (or the equipment), or using some other OPC client connected to the same server?

What I am trying to establish is whether 1) the problem was already with the write, or 2) the value was written correctly, but was not reported back as it should.

And: Please clarify what you precisely mean by " some of the item has the different value ". Can you tell whether this means that A) the value has not been written at all, i.e. the item has retained its original value, or B ) at the moment of the Write, SOMETHING was written - but it appear to be something different from what you have sent.

Thank you
Last edit: 27 Jun 2016 14:55 by support.

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

More
27 Jun 2016 14:00 #4170 by bojan
Hi OpcLabs,
We have an issue with data quality. It appears that the data sent from OPCLabs client to Softing’s I-Nat server isn’t recorded in the server.
  • We send the data using DA: client.WriteMultipleItemValues(IList<DAItemValueArguments> writeArgs.ToArray())
  • We check the results of sending using: operationResult.Succeeded of every result item
  • All elements in result set have this flag as true.
  • In rare occasions (e.g. 1 out of 700 items) some of the item has the different value in OPC server from what we sent.

How can we address this issue?
We created an app using OPCLabs component, so we can verify where the discrepancy is and are also monitoring the changes. The discrepancy is there already after the initial push.

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

Moderators: support
Time to create page: 0.060 seconds