LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

U64 - Default Limits / Maximum / Coerce

Solved!
Go to solution

hello,

 

LabVIEW does not coerce with the maximum value 1E+19  (?)

 

Is this an expected behavior ? (or a bug ?)

 

 

yyyyyy.png

 

 

I previously asked this question on the french forum (french is my mother tongue) .. here .. but I didn't get any answers.

Message 1 of 18
(2,448 Views)

My eyes crossed counting zeros.

 

How many did you enter and is that number of zero legal for a U64?

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 2 of 18
(2,435 Views)

Hi ouadji,

 

I just tried this with LV2015 (no SP1) and have no problems with it.

 

I used these settings:

check.png

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…

Best regards,
GerdW

using LV2011SP1 + LV2017 (+LV2020 sometimes) on Win10+cRIO
0 Kudos
Message 3 of 18
(2,427 Views)

is that number of zero legal for a U64? ... yes, of course

 

the maximum for a U64 = 18446744073709551615

my value              = 10000000000000001024

0 Kudos
Message 4 of 18
(2,425 Views)
Solution
Accepted by topic author ouadji

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.  

Message 5 of 18
(2,424 Views)

Hi Darin,

 

then why does my U64 control coerce inputs nicely to 1e19 - even when I input 1e19+1 ("100…01")?

Best regards,
GerdW

using LV2011SP1 + LV2017 (+LV2020 sometimes) on Win10+cRIO
0 Kudos
Message 6 of 18
(2,419 Views)

@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.

0 Kudos
Message 7 of 18
(2,413 Views)

@ GerdW - Darin.K : 

 

try this (LV2015 sp1)

 

xxxxx.png

0 Kudos
Message 8 of 18
(2,412 Views)

@ Darin.K : " The coerce and limit logic uses DBL and 1E19 is not representable as a DBL ..... "

 

I suspected something like that  Smiley Frustrated

0 Kudos
Message 9 of 18
(2,403 Views)

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

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 10 of 18
(2,400 Views)