Drop down menu to populate fields used for testing

[mrrcx]

Hello,

I have asked a few questions on here and everyone is very helpful thank you

My current question is related to drop down menus.

What I want to do is have the end user be able to select the testing item from a drop down menu and all of the values associated with testing that item.

The associated values will need to be used in the testing function so the test can run properly.

Things such as offsets, loads, and other values are what I am talking about.

To clarify...

have a drop down menu where you can select which item you are testing, and once selected have the associated parameters populate and be used during the test.

After searcing the forums for a few hours I was un able to find any other question or example similar enough to what I am trying to accomplish

Thank you!

[Todd_Lesher]

See "enum" or "ring".

[AnkitG]

---

@mrrcx wrote:

Hello,

I have asked a few questions on here and everyone is very helpful thank you

My current question is related to drop down menus.

What I want to do is have the end user be able to select the testing item from a drop down menu and all of the values associated with testing that item.

The associated values will need to be used in the testing function so the test can run properly.

Things such as offsets, loads, and other values are what I am talking about.

To clarify...

have a drop down menu where you can select which item you are testing, and once selected have the associated parameters populate and be used during the test.

After searcing the forums for a few hours I was un able to find any other question or example similar enough to what I am trying to accomplish

Thank you!

---

hi mrrcx,

You can use ring, enum or combo box. please see attached example, hope this help

---

[mrrcx]

Ok Ill take a look!

Anyway you can make that example for 10.0.1?

Thank you

[AnkitG]

saved it for 10.0 version

[df86]

Here is a taking their suggestions one step further incase you are still in need of help.

Good luck,

[mrrcx]

The example from df86 is more along the lines of what I was taling about.

you select 1 thing and it changes multiple inputs.

2 questions on that example though

1-

how do you enter new data for each test option?

2-

how can you use that stored data once selected for actually performing the test...

i.e. if i use a numeric control then i can branch off and use whats entered but how would i do that in this case?

The data will not all be numeric, some will be strings.  is it possible to combine those under 1 drop down and use the pre entered values for the test?

Thank you

[df86]

For quesion two, look at the revised VI attached.

For question one, It depends on the information. If the information for the test results will always remain the same you can modify the constant which gets indexed. Other opetion is at the Initialization of the software, read the information out of the file, this way you can change the values by modifying the file. Or third option is have the user input the options as they see fit at the beginning using the control. The attached VI is showing this option. 

Dan,

[mrrcx]

Yes this example is what I was getting at!

Thank you

i looked up how to add and modify the ring, but for the 'test info' box, how do I add more data boxes to enter.  I know for the outputs I will have to expand the object with more offest/multiplier fields.  when i expand the box it duplicated the origional.

also what is the purpose of the timer?

[df86]

So the main control is an array of clusters. If you would like more items added to the array, (if you are adding more test cases), just move the index up until you see a grayed out box and then type in the values you would like. the you can right click on the control and go to the data operations and select "Set Current Value to Default".  If you are talking about adding more content, (ie offest, multiplier, Test name, Test S/N). just grab the control type of the data you would like to add and drag and drop it on the cluster in the front panel. 

As far as the timer, it's there to reduce the frequency of how often you run the loop. Right now it's set to run the loop then wait 100ms before running again. This way you do not choke your processor.