NI TestStand Idea Exchange

Top Authors

User

Kudos

Post an idea

This idea mostly goes along with this idea. I use type def all the time in LabVIEW, especially with enums. TestStand can interact with my VIs with enums, but they are handled as a number. Furthermore, if the enum gets changed, the wrong value of the enum is often used. I really like the idea of custom data type of an enum. The ultimate would be if I only had to alter the enum once (in ctl file) and TestStand would automatically update its data type. This should be the same for clusters.

Sequence File Validation

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.

It would be nice to be able to create a new sequence from highlighting steps in a sequence and performing a right mouse click, "Create New Sequence...", this would be a kin to Create SubVI in LabVIEW.

This action could display a dialog to give possible options such as, to copy the Setup and/or Cleanup group, Create in a New SequenceFile or in Current SequenceFile, the option to Move or Copy highlighted Steps. It could also include creating any locals and /or FileGlobals (if creating in a new SequenceFile) used by those highlight steps.

View All (3)

It would be nice to be able to "fold" control flow blocks (like if - else -end, while - end etc.). Despite the vertical lines connecting the control flow steps on the same level, it is sometimes very hard to find where a long control block actually ends or what the condition for the "end" is you are currently looking at.

In such cases it would be helpful, if the entire control flow block could be hidden under its first line, tree-view like with a +/- icon to show/hide the interior of the block.

Regards

Peter

Add Debugging feature: Execute to cursor

It would be nice to have the same debug feature like in Visual Studio

There is a possibility to run/execute to cursor's position.

At the monent there is only "set next step to cursor" but this is not compareable with this feature.

Well, I know could set another breakpoint and resume to it. But most times i will forget to delete it....

So why not this stuff ?

Regards

Juergen

Even though we already have an About box for TestStand, it would also be nice to have one for the active TestSequence file as well. The Help menu would have a new item called "About MySequenceFile ...".

MySequenceFile About box splash screen:

The information in this screen should be loaded directly from a single FileGlobal string whenever a sequence file is made active. This can probably be done already by those that know how, but it should be already part of TestStand by default.

Eugene

View All (12)

It would be nice if the Step Settings for a Sequence Call step's Module tab would also list the calling sequences comments field and the parameter comments in addition to the prototype information. This would allow sequence calls to easily present information on the expected use of the sequence, along with parameter information (ranges, default options, etc) that would be useful to the developer. I've created a simple mockup of what I'd like to see here:

By adding these features, sequences can contain their own 'help' information which would allow the developer to configure the call without having to leave the step module dialog.

Thanks,

-Jack

VIPM for TestStand

FTP: Specify settings by expression

It would be nice to make Sequences public or private within a SequnenceFile.

With this you where able to make powerful SequenceFiles librarys. The biggest advantage of this

is you can show the consumer of the library only the "important" public sequences. The

private ones where invisible. This will help to avoid errors.

Regards

juergen

Hi,

I think this Thread should be placed here.

http://forums.ni.com/t5/NI-TestStand/How-to-create-a-build-in-User-StepType/m-p/1134151

The aim of this is that users can create the same powerful steps like that once which comes from NI.

Biggest enhancement of this would be that i can get rid of the "edit" - button and there is no floating panel

somewhere else.

The second enhancement is that i may use drag and drop between the edit and variable panel (if this is neccessary).

Like Manooch_H I am interrested in comments, too

Regards

Juergen

A TestStand configuration wizard

I would like to see a TestStand configuration wizard that would walk a developer through a checklist of all of the most important configuration settings and generate recommended changes.

It is best for a developer to be already familiar with Best Practices as in the following link:

Best Practices for Improving NI TestStand System Performance

http://zone.ni.com/devzone/cda/tut/p/id/7559

However, it would also be nice to have assistance in recording WHY certain choices are made as shown in this image:

Eugene

View All (3)

Professional Development package should include source code control (SCC) and Requirements Gateway right out of the box.

I know that bundled SCC was a problem in the past that NI wants to avoid, but I feel that a "Professional" development system isn't very professional without it and Requirements Gateway. However, It is very difficult and painful for me to get separate funds approved for important items that really needs to be already there right out of the box.

I already use free SVN, but TestStand does not recognize it, so it is not "integrated".

Eugene

View All (4)

Define Variables as Constant

Everyone should be familiar with the Sequences pane. In it, we get fancy icons for certain callbacks, but I'd also like each sequence reveal more information about the sequence's settings, and my first thought was to use helpful overlays for the icon. If you take a peek in the Sequence Properties dialog, you'll see there's three different tickboxes there that (can) radically change how a sequence executes. Unfortunately, I don't have any awesome ideas on how these could be presented (especially all at once) - it'd be pretty tough to fit all that discernably into a 16x16 icon. Both Comments and Requirements are visualized clearly, but I would just as soon trade the Comment column for a way to display these settings.

I'd be even more thrilled if the SequenceCall step type could also find some visual way to display this information, but I guess we should probably take this a step at a time 😉

View All (4)

NI TestStand Idea Exchange

Link Custom Data Types to LabVIEW Type Defs

Sequence File Validation

Updating sequence call names automatically

Ability to SELECT / INITIALIZE test resources for UUT before performing TEST.

Tool to create Sequence from Highlighted Steps

Folding editor for control flow

Add Debugging feature: Execute to cursor

Forward/Back Button - navigate like a browser

MySequenceFile About box splash screen

Display Sequence Call target Sequence and Parameter comments in the 'Step Settings for ' Module tab

VIPM for TestStand

FTP: Specify settings by expression

Add some OOP feature to a seqeunce

Ability to create user built-in StepTypes

A TestStand configuration wizard

Professional Development package should include source code control (SCC) and Requirements Gateway

Define Variables as Constant

Visualization of Sequence properties through the Sequence's icon

Beable to pass parameters with the Sequence used in Post Actions

Cross-linking the wrong LabVIEW VI code modules