NI TestStand Idea Exchange

Now when property loader loads the data from excel files immediately, not waiting for the cell to refresh.

It can lead the obsolete value to be loaded.

Hi,

Exactly like in the subject.

Now property loader can cope with the first sheet only. It would be good if it can cope with multiple sheets.

Kamil

To change the step name the command Step.Name is commonly used.

However, if the step contains multiple measurements, changing their names dynamically is impossible.

It would be good if this opportunity would exists.

Hi,

Now the Evaluate() command cannot resolve names when the name to evaluate is within the square brackets []. In other words if the name to resolve is a part of the index.

It would be demanded the Evaluate() doesn't have this limitation.  

Hi,

I'd like to return to the idea posted by me on the forum here: http://forums.ni.com/t5/NI-TestStand/Concession/m-p/1458500/highlight/true#M31968

It would be very good if teststand would offer the native testing against multiple limits. Let say the test will pass if the measurement is less than 5 and it pass under concesion when is less than 7, otherwise its fail.

So, summarising TS shall have the ability to delinie not only one set of limits per measurement along with the different kinds of passes.

Right now in "On Run-Time Error" combo box in Execution tab in Station option we have the option as below:

I think another one shall be added which would be Retry. At some ocassions, it'd be good if TestStand, in case of an error, could retry to execute the step for second - or even third or forth - time, by default.

Hi,

When you cancel the breakpoint set in the sequence file tab whilst this sequence file is running you can still see it in the execution view.

It's bit confusing, and needs correcting, I think.

Hi,

As in subject,

It would be good to have the Fail execution option. When the step will fail the execution pointer shal be moved to clean-up part of the sequence (and parent sequences) and the whole execution will be marked as failed

Sometimes in the tests we would like to check are they any common elements for two arrays.

TS2013 have a nice function called Contains() using which devs can easly check if the searched element is in the array or not.

And what about the function which returns an array of common elements of two even more than two arrays?

Instaed of looping one array and issuing Contains() command it would be good to have a kind of logical AND using which we can have a list of common elements?

Would the operator overloading be the right things to do?

Hi,

I propose to that the steps to have new feature called AllowableCallers.

Using this feature developers could restrict the callers (subsequences) from where the particular steps could be called.

Having this feature developers could prevent the mistakes of unintentional step copying during creating new subsequences using the copy-paste method.

The default value for this settings would be AllowAllCallers, but developer would be able to define the condition as they wish (function window f(x))

Hi,

Exactly as in the subject.

There is a need to add the explicit, text-based, if-then-elseif-else syntax to the list of command allowable in the statements and function definitions.

I know I can use C++ style of the if-then-else-elseif syntax, but in more nested expresions the readibility of it gets worse and worse very quickly.

Having this functionality would simplyfy the readibility of the statements.

Currently the message popup step is quite primitive.

It would be good to enhance the functionality of this step.

Proposal: pressing the any button definied should be able to trigger the set of TS commands (as in Statement step) definied for any button.

In this case it would be helpful in that way that developers won't be needed to program separate modules to process the flow control flags and user interface popup.

Hello

Execution of a single step is a process executing a lot of steps depending on looping and synchronization. Needing the option to call a PreExecuting and PostExecuting step before taking Looping, PreConditions and Synchronization options in consideration and after all other steps are executed. This is intended to custom step types for use with external customers.

Thanks Vagn

The "start modal Dialog" should get an additional input for a VI reference. With this input the start and End modal Dialog VIs could be stored in an FGV, what would clean up the blockdiagram.