NI TestStand Idea Exchange

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

So we have the setup, main and cleanup step groups in the sequence view which is fine, and they're collapsable which means if you're working in Main you don't get a screenfull of Setup above you.

We also have block sections that you can associate with step types to provide indentations making navigation easier.

What I'd like to see is the ability to create a collapsible section (so a sub sequence call is NOT what I'm talking about).

For times when a sub sequence call is not necessary, we should be able to insert a block section that is collapsable purely for visual appeal.

It makes long sequences easier to navigate. This would be a visual implementation modification on how we show block sections (so collapse versus indent).

 

Thoughts?

Thanks
Sacha

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:

19679i37712516107E8A41

 

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

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.

 

sequenceicons.png

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 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 😉

I upgraded from TestStand 2019 SP1 to TestStand 2024 Q4 and the UI looks really bad, with black and white theme with icons not recognizable and hard to look at for longer periods.

1) Please add function to have themes for TestStand like Visual Studio, some examples:
Dark theme
Classic theme (Older version of TestStand)

2) Make it easier for users to change the UI and function to zoom in/out in TestStand (like it´s possible in newer versions of LabView).

Iam thinking about expressions field should have zoom in/out function.

 

3) Change it back how it was for showing Sequences and Variables (TestStand).
It´s not better to show only one or the other. I would like both to be shown at the same time as it was in previous TestStand versions.

Hi there,

 

When using the Find/Replace dialog in TestStand, it would be nice to have a checkbox under "Elements to Search" that allows the user to choose whether or not to include sequence file attributes in the the results. I guess I could put together a regex to accomplish what I need to, but a checkbox would be nice.

 

FindOption.png

 

Why am I asking for this?

I'm used to quickly working my way through find results by using the CTRL+G / CTRL+Shift+G shortcuts. When I hit one of these attributes there's about a 4 second delay before the sequence file attributes dialog opens. This is super annoying in the workflow of the find results, and the vast majority of the time I'm not interested in searching the ignored Sequence Analyzer messages.

 

Thanks,

 

Mr. Jim

 

IgnoredMessages.png

 

 

 

- Disabling the editing of text in the response text box of a message popup step.

- Ability to include various fonts in the message popup rather than one overall font for everything...

I'm working extensively with LabVIEW VIs and Test Stand, and one of the most helpful features existing is the ability to configure a TestStand type to pass its data to and from a LabVIEW Cluster.

 

I think a great way to expand upon this would be to allow the developer to override specific variables within the LabVIEW cluster.

 

For instance, say I have defined a TestStand type with 5 total variables, all of which may pass to a LabVIEW cluster. If my LabVIEW cluster has at least the same number and type of variables, then this cluster passing has no issue.

 

However, if my LabVIEW cluster has 6 variables, then the TestStand type can only account for its defined five variables, and I am effectively locked out from the sixth variable. I cannot edit the sixth variable, nor can I assign it a default value (see Ex1_broken.PNG)

 

This wouldn't cause an issue if I could override specific variables within the cluster passing. That is to say, if I were given access to that sixth variable from the example, then I could assign it to a local variable. The other five variables would still be satisfied by the TestStand type, and no errors should be generated by the step. (see Ex1_fixed.PNG for what I envision this to look like)

Download All

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.

Hi,

 

I'm using TS2016. I'd like to suggest adding multiline watch view. I put some serial communication data in a variable, and watch it, but I can only see the top line. Of course, I can mouse over it, and see the entire thing, but it would be nice if I could see it automatically.

When running teststand deployment licence there is no Teststand GUI available to set or configure Results Processing.

I think it should be easy to export the active configuration to file. And then have a property loader type step to load the settings back into the sequence at runtime on the deployed machine. Note in my case I want to run different sequences with different reporting requirements on the same deployment PC.


I have found https://decibel.ni.com/content/docs/DOC-32076
and after more stuffing around than was justified I have got it working with TestStand 2014.

 

Export.png

 

 

Also it should be much easier to specify a relative UDL file. 

UDL.png

 

 

I resolved this by adding an expression after ReadEx that was:

Parameters.ModelPlugin.PluginSpecific.Options.ConnectionString="\"FILE NAME="+Left(RunState.SequenceFile.Path, Find(RunState.SequenceFile.Path, "\\", 0, True, True)) +"\\60467Database.udl\""

 

This means I can select an absolute path to the UDL file in the development directory on my laptop and then use a relative to sequence path in the deployment. 

 

I feel there should be an more obvious way or am I missing something?

Currently you must set the path to the folder that teststand will load its inital configuration through the options.  This means that it is not possible to change this via the cmd line wehn launching sequences.  Tehre are several work around for this (none of which are very good).

 

The 'best' solution to this issue would be to add "/configPath "c:/projects/tests1/" " as an option on the cmd line and allow teststand to use this instead of the path hardcoded int he registry.

Like in MS Word there is Ctrl +G to go on particular line, Similar should be in NI TestStand to jump to particular step.

In the status below the editor we can see the Current Step Number. It shall be better if we can enter there a number and directly cursor goes to that particular Step.

 

Regards,

Priyank Soni

I'm frequently missing that steps are skipped when running sequences. It would be handy to see a steps' background color change when the run mode has changed to skipped or forced pass/fail.

Create option to print selected components (Script, variables, Step Settings etc) this would be useful on several levels, it would make tracing thru long scripts easier, would provide a quick means of providing feedback on errors and other situations which lend themselves to having more than a single screen of information available concurrently.

LabVIEW executables update to the Windows settings when run.  So, if the scrollbar size is increased (as is helpful with touch panels), the scrollbars adjust.  However, TestStand called LabVIEW modules running under the Run-Time Engine do not update in size.  This makes it hard to customize the value to the user's needs.

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.

 

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.