LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

using units with quotient & remainder

Hello everybody (and especially LabView developers),

I got a problem regarding physical units:
When I divide two numbers with unit "s" (time, seconds), then a normal divide gives me a number without unit (which is correct). When I use "quotient & remainder" instead then I get a number with unit "s" as remainder (which is correct) and a number with unit "s" as quotient which is NOT correct!

I really like to use units, but from time to time a find such (silly) calculation problems... That's annoying!

Best regards,
GerdW
Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Message 1 of 6
(3,672 Views)
Hello GerdW,

For some reason I'm not getting that... mine looks ok.
But you're right, sometimes it's a little bit annoying to work with units...
0 Kudos
Message 2 of 6
(3,652 Views)
Hello PauloM,

I took your example and just inserted a new "quotient and remainder" and now look what happens...

Best regards,
GerdW
Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 3 of 6
(3,642 Views)
Hi Guys,

could it be that the first terminal to be wired is calculated with units, and the second one isn't? Have you tried wiring both outputs on a single function, but the other way round than before?

Curious....

Shane.
Using LV 6.1 and 8.2.1 on W2k (SP4) and WXP (SP2)
0 Kudos
Message 4 of 6
(3,635 Views)
Hi,

Those are the reasons why I think it's annoying to work with units... I tryied once and after some time I gave up and took care of it myself.
0 Kudos
Message 5 of 6
(3,632 Views)

I realize I revive and old thread but the issue is still present in LabVIEW 8.6.

 

17241i0B2F7C4A5BFB7EB8

 

The workaround is to always wire the Remainder output for the function to work as expected.

Unless it is already resolved in 2009, it should be reported as a bug.



LabVIEW, C'est LabVIEW

0 Kudos
Message 6 of 6
(3,273 Views)