06-20-2016 01:08 PM
hello,
LabVIEW does not coerce with the maximum value 1E+19 (?)
Is this an expected behavior ? (or a bug ?)
I previously asked this question on the french forum (french is my mother tongue) .. here .. but I didn't get any answers.
Solved! Go to Solution.
06-20-2016 01:16 PM
My eyes crossed counting zeros.
How many did you enter and is that number of zero legal for a U64?
Ben
06-20-2016 01:22 PM - edited 06-20-2016 01:23 PM
Hi ouadji,
I just tried this with LV2015 (no SP1) and have no problems with it.
I used these settings:
I set "coerce" for minimum and increment = 1, as these are completely making sense for an U64 value. (But also "ignore" for minimum and increment does work fine.)
When I input a value bigger than 1E19 the U64 coerces (as expected) to 1E19…
@Ben
You can always input "1e19" instead of a 1 followed by 19 zeros. No need to count zeros or keystrokes…
06-20-2016 01:22 PM
is that number of zero legal for a U64? ... yes, of course
the maximum for a U64 = 18446744073709551615
my value = 10000000000000001024
06-20-2016 01:23 PM
The most recent datatypes (EXT and 64-bit integers) suffer from these types of issues. The coerce and limit logic uses DBL and 1E19 is not representable as a DBL, so the value 10....01024 is not distinguishable from 10....00000.
06-20-2016 01:25 PM
06-20-2016 01:30 PM
@GerdW wrote:Hi Darin,
then why does my U64 control coerce inputs nicely to 1e19 - even when I input 1e19+1 ("100…01")?
I'd guess and hope that something got fixed in LV15 or LV15 SP1.
06-20-2016 01:31 PM - edited 06-20-2016 01:32 PM
06-20-2016 01:35 PM
@ Darin.K : " The coerce and limit logic uses DBL and 1E19 is not representable as a DBL ..... "
I suspected something like that
06-20-2016 01:38 PM
Just thinking along with the rest...
A property node allows etting the limit and it is a DBL.
Could this be a mantissa issue for doubles?
Ben