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
- General Issues, Building
- Timestamps - why offset to local time, and their general sematics
Timestamps - why offset to local time, and their general sematics
Is this with real ("device") tags on the KepServer, or with its simulated tags? Because, the simulated tags have some weird behaviors.
Regards
Please Log in or Create an account to join the conversation.
- LithalethuYotsi
- Offline
- Senior Member
- Posts: 6
- Thank you received: 0
Please Log in or Create an account to join the conversation.
You original problem that you had was that you *DID* get a new, but incorrect timestamp.
Now you are talking about *NOT* receiving some timestamp update.
Regards
Please Log in or Create an account to join the conversation.
- LithalethuYotsi
- Offline
- Senior Member
- Posts: 6
- Thank you received: 0
Please Log in or Create an account to join the conversation.
- LithalethuYotsi
- Offline
- Senior Member
- Posts: 6
- Thank you received: 0
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
- LithalethuYotsi
- Offline
- Senior Member
- Posts: 6
- Thank you received: 0
Regards
Please Log in or Create an account to join the conversation.
but what happens if, in this situation, you close the OPC Quick Client and then start it again? Will it keep the timestamp it has displayed before?
Regards
Please Log in or Create an account to join the conversation.
- LithalethuYotsi
- Offline
- Senior Member
- Posts: 6
- Thank you received: 0
Your response is much appreciated, the issue is not on the server. I've been on the line to simulate certain scenarios and the values change accordingly. I've attached two screen shots, first one is OPC Quick Client and second is a snippet of my application. The timestamp tag "RG06 Cabline.Node90.Machine_Status.CABLINE ALL PREOP" is bound to the label opposite Preoperation Enabled control on my application and the times don't match, I've tried both livebinding and low level code and the result is identical.
Attachments:
Please Log in or Create an account to join the conversation.
this is a valid concern and a good question.
However, QuickOPC only delivers to you the timestamps provided by the OPC server. It does not modify them. If the KepServerEX does not send the right timestamp, it is the server that needs to be fixed. Contact their support.
In OPC "Classic", there is just one timestamp. If you are using or can switch to OPC UA, you will find two timestamps there: SourceTimestamp and ServerTimestamp. There is a chance (but just a chance) that one (SourceTimestamp) will be the way you want it.
Best regards
Please Log in or Create an account to join the conversation.
- Forum
- Discussions
- QuickOPC-Classic in .NET
- General Issues, Building
- Timestamps - why offset to local time, and their general sematics