From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

NI TestStand Idea Exchange

Post an idea

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)

The Step Type Messaga Popup .

Usually I use the same text in the Step Name for the Title Expression

and for a long time now I have used NameOf(Step) in the Title Expression so as not to have to duplicate the Step Name.

Now that Templates are available I can save a copy this version to use instead of the default step type. But thats only true for my development PC.

This may not be saved on other development PC.

What would be nice if the default value for Title Expression was NameOf(Step) instead of "untitled".

regards

Ray Farmer

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

View All (8)

How many of you would benefit from the addition of a feature similar to LabVIEW's Quick Drop?

The functionality that initially comes to mind would be typing to search for your desired step type or step template and dropping it into the sequence you are developing. Please add comments for any additional functionality you might like to see in a TestStand step Quick Drop (for example, you may want TestStand to automatically navigate to the Step Properties of a step after it is dropped from Quick Drop).

Please also add comments for any other situations/scenarios (outside of adding steps to a sequence) where you might benefit from a Quick Drop-like functionality. Thank you.

View All (1)

Recently ran into a problem when I was configuring a LabVIEW module that passed in/out clusters/types. I had a mistake in my code that the teststand data type was not configured to allow it to pass to LabVIEW clusters, but the problem was not as obvious as I thought it should be.

Here's what I had:

And when I click on the red checkmark "check expression" for "Cluster", it shows up as "No Errors". Everything looks great, right? Well, it isn't.

It's not until I expand "Cluster" to show the elements that I see that there are connectivity problems.

It would be nice if "Locals.mylocal" expression would turn RED and show a "check expression error" if any of it's children also had a connection problem (specifically in this case that the type in TestStand was not configured to allow passing to LabVIEW clusters). This way it would be a lot easier to see.

Even worse, this problem is NOT found by sequence analyzer -- it's left to be found at runtime.

I know this is all because I had a bug/mistake in my code, but it would be a lot easier to track down and fix if these changes were made.

Right now it appears the sequence analyzer has no really effective automation options?

I can use the command line to launch the Sequence Analyzer, but I really want to run this puppy headlessly against a codebase every 24 hours similar to how VI Analyzer works. Ideally, yes, I'd love a full API, but for the short term, would it be possible to expand the command line?

what we have currently is:

AnalyzerApp.exe "C:\My Documents\MyProject.tsaproj" to get the window open with the right project in it.

what would be seriously helpful would be to add: some sort of "-Run -Report "C:\Reports\MyProjectReport.xml"" additional tags?

In general I'd love for the tool to (1) launch, (2) run project, (3) save off file, and (4) close without further nagging on the part of a user.

Extra kudos would be given if it could generate a standard-out message with some quick stats, if someone was feeling really gung-ho. Perhaps a # of rules, run and # of errors & warnings found? I can just as easily rake the xml output, so these aren't required, but I am in dire need of a way to automatically _get_ that xml output.

If the tool already does these tasks than please feel free to say so? I've combed the help in the versions I have installed, and so far have come up with nothing. I'm currently shopping around for a thin ui-robot to get the job done...

View All (1)

Hello,

For the moment Localization files are to be placed in TestStand public or TestStand user paths.

It should be interesting to move them in a custom directory, which could be configured in the stations options.

(Or defined somewhere in a TestStand project)

Doing so, would simplify the deployment processus ... and Localization files would not be treated as global files, but project files.

=> When you have to handle with many TestStand project, you could have a directory for each project ... with multiple localizations files different by project !

I think the mechanism of file managment of TestStand should be modified, in order ...