Please attach the script code you are trying to use , we lack a point of reference. The CTT has no problems with UaDateTime as we use it.

It is not about an existing script. I want to create a custom script using custom types. One of these types consists of strings and dates. I can successfully encode/decode strings by a look into part 6 "Mappings". I would like to know how I can decode a date. From specification I know a date is encoded as Long, as number of 100 nanos since 1601-01-01. And I know how to convert the byte string into a Long. But then I want to create a DateTime from this number. But I miss such a method. I expect something like:

UaDateTime.fromLong(myLong)
or
UaDateTime.fromNanos(myLong)
or
var d = Constants.DateTime_Min();
d.addNanos(myLong);

Is there such a method which I haven't found? What I tried so far (see my first posting) doesn't work.

This is the definition of Part 6:
a) A date/time value is encoded as 0 if either
1) The value is equal to or earlier than 1601-01-01 12:00AM UTC.
2) The value is the earliest date that can be represented with the DevelopmentPlatform’s encoding.
b) A date/time is encoded as the maximum value for an Int64 if either
1) The value is equal to or greater than 9999-12-31 11:59:59PM UTC,
2) The value is the latest date that can be represented with the DevelopmentPlatform’s encoding.
c) A date/time is decoded as the earliest time that can be represented on the platform if either
1) The encoded value is 0,
2) The encoded value represents a time earlier than the earliest time that can be represented with the DevelopmentPlatform’s encoding.
d) A date/time is decoded as the latest time that can be represented on the platform if either
1) The encoded value is the maximum value for an Int64,
2) The encoded value represents a time later than the latest time that can be represented with the DevelopmentPlatform’s encoding.
These rules imply that the earliest and latest times that can be represented on a given platform are invalid date/time values and should be treated that way by applications.
A decoder shall truncate the value if a decoder encounters a DateTime value with a resolution that is greater than the resolution supported on the DevelopmentPlatform.

What you are missing is these exception (limits) - so again I ask if you could provide a more concrete example of the structure you are trying to test and the tests you are trying to run for it. To generate an encode number from anything by a string representation of the a date does not make sense since the base time can vary on development platforms (and there are rules on how to handle that). Again we do not have any test cases that would need the functionality you are describing or any structure that would need to be tested that have this type of data.

In a custom script I want to decode a custom data type, which is a structure of strings and a date. I successfully decoded the string part of it. The string can be decoded using UaByteSting.utf8ToString(). The length of a string can be decoded by UaByString.toUInt32().

But how to decode a date? For example I get "000006853A07AA01" (the date time fraction of the custom structure). I expect(ed) to find a helper function like UaByteString.toDateTime() which returns a UaDateTime object. But UaByteString only supports encoding/decoding of String and UInt32 by using get and set.

So I started with my own decoder. At first I convert that hex string into a Long. The Long representation of that byte string above is 119916288000000000. Now I expect a helper function to convert this Long value into a UaDateTime, for example UaDateTime.fromLong() or UaDateTime.fromNanos(). There are some addXxx() functions, but no addNanos(). Then I tried this:

var d = Constants.DateTime_Min();
d.addMillis(myLong / (10 1000 1000);

But it doesn't work. My question: Is there anything available that helps me converting a Long (=Int64) into a UaDateTime?

Our servers have a couple of custom structs which I want/need to use in custom scripts.

So after a discussion in the cmp group - we think this might be what you are having an issue with:
You have a custom structure
Mystruct{
[string] someString
[UaDateTime] myDateTime
[Float] myfloat
}
You would like to decode this structure in the CTT, and you are having a problem with the middle element in the structure, you have no problems with the string or Float. The write format for the UaDateTime is an Int64
What I tried to explain that looking at something other then current time can have issues, since the definition of UADateTime include variances for platforms - So looking at the resulting value (not as a datetime but as int64 is not correct. The stack on the platform on which the CTT is deployed, converts - based on platform - to a UaDateTime that is appropriate for the platform. Your structure is not being decoded by the stack, but passed to the application and thus are trying to decode it at the application level correct? I'm assumming the server contains the correct encoding information for the custom datatype? i.e. Can UAExpert or another standard client understand your DataType and expose it as a structure? If so I think the correct request is that the CTT should be enhance to allow automatic decoding of custom datatypes, since then the stack will handle the constraints a deployed platform might have.

Yes, I can decode the datetime part to Int64. And yes, UA Expert can display values of such variables. I wasn't aware of platform dependent issues. I use the Windows platform. I was also using Linux, but there is not update since CTT version 1.02.x. It would be great when CTT becomes able to decode custom structs. At first I would like to have a Calendar class to calculate dates:

'01.01.1601' + 119916288000000000 (nanos) = '01.01.1981'

and vice versa for encoding.

Updated the CTT to be able to decode custom structure in a future release (this will help with companion specification testing , not just vendor specific structures)