NI TestStand Idea Exchange

Community Browser
cancel
Showing results for 
Search instead for 
Did you mean: 
Post an idea

The idea here is to have a widow that you can execute expressions while at a breakpoint or paused.   I would also like to be able to execute the expression while not running the sequence.  Many times I am not sure how will be returned by an API expression and it would be nice just to execute it.  I know that not all expressions can be executed outside running the sequence, but many can.  This would be a nice feature so you can test expressions without running the whole sequence.

 

Allow the configuration portion of steps that call DLLs to see mangled function names, such as those generated by many C++ compilers (@Initv, for instance).

TESTSTAND is capable of interfacing so many devices & instrument to a UUT.

 

Incase of ATE(Automatic test equipment), where lot of resources are made available to test the UUT, not all the resources or instruments will be used through out the test for a particular UNIT. Hence there should be facility to select the resources required for particular test, which will be then only initialized & used.

 

For example a simple power device requires only POWER SUPPLY, LOAD & DMM. Where as a data acquisition system requires POWER SUPPLY, DIO & AIO cards & so on.

 

Thus one should only select the resources required for test & hence no need to have init function separately for each sequence. This may sound a bit complicated but It really helps for LARGE ATEs, where optimization is KEY. Same thing can be implemented for TERMINATING resources once test is done.

I'm often traversing through many subsequences (both separate and contained), and I'd like a "back" button - just like the one in Requirements Gateway - so I can quickly move back through the list.  A "forward" button might be useful too I guess, but I'd be more keen on getting a "back" button first.

There is often problems with cross-linking the wrong LabVIEW VI code modules. Why not automatically import VIs into TestStand from LabVIEW projects using the name of the LV project as a name extension for each VI in TestStand?

 

For example, if the name of the LV project is "Project 1.lvproj" and contains VIs named A.vi and B.VI, then these could easily be loaded into testStand as "A-Project 1.vi" and "B-Project 1.vi"?

 

 

Eugene