# LabVIEW

cancel
Showing results for
Did you mean:

Solved!
Go to solution

## U64 - Default Limits / Maximum / Coerce

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.

Message 1 of 18
(2,437 Views)

## Re: U64 - Default Limits / Maximum / Coerce

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
Message 2 of 18
(2,424 Views)

## Re: U64 - Default Limits / Maximum / Coerce

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…

Best regards,
GerdW

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

## Re: U64 - Default Limits / Maximum / Coerce

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

the maximum for a U64 = 18446744073709551615

my value              = 10000000000000001024

Message 4 of 18
(2,414 Views)
Solution

## Re: U64 - Default Limits / Maximum / Coerce

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,413 Views)

## Re: U64 - Default Limits / Maximum / Coerce

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
Message 6 of 18
(2,408 Views)

## Re: U64 - Default Limits / Maximum / Coerce

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

Message 7 of 18
(2,402 Views)

## Re: U64 - Default Limits / Maximum / Coerce

@ GerdW - Darin.K :

try this (LV2015 sp1)

Message 8 of 18
(2,401 Views)

## Re: U64 - Default Limits / Maximum / Coerce

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

I suspected something like that

Message 9 of 18
(2,392 Views)

## Re: U64 - Default Limits / Maximum / Coerce

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
Message 10 of 18
(2,389 Views)