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.
- Forum
- Discussions
- QuickOPC-Classic in .NET
- Reading, Writing, Subscriptions, Property Access
- OPC XML-DA. Error: The item value does not specify a timestamp.
OPC XML-DA. Error: The item value does not specify a timestamp.
Please download and rebuild with the latest QuickOPC 2019.1, build 422.1 or later, as on our Web page and NuGet.
We have made the code more forgiving in this respect. Missing timestamp in the case you have described should no longer cause an exception.
Best regards
Please Log in or Create an account to join the conversation.
Attachments:
Please Log in or Create an account to join the conversation.
In the future, please put each issue into its separate forum thread. It is really important. We now have 3 issues here, under an incorrect title. It is a mess. . To sum it up, they are:
1. OPC XML-DA. Error: The item value does not specify a timestamp.
2. Number of open sockets.
3. commFault in getStatus call.
If they are related, links can be used to provide the relationship.
Regarding the number of sockets: Does it grow without a limit, or does it stabilize at or around certain number?
Best regards
Please Log in or Create an account to join the conversation.
Vendor info:
Arosii OPC XML-DA framework, Nordex RFC OPC XML-DA Gateway
I cant reproduce the issue "The item value from OPC NET API (Data Access) does not specify a timestamp." anymore.
It happened with All items but only once when "ItemChanged" notification was triggered first time.
Regarding the sockets. In my case this is a problem. It causes OPC server to stop working after a while
I have to use polling instead of subscription to workaround this problem.
But there is another problem.
My opc client is stuck in reconnecting to OPC server. I run Wireshark to trace communication and find that OPC server returns "commFault" state on GetStatus call.
Can I can disable "GetStatus" method call or inject my own handler of "GetStatus" response?
You informed me earlier that I couldn't disable "ServerStatusCheckPeriod" for OPC-XML protocol. Is it correct?
By the way, dOPC client just ignores opc server state. So, it does not have such problem and opens only 1 socket in subscription communication mode.
Regards
Please Log in or Create an account to join the conversation.
In question 2 , I wanted to know not just the technology (OPC XML-DA), but also the vendor/model of the server, if possible, please.
Additional question: Does this, in some scenario, happen with ALL items and consistently - that is, you cannot actually get any data from the server using subscriptions? Or only for some times? Or does it work for some time and then it starts issuing these errors? Or is it kind of random?
Regarding the sockets: The nature of OPC XML-DA subscription is in separate HTTP requests being issued over time, and each of them may have its own connection (= open socket). They should, however, be closing after some time. That is, if the number of open sockets does not grow "over all limits", I do not see it as a problem.
Regards
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
1. Is this an exception contained within the event argument of the DataChange notification:
2. Which target OPC server is this with?>
3. Is there a way for us to reproduce it?
4. Can you capture the network communication?
Best regards
Please Log in or Create an account to join the conversation.
I get an error from OPC XML-DA server after subscribing to opc items: "The item value from OPC NET API (Data Access) does not specify a timestamp."
Can you explain what is wrong?
Do you know to to fix it?
Regards
Please Log in or Create an account to join the conversation.
- Forum
- Discussions
- QuickOPC-Classic in .NET
- Reading, Writing, Subscriptions, Property Access
- OPC XML-DA. Error: The item value does not specify a timestamp.