LabVIEW
Why it can't work?
Don't know. It should work, when you see the run array unbroken.
Btw. you should not use "run continuously" with a VI. It's only intended for debugging purposes!
And you should search the term "coercion dot" in the LabVIEW help…
What does "work" mean to you? Because the code will operate but maybe not like you expect. In addition to using run continuous (which you should never do) you also have multiple controls with the same label. This makes explaining the issue difficult but I'll do my best.
You have the a-b control as a double, and the a-b control as a U8. The U8 only has values from 0-255 so if your subtraction has a result other then these 256 values you will not get what you expect. It also has no fractional component and any subtraction that has a fractional component won't give you the value you expect either.
Well, this looks like a first LabVIEW exercise.
Note that if you place a slide indicator, you can show the digital display (right-click...) and now don't need a second indicator. Make sure the datatypes match, you want DBL here (right-click the blue terminal...representation...). You placed a progress bar, which is U8 by default, simply change it.
@Viper wrote:
Progress bar? Hmm sounds like the thread to thread isolation is breaking down.
The what? In your first image you showed a progressbar. In your VI that you just posted you did not have a progress bar. altenbach was trying to say that the progressbar by default is a U8 and in your code it looks like you want a double.
@Hooovahh wrote:
The what? In your first image you showed a progressbar. In your VI that you just posted you did not have a progress bar. altenbach was trying to say that the progressbar by default is a U8 and in your code it looks like you want a double.
The first image and the VI were posted by different users. My comment was specific for the original question, which showed a progress bar, as can be seen from the terminal icon.
@Viper wrote:
Ahh guess I never realized that the icons actually contain useful information. I turn them off to save real estate.
Thanks
A very large majority of developers do the same. So much so that it was requested to make it non icon view by default. It was shot down by NI. If the poster had posted a VI (like everyone looking for help here should) then the icon view would also simply be wasting real estate.
