NI TestStand Idea Exchange

Top Authors

User

Kudos

Post an idea

I just had an issue (SRQ#1672094 - for NI employees who want to look it up) where I tried to open a termination monitor in a sub VI which was called in a VI that already had an termination monitor running. The whole thing seemed to run properly until the second termination monitor was about to be closed. It threw an error telling me that I was playing around with an invalid reference. I was a bit confused...

The issue was solved by NI hotline in a short time - as usual: It's not possible to have several termination monitors running in this constellation and I should forward the open monitor into the subVI and use it there.

I wonder whether it is possible that an error message is thrown when one tries to open a redundant termination monitor. Even if LabView can't know, TestStand should be able to and respond accordingly if the function is called. It would make debugging easier.

View All (1)

Hi,

In the bottom right corner of the Sequence editor window (or in other place if you find more suitable) please display information about type of the adapter server.

For example for LV Adapter it would be information about whether Adapter is set to wok with LV Development System, LV Runtime Engine or other executables. For HTBasis Server it would be HTB Runtime Server or HTB Development Server.

During the development I have to often switch between LV Dev environment and RTE. To do that you have to click three times to go trough modal window to get this information. If you do this often it's getting painful.

View All (4)

It'd would be good if in the Step settings for LV modules we can have a button which can trigger the test saying is that module going to work when we change Development Environment (DE) to Run Time Engine (RTE).

Now, in case like this, we have only a dry information saying TS cannot load the module because probably VI is broken. Problem is, when we switch over to DE VI is NOT broken.

Of course the reason behind is that RTE has not enough information to call one of dependencies, or there is ambiguity in calling a sub-module - for example a dependent sub-module is used called by step earlier.

So, summarising, the test like that would be quite needed (saving time of development), and information returns shall be more detailed indicating the sub-module cannot be loaded by RTE and why.

View All (6)

View All (4)

Hello Team,

Currently we can’t move or add additional results above the ‘Parameters’ if the subsequence or module has parameter list. It would be useful if we have an option to move the selected result to log in the Additional Results of step settings to desired position/row.

Similary with in the Parameters list, it would be useful if we have an option to rearrage the list.

Thanks

View All (7)

View All (3)

Hello,

I have a sequence which must loop a very long time, with cyclic access to hardware components.

In order to limit the amount of memory used by my application i decide to use the famous "Disable result recording" flag.

Beside this problem, my sequence don't have to collapse in case of runtime error (Due to hardware manipulations during execution),

and operators don't have to aknowledge the "error dialog box" ... every time an error occurs !

To handle my runtime errors, i deceide to :

The main sequence is a loop calling the different fonctionnalities by sequence calls
I configure the sequence calls with "ignore RTE", so my mainSequence never stops on runtime error
I Configure the "runtime error handling" with the Run cleanup ... so no popup disturbs the operator

This is OK, but i also want to treat my errors (Tracing at least) ... and then i get the folowing problem ...

The errors are no more accessible using Runstate.previousStep.result.error... ... Runstate.sequence.main.... .... , because i have used the "Disable result recording" flag.
Storing a runtime error in locals is not possible in post expressions ... because post expressions are not executing after a runtime error

Perhaps the only way to handle my problem would be to use the SequenceFilePostStepRuntimeError callback ...

But doing so, would need to use stationGlobals or FilesGlobals to get back the error in my main sequence. (A complicate architecture only to get an error !)

So, it would be nice, to be abble to ...

Let the result recording working
This make the runstate.previousstep.result.error... works fine
And sometimes, be abble to flush the result tree (Using a new API function. Something like <Execution>.FlushResults( ....) )

PS : My sequence don't use any report, database writing ... thats why disabling results recording is possible !

I don't know if i am clear ? (And with my bad english ???)

Manu.

View All (4)

View All (6)

When you select the "Unlod modules" in the module, you have no result message: user can't know if modules were really unloaded or not.

You can see the situation with a sequence that load a .DLL extension is opened and has run: if you want to delete (or update) the DLL file windows prevent you to do. Make Unload, Windows sometimes still prevent you.

I've not found the real conditions to reproduce the situation but I think you should improve the user information with that Unload Modules function to shos, as ex, which modules have been really unloaded and which ones not.

View All (2)

Hi,

Sometimes I can find difficult to access arrays using indexes. Although straightforward it can be difficult to maintain in certain situations, like calibration data for a lot of frequencies. Lets imagine you have a table of sixty calibration factors per frequency and forty frequencies, generated by third party software to the excel file.

It would improve accessibility if we could name columns and rows and use their names instead/along with the indexes.

We can access the array data like AnArray[4][6] now. In this idea we could access the data like that: AnArray["63dB”]["125MHz"].

When we would like to import the data using property loader it would be easier to access the data with defined names of colums and rows rather than indexes. (data binding)

NI TestStand Idea Exchange

Allow Custom LabWindows/CVI workspace or project from TestStand

Termination Monitor should throw error in LV when created too often

Feature request: Display information about type of the adapter server

Enable implicit cast numbers to string in OutputMessage function.

Loading LV modules by Run Time Engine (RTE). Test is the LV module going to work with RTE

Displaying the step unique ID when hover over the step name

Able to select multiple rows while using 'Move Selected Results Up/Down' in the Additional Results settings

Move Selected Results above the Parameters in the Additional Results

Allow the *.llb Source Distribution builds to work as the application instance

PropertyObjectType.TypeName - extend the list of returned types.

Be abble to flush result recording, using TestStand API ....

Allow multiple TS versions open at the same time

Specify substep module paths by expression

More information when using "Unload Modules function"

Implement execution timeout option in Adapter Module Configuration/Setting

Introduce data binding/handling mechanism for arrays

Debugging the sequences. Watch window value access indicator.

Programatically accessed feature: Do not compare all results, just log.

NI 845x script API

Tools shortcuts