Precision property node in numerical value

I found there had a problem in the "precision" property of numercial value.
FREQUENTLY, my simple code showed an error message (attachment).
Sometimes, the code was Okay randomly.
Is it bug or any other solution?
메시지가 08-07-2007 11:49 PM에 labmaster에 의해 편집되었음
메시지가 08-07-2007 11:50 PM에 labmaster에 의해 편집되었음
Attachments:
yahoo.png ‏17 KB

Set the format of your indicator to floating point (right-click...format&precision). You had it on automatic formatting.
LabVIEW Champion . Do more with less code and in less time .
Attachments:
Untitled_2MOD.vi ‏9 KB

Similar Messages

Setting DAQ channel by property node does not display the value

I am writing a configuration VI to set channel selection and calibration parameters for an SCXI chassis. I store a default setup in a configuration (ini) file and read that file automatically when the VI is called. The value from the file are set by property nodes using the "Value" property. The values from the file do not display in the DAQ channel selection rings, but the numerical calibration values do display correctly. When I click the down arrow in the channel rings, the correct value displays.
This behavior exists both in LabView and app-builder EXEs. Also, if I change the property nodes for the DAQ channels to local variables, it works. The Value (signaling) property doesn't cause them to display
properly either. Why can't I use the property node?

I don't understand exactly what you are trying to do.
Please upload a simple VI to demonstrate the behavior you are describing. Remember also to attach the .ini file.
Best regards,
Philip C.
Applications Engineer
National Instruments
www.ni.com/ask
- Philip Courtois, Thinkbot Solutions

How can I change the precision of a numeric array indicator using property nodes ?

I want to change the precision of a numeric array indicator programatically using property nodes. I tried to see all the array properties but I couldn't find it. URGENT !!!

If you want to change the precision of an element in an array you must first get the reference to the array element. Then raise the reference to the more specific class of a digital numeric. Use a property node connected to that reference to set the precision. See the attached vi for an example.
Brian
Attachments:
ArrayElementPrec.vi ‏27 KB

Test limits in numeric field in case value is written by property node

Hello,
maybe its possible to integrate this feature:
If I have an numeric input field with defined limits (e. g. 0 = minima, 5 = maxima, step = 1, coerce all on).
Now I write a number in this field and Labview correct the input into the limits.
In case I write a number by property node "value", the limits doesn't matter.
I have to test the limits manually before writing in the numeric field by read out the limit properties and so on....

I figure out that when the value is changed using the property "Value", the coercing process work as expected. For the property "Val(Sgnl)" the limits are ignored. This is on purpose?
I made a small program to test it. If the "input" is placed in a value out of range and "Signaling" is turned on and off couple times, the "output" stays or of range! Or i'm missing something or there something really strange here.

Problem with the Value property node (MacOS)

As far as I have tested it, Value Property nodes (and Value (signaling)) don't work in MacOS : The value property appears as a boolean, the value(signaling) as a cluster (width, height).
Even with boolean controls, the node is not working.
No such problem in LV 8.6.
Am-I missing something ? Is that some "intended use" ? Or simply a bug ?
Chilly Charly (aka CC)
E-List Master - Kudos glutton - Press the yellow button on the left...
Solved!
Go to Solution.

That sounds like some sort of indexing problem with the property nodes like somesort of corrupted installation. What if you just delete the property node and recreate it?
I dropped a numeric control and looked at the shortcut menu for the list of property nodes. Right below Value and Value (signalling) are Visible (which would be a boolean) and Xcontrol, which when you step down through the submenus, the first choice is Container bounds, a cluster of Width and Height. So these 2 datatypes that are 2 lower on the list match the ones you are getting.
What happens if you pick another property node a few elements up or down on the shortcut menu? Does is happen for some other properties, and if so, are thereany properties that are okay?
Here is what my property nodes look like for a numeric and I draggged the box up and down to show the natural order of the property nodes. Note that I have scripting installed, so there are a few more property nodes (and the blue box at the top) that you might not have.
PS. Check you signature. The Kudos button is now moved to the left since the forum upgrade.
Attachments:
Example_VI_BD.png ‏4 KB

When i change the value of a combo box using a property node it displays the value not the item label

I am using a combo box as a select list for text serial commands. I have items like "engineering", "GUI", and "Scan" for the commands "MDE", "MDN", and MDS respectively which i have input as the corresponding value in the combo box. so for example the label "engineering" has the value "MDE" in the combo box items list. when the Vi starts it needs to read the current value MDE, MDN, or MDS and then i want it to display on the front panel the item text corresponding to that command value.
To do this i have tried to read the serial command, ie MDS and then wire that to a "value" property of a property node of the combo-box, but instead of displaying the corresponding item label, "Scan", it displays the value "MDS" on the front panel instead. i want the front panel to use the label text when choosing and displaying but the block diagram to use the serial commands. Can this be done with a combo box? I'm trying to use a combo box so i can keep it all text and avoid having to build a case statement to convert enums or rings from a numerical value to the text command.
The correct text value is wired to the value property and it does exist in the combo-box. I have unchecked "values match items" and selected to not allow undefined values.

Don't use the value property node. Use the Text.Text property node. When creating the property node, select Text, then in the next pop-up box, select Text.
- tbob
Inventor of the WORM Global

Validation of numeric value precision and scale

Hi all,
Iam using ADF with EJBs.
I have one inputText field that will accept numeric values (of java.lang.Double type). Due to database constraints I want to validate the input value on its precision and scale.
I put an f:convertNumber tag under the inputText and set the MaxIntegerDigits and MaxFractionDigits properties with the desired values.
I also set the ApplyValidation property of the corresponding attribute in the pagedef file. However no validation worked.
I made the same test with af:ConvertNumber with no result too.
I know that with BC4J it is easy to set such constraints at the entity level.
Is there any neat way to set validation or I need to write code in the backing bean?

<af:convertNumber> works fine for me. see the following code
<af:inputText id="it1">
<af:convertNumber type="number" minFractionDigits="2" maxIntegerDigits="4" maxFractionDigits="2"/>
</af:inputText>
Another possible solution with regular expression
<af:inputText id="it3" value="9999.99">
<af:validateRegExp pattern="\[0-9\]\[0-9\]\[0-9\]\[0-9\].\[0-9\]\[0-9\]"/>
</af:inputText>
regards
srini
Edited by: sangara on Jan 17, 2010 9:53 PM

Is there a way to reference the property node value of a control in another VI?

Let's say that I have a situation like the one shown in the attached image.
I have an interlock system which is basically a bunch of booleans
If for example the "RF Enable" button in the "interlock VI" is true, then I should be able to flick the ON switch in my other VI (in the back), but if the value is FALSE, then it shouldn't allow it.
In other words, how do I check the value of a control across 2 separate VIs (running simultaneously)?
Thanks!!
Attachments:
sample.jpg ‏295 KB

Is one VI launched by the other, or are they launched independently? If it's the former then you just need to pass the control reference to the subVI via terminal node. If it's the latter there are a variety of ways to handle this:
Use a global variable - somewhat "sloppy" as it requires a global variable, and can lead to race conditions. In the "Interlock" VI you just set the value of the global variable when you change the value of the Boolean. In the other you're just reading it.
Action Engine - Ben wrote a Community Nugget a while back. Similar concept to a global variable.
Queue - The "Interlock" VI simply pops an element onto the queue with the value. The other VI just monitors the queue for a new element. It just needs to have something like a shift register to keep track of the last state.
Use the VI Server to access the controls of the "Interlock" VI. You can do this by accessing the "Interlock" VI's pane and get the control references. With the control reference you just need to get the value with a property node.
... (I'll let others chime in)

Is it better to use Invoke nodes or property nodes to set/get control values?

I have a series of VI's that run in parallel, each to manage different functions- pumping, sensing, a fluid flow model, an experiment generator/runner.
These need to exchange data, which I am currently doing using invoke nodes (that are all in subVIs), using methods "Set control value" and "Get control value". I find that every now and then (perhaps 1% of the time) the data isn't exchanged correctly and therefore the system doesn't work. I can imagine how "set" could go wrong if they happen simultaneously, and can devise ways of preventing this. However, the "Get" method suffers from the same problem. This is a major problem, because I want to leave it running for several hours.
I could in
principle achieve the same thing using property nodes and find myself wondering if this might be more reliable. But I don't want to change over only to find it makes no difference!
Can anyone advise?

You can use some kind of syncronization such as queues, occurances, or notifiers but I think the easiest way would be to create and action engine. This was only one action can execute at a time avoiding a "race condition". Possibly a write action and a read action might help. You also can add queues or notifiers into this concept. hope this helps.
BJD1613
Lead Test Tools Development Engineer
Philips Respironics
Certified LV Architect / Instructor

Just checking on another odd feature: Typedef enum Property Node "Value" not reflecting changes in the Typedef?

Just encountered this odd behavior in LV 2011 which I reduced to the following example:
- create a new VI and drop an enum control on te FP.
- make this control a typedef and open the corresponding typedef
- create a "case 1" item and a "case 2" item
- save the typedef (I used the name Typedef Control 1) and CLOSE it (this is to allow updating of the original control).
- drop a case structure on the diagram and connect the enum to it:
So far so good. Now create a "Value" Property node for the enum and use it instead of the terminal:
If I now go back to the typedef and add a "case 3" item, save the typedef and close it, the control is updated, but the Property node is not.
How do I know that? For one, the Case Structure contextual menu does not offer to create a case for every value. Also, if I add a "case 3" case manually, it turns red.
Luckily, the magic Ctrl-R key stroke actually does solve this problem.
Tested in LV 2011.

By Ctrl-R trick do you simply mean running the VI? That is one way to force a recompile, but if you hold down Ctrl while pressing the run button you can recompile without running. This should not be "dangerous" in any situation.
As you have drawn your example, I see no reason not to use a local in that situation (ok, maybe for vanity). Still, I view the behavior you describe as a bug, and it should certainly be fixed for the benefit of local haters out there. You have to be a little careful where you draw the line between what gets handled in real time and what gets handled only at compile time.

How do I use the Index Values property node with a multidimensional array.

I am using a 2D array to store operator inputs on my front panel. I only want to display one element to the operator at a time. I am trying to use the Index Values property node to change the displayed element. However, I can only get the Rows index to work. How do I direct the Columns index as well? The help says to use one per dimension. I need clarification on what this is talking about. I've tried adding a second element to the property node, 2 seperate property nodes, and diferent wiring techniques. (series, parallel)

If you only wire up one of the inputs (col or row) what you get out is a 1D array of either the column or row. If you wire controls to both, then you will get one element out of the array. Getting a single element in a 2D array requires you to specify both a row and column.
Message Edited by Dennis Knutson on 02-08-2007 08:34 AM
Attachments:
Index 2D Array.PNG ‏2 KB

Help comparing the value of a button using the Property Node (I get a variant)

Dear Sirs:
(I'm using LabView 6. I guess the solution is different for 6.1)
Currently I have created an array of Boolean RefNums (which point to many, many buttons). When I need to know when any (and which) of the buttons was pressed I just compare every element on the array with the constant TRUE. It fact, as the array is built from RefNums, I should compare the VALUE from the Property Node.
The problem here is that the Property Node for this type of Boolean is a LV Variant, and I need to compare this with a TRUE/FALSE value.
I tried to convert the TRUE constant to a LV variant and visc. But nothing works... I always get that none of the buttons was pressed.
Here it co
mes the question: "How can I compare the value of a Property Node for a Boolean (Button) with a TRUE (or False) constant?"
BTW, maybe I should explain why I'm using RefNums instead of the direct values: As my project requires tons of buttons, I would preffer using RefNums to refer to them. (I.E. I could use a single VI that takes the RefNum and formats the button to hide it for certain users).
I have enclosed a VI that contains what I've achieved until now, which is nothing
I appreciate your time and help.
Best regards,
JAVIER VIDAL
Attachments:
Other_Main_Menu.vi ‏103 KB

Javier,
There is another problem in your code: the booleans are not polled by the main loop so they will remain false until the user presses them again. This renders the boolean latch action useless.
What you can do is to change the mechanical action of the booleans to non-latch. When you detect a "true" in the polling loop, set the boolean to false again. One added benefit is that once all boolean are non-latch, the value property won't be a variant but a boolean so conversion is no longer needed.
LabVIEW, C'est LabVIEW

Why is the Value Property Node of a Typedef control not typedef itself?

This is not preventing me from progressing, but I am puzzled by what I am seeing on one of my diagrams (LV 2011).
I have a typedef control which I am reading around my diagram and passing to some subVI. For this purpose I create a read "Value" Property Node and pass the value to the subVI.
The subVI uses the same typedef control as that in my calling VI but nonetheless there is a coersion dot on my calling VI's diagram when I connect the "Value" to the subVI connector. Why?
The closest to this discussion I found was this old one, but it did not end up with a final answer.... It turns out that the typedef control I am talking about is an enum, but that does not matter.
As a matter of fact, if you connect the Value output of a Property Node to a sequence and create a subVI from that sequence, the corresponding control has lost any link with the typedef. In other words, the Value property node of a typedef control is not a typedef. Why?

[...] Why?
Because you haven't posted an idea here.
Well.. maybe you or somebody else has and I missed it, after all there's more than 14k ideas so for just for LabVIEW.. What? Who said that means there's a lot of room for improvement in LabVIEW??
Jokes appart, if there is an idea, please give the link.
When my feet touch the ground each morning the devil thinks "bloody hell... He's up again!"

Significant digits not obeyed when value set through property nodes

Hi, I have a front panel with a large number of indicators on it. As updating each one is a very straight forward task, I am using the This.Panel.Controls array to step through and update each indicator appropriatly. The problem is, that because I have so many indicators, and the actual numbers aren't that important (they are also being logged elsewhere) I only wish to have 4 significant digits displayed so that the value fits into the size of the indicator. I set each indicator to have a display format of %_4f, but when I run it this is not obeyed and 7+ digits are displayed. I'm guessing this has something to do with updating the controls via the property node, but I'm not sure why that should cause an issue. Any ideas?

Nope, I double checked the format string. I do mean significant digits by the way. My imput values are expected to be in the range 0-100 but I've sized my indicators to fit only 4 digits, which will give me at worst a 0.1% error over the full range, which is good enough. Right now the channels from which I am grabbing data are all disconnected, so I am just getting noise. I've attached images of both the format string I'm using, the relavent part of my code where I update values, and an example of the output I get. Thanks,
Jon
Attachments:
FormatString.PNG ‏32 KB
ouput.PNG ‏2 KB
ValueUpdating.PNG ‏25 KB

I'am having problem with a graph property node by using format & precision

I would like to display an amount of data in a waveform graph and to choose the X scale to display absolute time (whitout date information) or scaled decimal value.
Absolute time is a must because the scaling should reflect the acquisition time and not only a value in hour, minute and second.
Using the property node I can choose between 10 differents formats (0-Decimal, 1-Scientific, 2-Engineering, 3-Binary, 4-Octal, 5-Hexadecimal, 6-Relative Time, 7-Time and Date, 8-SI, and 9-Custom).
Format 7 - Time and Date should be a good choice but LabVIEW set automatically system time AND system date without any possibilities to change anything.
Trying format 9 - Custom ends everytime with error 1077 (invalid property value).
Any help to explain me how to use the format Custom or to give me a solution to switch between time (no date) and decimal scaling is appreciate.
Thank

In addition to the Xscale.Format property node, you also need to set the XScale.FormatString (see a little below the Format entry).
Use %<%.0X>T as format string.
Chilly Charly (aka CC)
E-List Master - Kudos glutton - Press the yellow button on the left...

Precision property node in numerical value

Similar Messages

Maybe you are looking for