If you have lot of code between an if, else, end statement steps (and other flow control structures for, foreach, while, and etc.), it would be nice to roll all that up so you can see more of the flow of the sequence. This will also help to know what steps are in those structures in large sequences. TestStand already has some code folding in the sequence, so this is an expansion of this. Many text and code editors have this feature and it would be a great feature for TestStand.
Let's say I'm building a fairly long compound expression that has some repeated parameters - I would like a way to specify (without creating additional locals) a variable/macro for use just within that expression.
I'd like to see a "No Comparison" comparison type added to the String Value Test.
Currently there are only two options for comparison type on the String Value Test: "CaseSensitive" and "IgnoreCase". I have often wished there was a "No Comparison" option similar to what is available for the Numeric Limit Test. Sometimes you want to pass a string to the test report in the result field that neither passes nor fails the test.
I thought that it will be good if the developers could collapse blocks of code which are in between of the Flow Control or/and Synchronisation step types.
I think about the mechanism we know already from TestStand which hides block of code: i.e. Setup, Main, Cleanup section in the sequence, or it can hide variables. It is a little "+" and little"-" to expand the content of the type of variables.
The types of steps I think of were mainly types from Flow Control and some types from Synchronisation. It would be good if for example we could collapse If-Else-ElseIf-End, Select-End, Case-End, While-End, DoWhile-End, etc statements
I think this functionality could improve the readability of the sequence, and helps the developers to have a better view on the whole sequence.
I was pretty surprised that this isn't already possible or that there wasn't an idea in the ideas exchange for it. The idea is to allow custom step types to embed their 'edit' dialogue into the configuration tab for the step settings. At the moment you have to click a generic 'edit <step type>' button to launch a dialogue.
This would make custom step types much more user friendly and save unnecessary clicks/steps required to custom and bring the experience of configuring steps more in line with the built-in step types.
I appreciate that it might require a little more effort on the developers part (e.g. posting new values on value change instead of on 'ok'/'cancel') but it could also help to avoid some issues like 'hanging' TestStand when the dialogue is closed and the panel close isn't disabled/handled.
We in our company are done now several test systems where the best process model is Batch Model. Customers however does not want other reports than UUT report from each test socket. Simple skipping of batch report generation is not possible at the moment particularly now when plug-in structure has arrive for joy of us all. For me this wanted feature is late now because I manage to find out solution, with a great support of local NI team. Finally this feature of easy batch report disabling would serve future generations and today newbies. They will save hundres of hours when they don't have to use try&fail -method to skip those few meaningful steps but just make one selection in report options.
I have a sequence file that contains hundreds of sequences. It would be nice to be able to logically group and organize these sequences, such as in a tree control with virtual directories (hierarchy), instead of them being in a single long list.
It is very common to use a typedef as input or output terminal for any VI. If such VI is used in TestStand either as custom step or in a sequence, then teststand requires a relink of step/sequence whenever the typedef values are modified.
Teststand need to resolve this differences automatically, rather than expecting user to relink sequences.
What the menu might look like with a Insert VISA step:
A VISA>>Write step would replace a LabVIEW Action Step such as the one I used below for direct Instrument control from TestStand. Queries would look similar and be able to set limits on the returned value.
LabVIEW VI for the power supply command to the VISA instrument setup from M&A Explorer.
This is “PS1” in Measurement and Automation Explorer uses Alias Name.
Example of Query instrument to an Agilent 34970A using Alias Name “DM1” setup in MAX.
However, a little more complicated than a single string command from the menu. Might take several Write steps first.
Instrument control without additional software or programming languages.
Ability to immediately add new instruments and modify existing sequences without an instrument driver. Demonstrates the quickest possible way to gain instrument control with the least effort (for simple systems).
Simple test sequences can be written right away making it easier for technicians or engineers to write tests.
VISA sequence steps can be dragged to the palette and easily re-used.
It would be nice to have the message popup be more generic so that it can be used in more situations. For example to notify the user that there is a wait in progress. It is currently not possible to remove the button from the Message popup.