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 Type Name seems to be not correct ?
The timestamps are incorrect (invalid) in the PubSub Wireshark trace too. It must be a problem in your mockup. Here is a message from your Wireshark capture:
It says "Timestamp: Not representable".
The bytes we are talking about are highlighted: 1F 99 68 38 5a D7 dd 64 . This means a number of 0x64ddd75a3868991F = 7,268,202,156,139,256,000, which represents cca 23047 years, which must be even added do the epoch (base date) of 1601, so the total is clearly way ahead in the far future.
From the OPC UA spec (reference.opcfoundation.org/Core/Part6/v104/docs/5.2.2.5 ):
A DateTime value shall be encoded as a 64-bit signed integer (see Clause 5.2.2.2) which represents the number of 100 nanosecond intervals since January 1, 1601 (UTC).
Our subscriber's behavior is then exactly in compliance with the spec, because this date is transformed to latest representable date upon decoding, as the spec says:
Best regardsA date/time is decoded as the latest time that can be represented on the platform if either
The encoded value is the maximum value for an Int64,
The encoded value represents a time later than the latest time that can be represented with the DevelopmentPlatform’s encoding.
Attachments:
Please Log in or Create an account to join the conversation.
It's an own written mockup and not finished.Regarding the timestamp: Which software is your OPC UA Publisher?
Do you think the wrong timestamps came from the mockup although i can see correct ones in the wireshark trace ??
So i tried again with your Demo Publisher, with UDP and ETH and both variants show correct timestamps in the OPC comandline Tool.
I think i should compare the different ws traces, there must be something different..
Thank you for your support. It helps me a lot.
Please Log in or Create an account to join the conversation.
if you need to determine data types of entities in OCP UA, there are other ways to do it,
What would your recommendation to check variables for correct type and format ?
And for the time display problem i did a wire-shark capture in the attachments.
This are the result from OPC command line tool:
I am also wondering about the 2 timeouts before messages are recived.
I already read: kb.opclabs.com/OPC_UA_PubSub_Common_Traps_And_Pitfalls
But as far as i understand we don't send Delta Frames. So could there be any other reason for this delay ?
Please Log in or Create an account to join the conversation.