When testing with CTT, I have encountered a case were EURange.high is written with -56 and EURange.low with 0. Should this be allowed? If so, then the numeric absolute needs to be taken from the difference of the two, when configuring the percent deadbandValue e.g. :
Taken from page 28 of OPC UA Part 8 DataAccess Specification:
DataChange if (absolute value of (last cached value - current value) >
(deadbandValue/100.0) * (abs(high–low) of EURange)))
The CTT test many cases, including error cases. Which test case are you looking at? and in what version of the CTT?
A range is suppose to be between the lowest value and the highest value a number can vary between. Sometimes both numbers are negative (i.e. -100 and -50) but even in this case the range of 50 results.
Paul Hunkar - DSInteroperability
In this case the CTT merely showed the issue I was thinking of sometime before. I am referring to test script 006.js of the AnalogItemType CU. Here a write to the SByte datatype is issued (EURange.low = 0 and EURange.high = -56). My current implementation does not allow setting the low Attribute to a smaller numerical value than the high part. Therefore I was wondering wether the "logic of common sense" (EURange.high being always higher than EURange.low) can be inverted to "EURange.low can be numerically larger than EURange.high" concerning signed values as shown in the example above.
Thanks for your help,