Populate ENUM RING via Property Node String[]

Can you populate an ENUM Control using it's Property Node String[] Element? If not, is there a way to do this programmatically? So far I have failed to do this.
I am Using LV6.1.
Thanks

Mr. Kring can probably come up with a much better example, but here's a quick one-off example in LV 6.0.2.
Download both attached files. Open enum_target.vi, and note that the enum shows only a single choice, "Before". Open Change_enum.vi, and point the file control to the enum_target.vi. Run the Change_enum.vi. The contents of the Enum control in enum_target.vi should have changed to the string array in Change_enum.vi.
This is a simplistic example, but it should work. Explanations are given on the diagram of Change_enum.vi of how references are pushed around in it.
Attachments:
Change_Enum.vi ‏39 KB
enum_target.vi ‏7 KB

Similar Messages

How to read the configuration of a FXP number via property nodes or other methods.

Hello all,
I am attempting to store in plain-text the value and configuration specifics of the LV FXP datatype. (please do not suggest I cast it to integer).
The ini config format does not support FXP. So we'd like to; using property nodes, interrogate the specifics of a FXP numeric control on the FP.
It appears this is not exposed by control ref's and property nodes.
Oddly enough, you cannot even interrogate the detailed type of an INT if it is a U8, I8 or I16 etc?! via property nodes, the deepest you can go is 'digital'.
Specifically, you need to know the following to 'reconstruct' a FXP:
1. Value
2. Signed\unsigned
3. Word length
4. Integer word length
Without this, there is a risk of corrupting the value during conversion.i.e we want to load initial FXP from disk at application startup. This is a critical application and we cannot tolerate rounding\conversion errors accumilating with numerous reads\writes of FXP settings.
It is odd that you cannot interrogate via property nodes the details of a numeric type. ie. you cannot 'discover' via the property node of an INT if it is a U8, I8 or any other type.
Regards
Jack Hamilton
PS: Don't suggest XML either....

Aristos Queue wrote:
Alias name here wrote:
..second post telling me the 'propertys' of a control have nothing to do with the value is bizzare - via 'properties' for a LV control is the ONLY way to configure the specific type of a numeric...so via the numeric 'property nodes' should\would be able to query it's configuration.
I do not see any way to set these things through the properties...
I think he means by right clicking the control on the front panel and configuring with the properties dialog. The properties are exposed there, but not within the property nodes.
Edit: You beat me.
CLA, LabVIEW Versions 2010-2013

Error 1082 when setting Strings[] property of a menu ring control via property node.

I've attached a VI in which I attempt to set the Strings[] property of a menu ring control via a property node. Can anybody figure out what I'm doing wrong here? I'm using LabView version 7.1.
Thanks,
Mark Moss
Attachments:
Bug Test.llb ‏69 KB

Open up your Stations Parameters Control.ctl file and change it from a Strict Type Def. to just an ordinary Type Def. (the pull down menu is located next to the font selector).

Cursor: Bring to Center via Property node?

The pop-up menu on the Cursor Legend for graphs includes an item: Bring to Center which moves the active cursor to the center of the plot.
Is this capability available programmatically? An Invoke Node method or Property Node? I would like to have a button on the FP which "retrieves" a free cursor. I can see complicated ways using Cursor Position and Scale: Range property nodes. I could not find anything as simple as the pop-up menu.
Lynn

Bublina wrote:
It works OK, but I used it and I remember it failed to work for extreme zoom levels (nothing happened)
Do not remember if the inbuilt functionality failed aswell.
Edit: It did
I take the Edit as "it fails as well". At least, it wouldn't surprise me if you meant it differently.
The reason:
Extreme zoom levels usually mean, that both endpoints of the scale do have a very small difference. Since the center is (at least in altenbach's code and i assume that the context menu function works similar) the average of both endpoint values, the difference between endpoint and average cannot be covered by the used numeric representation. So it computes an average, but that equals to one of the endpoints......
So this is rather a "works as expected" issue, even if not very nice and most likely considered a bug by the user (without above explanation).
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Waveform Names to Menu Ring String Property Node

Hi,
I am extracting waveform data (names) to go into a menu ring as string data.
It seems to work, apart from when you actually click on the menu there is no text (though you can successfully change it). I am wondering if it is to do with the odd symbol in front of the name but not sure how to get rid of it.
Hoping it is something simple but it is just knowing where to look with all the options available to you.
Please see attached.
Best Regards,
James
Solved!
Go to Solution.
Attachments:
MenuRing.jpg ‏23 KB

Hi James,
You were 99% of the way there all you needed to do was to pull that weird character from the string, I used the “match pattern” function to allow me to isolate that character and pass the resultant string into the text ring property node. A good bit of advice if you find a character in LabVIEW that you do not recognise or if you are unsure about spacing, right click the output string and select “ ‘\’ codes display “ this will show what the code representation of the string is and you can just feed that directly into the “match pattern” function. I have attached my code (LabVIEW 2010 if you need in previous version please just ask) for you to have a look at. I have used a producer consumer template and selected multiple input channels from a simulated PCI 6220.
P.S. I’m not sure where that character comes from??
Regards
Andrew George @ NI UK
Attachments:
Forum James AC.vi ‏26 KB

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.

Using a property node of a menu ring to generate a secondary address does not work in a subvi unless the subvi has been or is opened. Why?

I am writing drivers for third party equipment using LabView 6.1. I am using the property node, digdisp.text, to get the item number of menu ring. This number is being used as the GPIB secondary address for the equipment. This vi is one many subVIs like it in a main vi.
The only way the main vi works consistently is if I open all the subVIs, otherwise the secondary address isn't picked up and I get a EARG and ENOL error in NISpy and a GPIB write error in the Error Out cluster.
I have attached an example of a NIspy capture of a failed attempt.
Attachments:
Capture.spy ‏9 KB

Hi,
EARG (4)
Error Condition: Invalid argument to a function call.
Description: EARG results when an invalid argument is passed to a function call.
Possible Cause: The following are some examples: you call ibtmo with a value not in the range 0 through 17 (possible timeout values correspond to a table of values ranging from 0 to 17, where the default is 13, which represents a 10 second timeout); you call ibeos with meaningless bits set in the high byte of the second parameter; or you call ibpad (or ibsad) with invalid addresses.
The reason you are getting the error is because not only is your secondary address invalid, but your primary address is also invalid. Lines 14 and 16 of your attached NI-SPY capture set
the primary address (ibpad) and secondary address (ibsad) respectively. You need to make sure that you are passing the addresses properly to the subVIs using a connector. It seems like your programming when sending and receiving data (like the addresses) from your subVIs is not correct. You have to be sure to pass the data back and forth in the proper method using connectors.
A.S.
Anu Saha
Academic Product Marketing Engineer
National Instruments

Tree Control Property Node for Accessing "Child Text" String Array

When adding items to a tree control using the EditTreeItems invoke nodes, the inputs include "Child Tag", "Item Indent", "Child Only?", "Glyph Index", "Child Text", and "Left Cell String" as can be seen in this screenshot.
There are property nodes for the tree control for accessing each of these elements, except for the "Child Text", which is an array of strings. It is possible to access this data as outlined in this forum post, but this method is somewhat involved and round about.
I suggest that a property for the Tree class be created to access the Child Text array directly.

The work around only works if you do not have an empty string element some where in the middle.
At lest could the "Active Celltring Property" read return an error when you have gone beyond the end of the array.

Different formats for each line in enums & rings?

I don't know if this one is possible but I can't figure it out.
Can you make an enum or ring control have a different format for each selection?
E.G.:
Selection 1 [default]
Selection 2 [test mode]
Selection 3 [optional]
Selection 4 [optional]
I've tried the formatting options and property nodes, no luck. Maybe there are possibilities with control customizing I'm not thinking of???
Thanks & Regards,
K
Using LabVIEW: 7.1.1, 8.5.1 & 2013

Hi K.
I don't think it's possible to have those text properties vary in a text-ring, but you might be able to accomplish your goal using a pict-ring - using images of formatted text. In the example (attached) Paint was used to create the pictures then import them into the pict-ring. Here Unclebump shows how to use "Draw Text at Point.vi" to create formatted text in a picture control, though, I have no idea how to copy such pictures out of the pictures control!
Cheers!
"Inside every large program is a small program struggling to get out." (attributed to Tony Hoare)
Attachments:
FormattedTextPicRing.vi ‏14 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

Tentative bug report: property node (and other objects) resizes structure in which they are dropped even when this is not needed

This one has bugged me for a while, so, since I am in a mood to report annoying features, here it is:
On the diagram, when you drop an object that could have its size increased by user action (for instance a property node in which you chose "Value", which is a short property, but you could later change this to a "longer" one, which admittedly might require more space on the diagram), a case structure in which you drop it, will automatically increase its size.
Let me illustrate this with ONE example (can be reproduced with other objects such as enums, clusters, etc...).
Here is a simple diagram:
Note that I am going to create a property node from the front panel. This, for a reason that makes the beauty of this "feature", is very important. Apparently, if you create the property node from the diagram, nothing weird happens. The exact location where I will drop the node is not very important but needs to be close enough from the border.
Here is the result (LV 2011 but as I said, this has bugged me for a few versions already):
Basically, the case structure (and the whole diagram as a matter of fact) has expanded.
This is particularly annoying, say, when you are creating a diagram with 10 cases in a case structure and you start dropping things such as property nodes in each case: the structure keeps growing, and growing, and growing...
That also works with Event structure, and I am ready to bet, with other as well.
As I said, it is also not limited to Property nodes. I have noticed that this happens if you drop a cluster constant that contains an enum (presumably because some of the enumerated strings are longer than others).
I could speculate why this is the case, but that is not my job.

Actually, this might not be true. I found a variant of this behavior. With "Place Structure with Auto Grow enabled" unchecked, here is what I observed while dropping a property node on my diagram:
Before:
After:
This is the expected behavior. The Property Node is partly hidden inside the Case Structure I dropped it in. Now that's not what I wanted to do. I wanted to drop it in in the innermost Case Structure:
The problem is that now this Structure has grown (as has the whole diagram) to leave space for the whole Property Node:
It is a subtle bug in the sense that I tried to reproduce it on a new VI with a series of nested Case Structures, but it did not result in this behavior.
Anybody caring to comment?

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

Font change in text enum ring and display issue

Hi,
I was finally able to update the text in a text ring programmatically, but for some reason, when I choose it as a drop-down menu, I just see blanks. Also, for some reason, the font used is changed - it is more spread out and and block letters. Any ideas why this is happening? I am using the "strings[]" property from a property node to update the items in the list.
Thanks,
Jason

Hi Jason,
Can you please post a simple VI that demonstrates this issue.
Ankita

Problem in writing to a property node of a cluster

Hello together!
I have a problem in writing to a property node of a cluster which contains several control elements, such as combo boxes or string controls.
I would like to set the options to choose for an array of such clusters.
I tried to do this by writing to property node --> value, but the the control element in the cluster does not remain a control, but instead an indicator. The can't choose one of
the options that I set. So I further set the property node --> indicator (of the cluster) to "False", with the purpose to keep the control as a control. This results in a comment from Labview,
that this is not possible as long as the Vi is not in edit mode. I don't understand this comment. If I look to Labviews toolbar "Operate", I see that I am obviously in edit mode.
If anybody could help me, or suggest a better solution to solve my problem I would be very glad.
Thanks a lot!
Woodi
An example of what I tried to do:
Attachments:
How to write to a cluster.vi ‏42 KB

I took the liberty to modify your VI for an alternative approach (LabVIEW 7.1). You should keep your array of 32 clusters in a shift register and show only a single cluster as a front panel control.
Selecting a different transducer from the listbox on the left will load its settings into that control via a local variable.
Any changes to the settings will modify the currently selected array element
At any give time, a boolean array shows which transducers have changed settings
At any given time, a listbox summarizes all settings.
Let me know it this makes sense to you. These are just some ideas, modify as needed. Good luck!
LabVIEW Champion . Do more with less code and in less time .
Attachments:
How_to_write_to_a_clusterMOD.vi ‏87 KB

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)

Populate ENUM RING via Property Node String[]

Similar Messages

Maybe you are looking for