 |
|
||||||||||||
When creating custom step types, it is highly recommended to use Post-Step for calling execution module instead of Default Module.
Thus, when instanciating a custom step type, parameters passing is not saved within the sequence but only in the step type definition.
This allows to change parameters passing without having to update all the step types instances.
In some big test benches, it is intersesting to have low-level step types and high step types based on low level step types.
High level step types execution modules are sequences using low level step types.
Since sequence adapter is not available for Post-Step, we are obliged to call the sequence through Default Module.
Thus it can generate problems when adding parameters in sequence call.
I suggess to allow Sequence Call in SubStep creation :
Jean-Louis Schricke, MESULOG
TestStand Architect
When using the TestStand API, I always find myself switching back and forth between TestStand and the TestStand reference help. While the intellisense function help is usually enough, many times I like seeing the more detailed information in the help. I would really like to have the option of displaying context specific help in a TestStand pane, similar to the context help window in LabVIEW.
This pane could dynamically update to display function information when using expressions, or show general information about the active pane or dialog (for newer users). Much of the linking for the second case is already done, since the F1 key will pull up relevant help for the active pane currently.
For some reason I was certain this was already in the idea exchange, but I couldn't find it -- so I'll post it.
Select Case structures are frustratingly difficult to use if you want one case to support multiple values.
In text languages you can often do something like
Switch (Foo) {
Case 1:
execute this code;
Case 2:
execute this code;
Case 3:
Case 4:
Case 5:
execute this code;
Case 6:
execute this code;
Default:
execute this code;
}
Notice that the case for 3,4,5 is all the same, and I just need to put it in place once.
TestStand can't do this. You need to do something like this:
how to do select case on multiple values
which is horribly difficult to write, maintain, and understand what is happening. It would be MUCH easier if select case on multiple values worked like this:
where it looks just like other text based languages, although it takes up quite a bit of realestate on the screen.
or maybe something like this:
where I can just type in a comma separated list of allowed values. The similarity with text based languages disappears here, but it is much smaller on screen (but notice how it shows nicely in the description field) and lines up better with LabVIEW notation.
Note: LabVIEW already supports doing this, and also supports ranges of values (eg 3, 5..10, 12 for numerics) which would also be nice, and also supports case sensitive and insensitive comparison for cases.
When monitoring values within a loop in TestStand, it is often desired to only record step failure results. It would be useful to have a "Result Recording Option" of "Enabled On Step Failure":
This is possible through various means (SequenceFilePostResultListEntry callbacks and other custom code). However, I believe this would simplify TestStand sequence development significantly.
I'm taking a bunch of steps and trying to put a "If" flow control step around them.
Kinda like this:
But what I end up with is just a If/End statement in the middle of the steps that I selected (well, after the first step in the selection)
What I would have liked to see is this:
Whare the If/End wraps the steps that I selected.
I don't quite know how best to handle the situation where the steps you have selected are not sequential (there's an unselected step in the middle), but that could probably just behave how it is now.
Hello,
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.
Cheers!
Shawn S.
Find yourself placing a Sequence Call step and trying to determine the appropriate value to enter for a numeric parameter called "Direction"? Tired of creating sequences with numeric parameters named like the following: "Direction_0_Up_1_Down_2_Left_3_Right"?
The solution is to support the creation of variables with enumerated type within TestStand. Enums could be created as custom variables and then used as wherever a self-documenting variable is required.
Enum type creation:
As seen from a Sequence Call step to a subsequence that uses an Enum as a parameter:
I would like to enhance the TestStand Message Box step to add a 'Preview' button. When selected, it would show how the currently configured message box will look when run.
I find that I am often switching around the text, fonts, and other aspects and would like to get that straightened out before run time. I know you can run the step individually by selecting 'Run Selected Step' but that is tedious, plus you have to take into account preconditions and other functionality. Normally, I have to remove the precondition (if there is one) as often the step cannot be run by itself.
So here is my example with the button added. Not exactly sure what tab it would belong on.
Thanks,
Paul
Do you ever write an expression in TestStand with a bunch of parenthesis () and get lost halfway through trying to figure out which pairs are open and which are closed. Well, I do. Every Day. And I spend accumulated hours a week just trying to keep track of which ) goes with which (. If I'm lucky I can look for a little red item in the expression, or click on the check expression checkbox, but when I have a 'only runtime evaluatable' expression I'm out of luck (which is rather often) ). Some languages/editors have a parenthesis matching, where the ) your cursor is on causes the matching ( to get bold or flash. Others start coloring each pair a different color, so it's easy to see them all. Why can't TestStand do something like this????
Do you have a feature idea for how to improve NI TestStand? Submit and vote on ideas now!- 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!
- 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. - Watch as the community gives your idea kudos and adds their input.
- As NI R&D considers the idea, they will change the idea status.
- 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.
|
||
|
||
My Profile | Privacy |
Legal |
Contact NI
© 2011 National Instruments Corporation. All rights reserved. |  E-Mail this Page
|
||
|
||