LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Why do very few programmers use LabVIEW unit labels

Highlighted
The coincidence with the Nugget is simply that, a coincidence.  It is interesting that one comment was that someone took beginner, intermediate and advanced courses and units were not taught.  Perhaps this goes some way to explain why they do not appear to be used often, especially be instrument driver suppliers.
0 Kudos
Message 11 of 21
(1,803 Views)
Highlighted
I use units quite often. Very handy when working with systems that utilize both imperial and metric units of measure.
PaulG.

LabVIEW versions 5.0 - 2020

“All programmers are optimists”
― Frederick P. Brooks Jr.
0 Kudos
Message 12 of 21
(1,775 Views)
Highlighted

I was in heaven when I first discovered units. Halleluja! I often want to change displays from minutes to seconds, and this makes it super-easy. But now I'm being crippled by bugs when I write subVIs that use generic units.

0 Kudos
Message 13 of 21
(1,603 Views)
Highlighted

Like all functions in software.. If it is not complete (having too many bugs) It is better not to use it.

So NI, please flag all bugs with units and either solve them, or at least forbid units to be used with buggy functions.

greetings from the Netherlands
Message 14 of 21
(1,592 Views)
Highlighted

I've not experienced a bug wrt units.  I've never used the square function though, but this would be easy to recognise as the use of this data would not have the expected units.  What other bugs are there?  Are they fixed in versions after 7.1.  

 

I find myself writing code for others in my company now (and here no one else uses units), and I constantly have to ask about what units their data is in!  Units everyone!

0 Kudos
Message 15 of 21
(1,561 Views)
Highlighted

An other approach is to use in your software only base units, so all data are in Amps or Volt, or degrees Kelvin

And only on the user interface translate to the units people want to see.

greetings from the Netherlands
Message 16 of 21
(1,549 Views)
Highlighted

My main problem with units come when I write subVIs with polymorphic units. Then I get errors like "The source is degC but the sink is $11", when my polymorphic unit is $1. The final straw was "polymorphic unit too complex" or something similar, a phrase that didn't even turn up in Google.

 

Formula nodes can't take inputs with units.

 

Maybe these things have been updated since LabVIEW 7.1, but that's what I have to use.

0 Kudos
Message 17 of 21
(1,547 Views)
Highlighted

I would strongly suggest that Albert ask for working units in the LabVIEW Idea Exchange, and the rest of you kudo it.  This is a tough problem to do correctly, but it is more likely to get done if there is a demonstrable demand.

This account is no longer active. Contact ShadesOfGray for current posts and information.
Message 18 of 21
(1,529 Views)
Highlighted

I'm not sure what you suggesting.  Please clarify, as I feel that this is an important topic.  

 

Related, I recently created a company wide database and dictated that all data would be stored in SI units.  I consider this problem solved, but then I am able to tightly control the inputs and outputs: something I don't have for LabVIEW code.

0 Kudos
Message 19 of 21
(1,511 Views)
Highlighted

Thanks DFGray

 

http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Make-units-work-all-the-way-or-skip-them/idi-p/1803510

 

I understood and filed a very simple Idea although it is in fact a bug report.

greetings from the Netherlands
Message 20 of 21
(1,497 Views)