NI TestStand Idea Exchange

Using the stock reportgen_xml.seq file, the text value of the XML node shouldn't contain the characters < or >:

http://www.w3.org/TR/xml/#syntax

When using LabVIEW VI's to parse this, you (rightly) get errors, so it's incredibly difficult to just search and replace the offending characters with their XML escapes.

Example node contents from the XML report:

It would be nice if there was a station option that would set the default load option for all created sequence files. Currently I must either programmatically modify the RunState.SequenceFile.ModuleLoadOption property with a statement in each of my .seq files or navigate to Edit » Sequenfe File Properties and change the feature over and over again.

An example of what I'm talking about is shown here:

Programmatically Update Default Sequence File Load Option
https://decibel.ni.com/content/docs/DOC-20095

Thanks!

View All (5)

In every TS step we have the looping feature. I find it very elegant feature which allows us to save implementing full loops for singular steps.

I wonder if some statistical information to the looping feature can be added to the looping feature.

We could image that there is a step with the i.e. LV module which is responsible for acquiring one sample of data. Let say the sampled signal is noisy. It would be fantastic if we can use this singular step which acquire singular sample and the looping feature of the TS step to get multiple samples and to have a statistic the samples taken. The statistic could be:

--averaging

--mediana

--standard deviation

--etc...

View All (5)

In a recent Test Stand training session at my work, we learned about Engine callbacks and specifically about the Load and Unload ability to run code when simply loading or unloading a TS sequence file. In speaking with our FE, there is no was to disable the Engine callbacks and he asked that I post this request.

Without the ability to disable this feature, there can be inadvertent to malicious consequences. The loading or unload of a sequence file needs to be passive during development so the sequence file can be reviewed and verified to be harmless before putting the sequence file out for production use.

In the inadvertent instance, a developer could produce something that they are not quite sure will work and it could produce a side-effect. It would be good to be able to open this sequence file and review all the steps before the Engine Load callback has any chance of running.

In the malicious instance, the Engine Load could be used to perform unwanted events - I.E.. Performing a system call to format the C: drive, making a remote connection to an external computer, etc. during the code load and before anyone has a chance to review the sequence file and verify that it is harmless.

The Engine callbacks are a great feature but with the inability to disable them creates a great security risk. There needs to be an option in the TS Sequence Editor to disable all or selected Engine callbacks and then a sequence file can be opened safely and reviewed before execution.

When investigating a specific UserGroup (in the user group list) it is very easy to check the array of Members to find a specific user's name... However, given a specific user, it is a bit of a process to do a reverse lookup and find what group the user is a member of.

While I know that I can always check privileges on specific operations for a user to make an educated guess on what group I belong to, it would be more elegant if I could just access a method or property such as:

CurrentUser.Memberof()

and have it return the string for the UserGroup name. {Operator, Technician, Developer, Administrator etc}

View All (1)

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)

View All (7)

View All (4)

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)

View All (3)

What do you need our team of experts to assist you with?

Request a quote Find the right product Place an order Get support on a product

How can we help?

Please enter your information below and we'll be intouch soon.

This field is required

Preferred communication method

Email Phone call

What do you need our team of experts to assist you with?

Request a quote Find the right product Place an order Get support on a product

NI TestStand Idea Exchange

provide cancel button on loading express VIs dialog

XML generated for report text of reporting results of For loop contravenes W3 XML spec

Add Station Sequence File Load Option

Feature request: statistical information when looping the step

Disable Engine Callbacks during Development

Teststand configurations based on windows login

Execution Globals

Add API property for User to look up Membership?

Execution Object Property

Termination Monitor should throw error in LV when created too often

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

Allow multiple TS versions open at the same time

Introduce data binding/handling mechanism for arrays

StationFileLoad StationFileUnload Callback