Why not make it possible for Teststand to generate reports in PDF format?
It would make it a lot easier to send a testreport of a specific board to people not connected to the actual tester.
Today we use XML but this requires the stylesheet to be present on the readers pc.
Graphs are also not showing correct unless you do a manual setup of the settings in Internet Explore.
PDF would make my life a lot simpler
The built-in Wait step currently causes TestStand to simply stop at that step until the specified period has elapsed. For steps longer than a few seconds, it would be nice to have some sort of indicator to show how much time is left to wait (and to show that the computer hasn't locked up on those waits that are more than 15 seconds).
It would be really nice to have a check box option to show some sort of wait indicator, even if it was simply using the progress indicator in the lower right corner of the screen (something that simple could even just always be enabled).
On a related note, could the progress bar be made wider so that there is more resolution as to how much progress has been made? If there was a ten minute wait for something, the bar would be moving very slowly and hard to tell progression was being made.
It would be nice to be able to drag a sequence from the sequences pane over into the steps pane and have it automatically insert a Sequence Call Step with the dragged sequence selected.
In order to logically sort sequences within a sequence file, you have to add either a prefix to your sequence names or add dummy sequences between sequence groups:
What would be great is if I could could add sequence groups which let me organize my sequences logically in a tree view. Unfortunately, I can't shoop my vision of that at the moment.
It would be nice to have some kind of Custom Step which gets triggered when a step is deleted from a sequence. Something very much similar to "OnNewStep" which is triggered when a Step is dropped into the sequence.
We may have an option, say, "OnStepDeletion" to detect the deletion of a step. This will be very helpful in many of the step usages.
The TestStand Flow Control Steps like "IF" and "FOR" use the "OnNewStep" to create an "END" step along with them when they are dropped. But there is no means to automatically remove the created "End" when the "FOR" or "IF" Steps are deleted from the sequence. The proposed "OnStepDeletion" can be handy in such cases.
I hope you all will support this idea as it will make many of the functionalities more efficient.
(PS : Forgive me if anyone has posted this idea already. I couldn't find any such posts)
I have noticed that the TestStand shipping examples are often overlooked when looking for ways to accomplish things with TestStand. This is not the case (as much) in LabVIEW and CVI, and I feel that this is because TestStand does not have an example finder. I would like to see some method of accessing the shipping examples through the sequence editor environment, such as:
Another problem with the current setup is that the only way to know what the example demonstrates is the name of the folder. This makes it easy to overlook examples that would be helpful.
I propose adding a TestStand example finder with these features (in order of importance):
It would be great to have the ability to create an independent TestStand configuration that is valid in a workspace context. That would allow project specific search directories, StationGlobals an several other configuration items you normally don't want to share across projects on the same test station.
Currently, to export properties which are part of an array, such as the limits of a multiple numeric limit test, you have to specify each index of the array separately, like in the first screen shot, or else you get all of the raw XML, which is difficult to interpret and use.
This is both labor intensive and unituitive. . If instead we had the option to export the array with the "?" and have it parse the information out like in picture 1, it would be much simpler to use.
It would be helpful to be able to provide a regular expression (like Labview Match Pattern) as a string value test limit. We often look for a pattern of data within a string rather than a constant.
Maybe also a regular expression function within the built in functions within TestStand expressions would be a help also. This could provide more flexibility if a user needs it. For example adding option to gain match position, and match length as well as give the option to search in reverse and ignore case.
Do you ever have too many custom data types, and it looks something like this
This just really sucks when you have 100's of data types to go through. My list is currently 150 long. That's a lot of clicking on that little arrow at the bottom.
How about something like this:
Go through and reorganize your types
<< insert some whiz-bang graphical editor here that allows dragging/dropping of types into groups -- none of this "move up in list" "move down in list" stuff that we are doing now to move step types in/out of groups >>
Now when you go to insert a type, you see a tree structure and all your types are organized
This would be so much easier to find the type I want.
How many times have you found yourself typing double backslashes "C:\\Windows\\System32\\cmd.exe" or even worse, going through a copied path to change every backslash to a double backslash (and inevitably missing one), just so you can pass a file or directory as a constant to a code module or another sequence?
I'd like to see a symbol for 'explicit string' in the TestStand expression language, much like C# does with the @ symbol.
So if we typed @"C:\windows\temp" we would actually get the string "C:\Windows\temp" instead of "C:\Windows<tab>emp".
To really go the extra mile on this:
1) TestStand functions Time() and Date() only output local format; they should support both local and UTC format. (Like LabVIEW's Format Date/Time String)
2) TestStand configuration options should have a setting(s) for:
report time format local / UTC
datalogging time format local / UTC
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.
It would be nice to integrate VeriStand into TestStand with a VeriStand Adapter.
This would make developing with TestStand and VeriStand much easier. The adapter would provide a lot of the VeriStand .Net api natively to testand:
- Deploy a system
- Set/Get Channel(s)
- Stimulus Profiles
The adapter would be especially nice for integrating the new Stimulus Profiles in VeriStand 2011. It would allow for you to create the Stimulus Profile sequence and the Real-Time sequence. The Real-Time sequences would only be able to use a subset of TestStand steps, and would have to be different than a normal TestStand sequence because they are executed by the VeriStand engine, but the Stimulus Profile sequence could be a normal TestStand sequence.
The integration of the Stimulus Profiles would leverage a lot of features TestStand already has like source control, requirements, reporting, etc. Also, it would just give the user a much more intuitive experience when using the two together. Their test development would be centralized in TestStand instead of having to switch between the two different editors. It would also give better access to the parameters being passed into the Real-Time sequences at the TestStand level.
There are probably more benefits that could be realized by integrating TestStand and VeriStand, and this is a feature I would love to see as a user of both TestStand and VeriStand.
Almost all of our analog measurements are specified in %: example
a Power Supply DMM measurement limit is 24.00Vdc +/- 5%
We typically have 100+ measurements like this in a project
Why not include it in the default step types as an optional selection?
I sure would use it, so would my team.
I agree that it should not alter existing programs using the default step, but I believe that this feature should have been in Teststand when it was first released.
I have run across this in both analog measurements, and the results from an ADC
Think a limit of 0x234 +3%, -7%
You can copy the value of a selected variable to another element.
But you cannot paste the value into the selected element in an easy manner.
What you have to do is click into the selected variable’s value field and then Paste, but this doesn’t produce the correct result (for strings anyway)......
You end up with is double quotes!!!
Also if you had ‘Copy Value’ on multiple selected elements and pasted them then you get
So it cannot handle multiple selections.
It would have been better if you could have selected the place where you wanted to paste the value(s) and a new menu item became available ie ‘Paste Value’.
This way should also be able to handle multiple selections.
The problem with double quotes shouldn’t occur and should be corrected with the current pasting of values.
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.
Handling arrays in TestStand is pretty limiting and more often that not you have to pop into a code module to perform any sort of array handling.
The following is the default functions that can be used in expressions:
GetArrayBounds(array, lower, upper) Retrieves the upper and lower bounds of an array.
GetNumElements(array) Returns the number of elements in an array.
InsertElements(array, index, numElements) Inserts new elements into a one-dimensional array.
RemoveElements(array, index, numElements) Removes elements from a one-dimensional array.
SetArrayBounds(array, lower, upper) Changes the bounds of an array.
SetNumElements(array, numElements) Sets the number of elements in a one-dimensional array.
I would like to see this expanded to avoided have to resort to using code module.
The following is some suggestion:
Array Subset function
Array Max & Min
Replace Array Subset function
Search 1D Array
Sort 1D Array
Currently, if you create a step type and name it OnNewStep, it will execute when an instance of the step is created. This is pretty confusing to new users - why don't we just have an OnNewStep substep type (like prestep, edit, etc)? Custom steps would then just be meant to be called manually using the Step.ExecuteSubstep() Method as documented in the help.
We could keep the "onNewStep" custom step functionality to maintain backwards compatibility with older step types.
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.