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.
Could we add an option to the context menu within TestStand that populates when one right clicks the tab for a *.seq file in the Sequence Editor? I would like a feature that allows users to be able to close every window except for the selected window. I've included a screen shot below for clarity.
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.
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.
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.
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...
TestStand can support LabVIEW Clusters, but with Object-Oriented LabVIEW development becoming more and more common, and OOP particularly suited to driver development it seems crazy that one NI product does not properly support the other!
One of the biggest benefits I see is that the inheritance property of classes could allow us to create flexible test systems that can have a particular driver changed without having to change the sequence itself.
In TestStand you can create a comment in a variable, but that comment will be deleted even if the data type of the variable is changed. This does not make too much sense because it happens that the customer needs to change the data type, and then he has to re-write the comment completely. This feedback comes straight from multiple customers and it makes sense that it should be so.
Current shortcuts for TestStand include Ctrl-D to close executions and Ctrl-F4 to close a sequence file. However, both of those windows show up as tabs in the current GUI layout.
Every modern internet browser allows the user to close a tab with Ctrl-W. This would also be a neat feature when only trying to close one report at a time when viewing the results from multiple UUTs, instead of closing all reports by closing all executions with Ctrl-D.
Currently, the Installation Destination options are as follows:
There is no way to install files to the root directory, or its subdirectories, with the exception of those already present in the Installation Destination. For instance, make it possible to install a file to the following directory: C:\ProgramData\IVI Foundation\IVI
LabVIEW recognizes any cluster of <Bool, I32, String> as an error cluster. TestStand should recognize this as well and default any such cluster output to Step.Result.Error.
With the addition of the Silver controls in LabVIEW 2012 "error out" was changed to follow the style guide recommended naming convention of leading caps and is now labled "Error Out" which is not intercepted and assigned to step.result.error.
We have several sequences which are too long to execute (test stand crashes during the initial load) using the preload option. These are often sequences with 50-100 subsequences which define contiguous tests to be performed.
If Test Stand had a 64 bit version additional memory would be a solution to this problem.