NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Combobox Questions

Hi everyone,

 

Got some basic questsions regarding creating combobox/drop down lists for Teststand.

 

I tried to search for this but seems like everything relatd to combobox is "created" or passdown from a DLL/VI or some adapter call.

 

What I am trying to do is either 1 of 2 things:

 

1.) I have a subsequence in TS I have created that contains a bunch of Parameters for.  Now on my high level Sequence, I do a sequence call, point to the subseq and now I have to input the parameters inside the module option.  My question is, is there anyway I can create a combobox so I can pre-define what can be added in via drop down list.

 

2.) I have a DLL adpater that gets called.  The DLL has input parameters that already contain comboboxes.  Is there anyway for me to pass on the comboboxes to another level?  In other words, I am creating a subsequence around DLL that gets called by a higher level seq.  The higher level sequence needs to input parameters into the subseq, which in some cases are the input parameters for the DLL.  When I tried to do this, the no combobox appears in the high level sequence, I can only see comboboxes in the subseq that directly calls the DLL.

 

Regards,

Mike

0 Kudos
Message 1 of 4
(3,496 Views)

Short answer to both: no

 

Long answer: Since 'enum' is not a native TestStand data type there is no way to natively represent a combobox or get a combobox-like effect for your variable. When calling a LabVIEW VI or a CVI dll, TestStand can read the enum information from the code module and thus will populate the parameter entry with a list of options.

 

Your best bet would be to try something similar to this and also post on this Idea in the Idea Exchange.

CTA, CLA, MTFBWY
0 Kudos
Message 2 of 4
(3,481 Views)

Gah that's too bad.  Thanks!

0 Kudos
Message 3 of 4
(3,453 Views)

I too wish for this feature.  I've been charged with developing a platform of sequences that will run a fairly involved peice of ATE where the other engineers might not know 100% the details of what happens behind the scenes of the sequences they call.  It would be a lot easier to just restrict what they can pass as parameters than to have to add all the "error" checking which they won't see until they try and run the sequence.

0 Kudos
Message 4 of 4
(3,412 Views)