NI TestStand Idea Exchange

Community Browser
About NI TestStand Idea Exchange

Do you have a feature idea for how to improve NI TestStand? Submit and vote on ideas now!

  1. Browse by label or search in the TestStand Idea Exchange to see if your idea has previously been submitted. If your idea exists sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click Post New Idea to submit a product idea. Be sure to submit a separate post for each idea. Note: the TestStand Idea Exchange is not the appropriate forum to submit technical support questions.
  3. Watch as the community gives your idea kudos and adds their input.
  4. As NI R&D considers the idea, they will change the idea status.
  5. Give kudos to other ideas that you would like to see implemented!

The TestStand R&D team is committed to reviewing every idea submitted via the TestStand Idea Exchange. However, we cannot guarantee the implementation of any TestStand Idea Exchange submission until further documented.

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

Forgive me for the cavalcade of suggestions this week...

 

One of my favorite options in the LabVIEW development environment is the "Find all Instances" context menu option, whereby one is able to locate all calls to the particular SubVI.

 

I have long wished that something similar were available in the TestStand Sequence Editor. I'd like to propose a "Find All Sequence Calls" context menu selection when right-clicking on a sequence in the Sequence pane. This could leverage the Find tool, but save the user from copying and pasting the name of the sequence. (And save the user from configuring the search options to narrow down the results) It'd be nice to be able to define the scope of the "find" operation to either the selected sequence or all sequences in memory, but I'd settle for a simple search of the open sequence.

 

Cheers,

 

Mr. Jim

 

FindAllSequenceCalls.png

 

 

Hello,

 

If you get memory problems, you had to tune your reports options, result collecting, load / unload modules  .... Smiley Embarassed

 

These tasks are very long, you have to point all memory consumers first ... It pollutes your test sequence only for memory purposes ! Smiley Frustrated

 

When you try to modify the result reccording, you will also have problems for your report generation ... 

 

It should be nice to add a new feature allowing an automatic result list removing, after onTheFly reporting, ontheFly database writing have treted them ...

 

A kind of "OnTheFly and remove unused results"

 

When ontheFly reporting, and The OnTheFly database writing are over, the treated resultList should be put in a garbage structure !

Older test results could be removed if memory is needed ... Smiley Wink

 

I know this could be not simple ... but this could help very much, for big sequences creation. Smiley Happy

 

Thanks a lot.

 

Manu.net (TestStand memory dustman !)

 

The ability to type in a property string to search for:

 

properties finder.png

Currently in TestStand, for a Numeric Limit Test, the "Numeric Format" applies to both the measurement and the test limits.  I would like to be able to have different numeric formats for the test limits and the measurement.  For example, I might want my limits to be %.2f (e.g. 1.23-2.34) and my measurement to be %.3f (e.g. 1.345) so that I can demonstrate a certain measurement accuracy.

 

Pulido Technologies LLC

Recently I had a problem with a testprogram slowing down after 3 hours of execution.

It was traced to opening a .wav file and not closing it. The .wav file was opened and played 3 time but only closed once.

The problem was discovered by using Windows 7 task manager and looking in the process information display. The number of .wav file instances increased with every run.

Vi analyzer did not find this.

 

It would be nice to have a tool that monitors the teststand execution and highlights suspicious behavior, like growing resources.

 

Instrument handles are also an area that can cause memory leaks. If an Ni-Daq is used and not closed, resource usage grows with each run.

When a step cannot be preloaded due to the prototype being out of date (if, for example, a VI was updated after it had been placed in a sequence), an error message pops up telling the user what is wrong. This can then be used to track down where the step is that is causing the issue. Some of the error descriptions get quite lengthy.

 

While this does provide the user with information as to where the error is occuring, the only option is to click "OK", which then closes the message. In long sequences with many subsequence calls and steps (many of which may be similarily named), it is cumbersome to find the specific step that was listed in the error message that is now no longer viewable. At times I find myself having to get to the general area where I thought the error was listed as occuring, and then click RUN again just to get the error message to pop up again, and then continue narrowing it down (repeating this process several times). This is very cumbersome.

 

There is a simple solution to this issue. The easiest method would be to simply include a second button in the error message that brings you directly to the step that is causing the issue (with it selected in the step window). This would solve the main issue of trying to find the step that was listed in the error message as being the problem.

 

To go a step further, there could be a button that simply activates the "reload step prototype" that you have to do once you are at the step that is out of date.

 

To go even a step further, and solve another issue I would like to see remedied, there could be the option of reloading all steps that call that module (since they are now likely all out of date and need the prototype refreshed). Currently, if a VI is called repeated throughout the sequence, then each one must be found and have its prototype reloaded manually. This is very tedious.

 

There may be other preloading errors besides the "prototype out of date" issue (ex: VI not found, etc.) that could use the same functionality of a button that brings you to the offending step, but this is what I am running into at the moment.

 

Regards,

Hello,

It would be nice to insert comment lines not stuck to steps. In fact often comments lines are not related to a step and it's unlikely that moving a step it drags the comment with it. 

  • Have a spec that declares the name of the measurements signal?- Drag-n-Drop from the doc to the Limits>Measurement name field. no need to copy, select, enter field, paste
  • Know what module you want for the step? -Drag-n-Drop from Workspace or Explorer window to Module Path. I browsed there allready and can start slinging modules in
  • Have a list of Parameter Values in a file? -Drag-n-Drop into the value field. No need to retype and we know the data type allready- add the "" around string litterals (And why am I trying to get in between them anyhow pray-tell? TestStand can put the back-it put em there once allreadySmiley Wink 
  • Know what parameter or operation you want in the Expression?- Drag-Drop into the expression field or the expression builder.
  • Duplicating Limits or selecting a comparison? Drag-n-Drop into TestStand

Drag-n-Drop

Drag-n-Drop

Drag-n-Drop

Drag-n-Drop

Drag-n-Drop

Drag-n-Drop.....Sooooooo easy

It'd be neat, in the scenario when a parallel thread is called, if there was some smooth way of gathering the results back into the main thread of the execution for the sake of the report. 

 

I've handled this historically by passing a parameter into the subsequence/thread with the ResultList-index of the parent-step, and then doing some notification based handshaking during cleanup of both threads to quickly copy the Result container out of the sub and back to the parent via API calls. But I bet the R&D types could do this far slicker and reduce the whole thing to a checkbox... 😉

 

21413i267B71BB01EB46E5

 

When I create reports they usually look like:

21417iA1EFA6BABE8471F4

 

I just think it'd be a simple feature to add for users who might be uncomfortable with the API  & ResultList? (Naturally if the sequence doesn't wait at the end it may never be safe to 'pass back' results. But if you're already killing time on the back stretch, why not copy the block up?

 

Cheers,

 

Elaine

Hello,

 

It would be nice to VIEW errors which occurs in the process Model or callbacks using a special dedicated window.

 

Recently, i have send updates to one of my customers, using FTP transfert.

The updates consists of processModel updates, dotNet assemblies ...

During the FTP upload by my final customer, the dotNet assemblies were marked, by windows 7, as "Bloqued" Smiley Frustrated. (For security reasons ...)

These assemblies were called in my process model.

When the final user tryed to launch his application (Operator interface), nothing occurs Smiley Mad! The dotNet assemblies calls fell in error, but without any message. I had to investigate using debugging tools to find out the problem.

 

It should be nice, in case of "anormal errors" in process model calls, or in callbacks (like frontend callbacks) to launch an error window to view this kind of errors.Smiley Wink

 

You may say, you should have test the errors and handle them correctlty ... and you're certainly right !

But i get a look to the default processModels provided with TestStand ... and they are coded as i do !!!!

So even with the 'default process model', if an internal dotNet error occurs (missing sub assemblies, no more ressources ... ) the same kind of anormal behaviour could occured !

 

So having the way to view process Model, or hidden callbacks errors will perhaps be interesting ! Smiley Happy

 

Thanks a lot.

 

Manu.

Hello,

 

It would be nice to be abble to define the report file name "using tags". Smiley Happy

 

For the moment the Report name is created automatically. You can't easily change the order of the filed you want to see in the filename.Smiley Sad

You can only modify the date/time position.

 

I would like to see something like this :

 

Reportname = [%T<YYYY_mm_DD HH_MM_SS>]_[TestSocket]_[UUT].txt

 

ReportOptions.png

 

Thanks.

 

PS : I am using TestStand 2012 ... perhaps this already exists in TS 2013 ?

 

Manu.

Why restrict to load the type pallets always from <user or NI>…Components\TypePalettes folder?

 

It will be very helpful I can configure my path to the load my custom type pallets, this will resolve the issue handling different type Palettes for different customers / projects / sequences.

 

Or even better, if given the option to associate the type pallet to sequence files / sequence model. Just like Edit -> Sequence File Properties -> Model Option -> Require specific model.

Could R&D develop an option to make the standard message pop up automatically go away after a set period of time?  I understand that the message pop up is typically used to receive input from the user/operator, but other times I would just like to notify the operator of pertinent information and then have it go away.  It would be nice if there were a checkbox to enable this feature and then a text box where I could enter the time in seconds I would like the pop up displayed.

 

Regards,

 

Shawn S.

Support use of relative path for image file pathname in message popup step options.

Relative paths make reuse and maintanence easier for me.

Image file pathnames are the only part of my code that breaks when I rename my project directory.

In our Company also hardware developer creates testsequences in teststand, so it would be nice, if there could be a small user interface to configure the values of the parameters for a subsequence.
The solution could be, if they drag and drop a sequence into their main testsequence, a user interface pops up to configure the parameters for this subsequence. So it would be possible to restrict the values with a drop down menu or Radio Buttons or to give some graphical help to choose the right values.

 

Or maybe i could create something similar to the IVI sequences, where i can click on a button and a small editor window is opened.

It will be good if a "Extract" sequence option present: When we select more than one steps in a sequence, show this option. Once you select extract option, new sequence should be created within the .seq file, and automatically insert a step "Sequence Call" which calls the new sequence.

In synchronization  Notification with Wait as an Operation, then there should be Time Out status (Optional Output, Available as a property now) based on which the user can take decision.

I would like a new option in the Step Properties -> Run Options -> Results Recording Option.  The new option would appear for Sequence Call steps only and would allow the step to disable results recording for all steps in the sequence being called.  I would like this to recursive and apply even to subsequences within the sequence being called.Disable Recording of Steps in Sequence Call.jpg

A coworker of my is taking the TestStand training for the first time and I asked him what he thought.  He has been developing software in Visual Studio for some time now (C#, VB.net, etc).  One of his feedback was the extra steps needed to create variable seemed excessive.  His point gave me an idea that I thought would be very nice to have.

 

Currently, in the expression editor, when you start typing there will be a small popup suggesting existing variables to select.  Wouldn't it be nice that it also gave you the option to create the variable right there.

 

Say for example I'll need to place my module return data into a variable but I didn't think ahead and create a local variable.  Now, I am in the expressin editor and I start typing 'local.' and then the name of my none existing variable "newVar".  The little popup that shows the existing varialbes detects that what I've typed doesn't exist and gives me a new button where I can create it and assign a data type.  No going over to the variable editor window...