NI TestStand Idea Exchange

Post an idea

When user opens the Offline Processing Utility and at the same time starts to type on the keyboard the user can accidently rename the profile.

(Attached a screen-recording to visualize)

It would be great if there was no selected row or column when starting/opening ORPU. The renaming of the profile disturbs the production since the database logging will not work as expected.

When we start ORPU we already have the '/tray' enabled but somehow its still possible to accidently rename the Profile.

View All (5)

TestStand File Diff and Merge Utility is not very useful for code reviews on its own. It seems adequate for notifying the user that a sequence was added, however from the tool itself the user cannot actually review the newly added or removed sequence's contents. Why is there no + on the item tree to go deeper.

Alternatively:

If I have to right-click a sequence and select "Go to location" then why bother with the separate tool to begin with? Why isn't the diff utility integrated into TestStand's sequence editor itself? Seems like a side-by-side comparison within Sequence Editor would allow a reviewer to poke and prod around all the hidden settings that are often missed using the existing utility.

Looking at any step result, there's a TS.StartTime property, but it's referenced against the "the number of seconds since the application initialized the TestStand Engine"

What this means is that each step result is referenced against a somewhat arbitrary and changing epoch that isn't recognizable outside any one instance of the TestStand application, let alone by external applications.

I'd like to propose adding TS.StartTimeUnix, which contains the absolute time the step started.

I've added this in our model customization plugins, but to convert the epoch to UNIX I have to perform this calculation:

Seconds(False)-Seconds(True) + Parameters.Result->TS.StartTime

Why I'm asking for this:

In our step result database table, we've added a column for STEP_START_DATE_TIME which is absolute UTC time. To populate this I have to go through the gymnastics above. I revisited this code today and thought, "What silliness. This should be something natively supported." (Other than that I have no strong opinion on the matter)

View All (7)

The "Report Options" dialog box provides a lot of flexibilty in the way reports are generated for sequences executing under the Batch model. A new report can be generated for each UUT, for each socket, etc. One option that appears to be lacking, is to flat out not generate a Batch Report. Doing a brief search, I found at two other folks who were trying to do the same thing:

http://forums.ni.com/t5/NI-TestStand/Disable-Batch-Report-TestStand-2014/td-p/3091476

http://forums.ni.com/t5/NI-TestStand/How-do-I-disable-batch-report-in-the-batch-model/td-p/238387

Suggest adding another check box to the Report File Pathname on the Report Options dialog box to disable batch reports.

Currently, to export properties which are part of an array, such as the limits of a multiple numeric limit test, you have to specify each index of the array separately, like in the first screen shot, or else you get all of the raw XML, which is difficult to interpret and use.

This is both labor intensive and unituitive. . If instead we had the option to export the array with the "?" and have it parse the information out like in picture 1, it would be much simpler to use.

Regards,

Kyle Mozdzyn

Applications Engineering

National Instruments

A nice feature of reporting is the ability to form the report file pathname using an expression. However, since the path is resolved before the client Sequence file is executed, you cannot use properties populated in the client sequence file as part of the report pathname. Currently the only way to accomplish this without modifying the model or reportOptions callback is by including the <UUTStatus> macro in the path expression, which enables a portion of the process model which copies the report to a new path based on the result of the UUT:

I propose that we add an option to force the report path to be re-evaluated after the client sequence to allow users to include properties evaluated in the client sequence file in the report file path without needing to include the <UUTStatus> macro. (basically exposing the ReportOptions.NewFileNameForEachUUTStatus property in the dialog)

Problem:

I create a model plugin and add some model callbacks to it. Then I want to access those model callbacks from my client file. I have to now add them to the process model so they show up in the list when I go to add callbacks. I get that I can add it as a blue sequence and it will work However, that is confusing to other developers if they don't know the plugin has the callback in it. It is painful to change the process model every time I create a new plugin because the process model could be used on hundreds of machines whereas my plugin may only be needed for 1 or 2 machines.

Solution:

Option 1: Show all callbacks from any plugins in the callback dialog list

Option 2: create a configurable list of model callbacks. Basically add any sequence files marked as model to the list and it will show all the callbacks from the sequence files in the list to the client, unless it cannot find the file in any search directory. Then it wouldn't show.

Option 3: From the add callback dialog allow the user to browse to a sequence file which contains model callbacks

I think adding this functionality will greatly help in making the plugins more abstracted from the process models. Just saying.

Cheers,

View All (7)

View All (2)

Hello,

It would be nice if there were an easy means of programmatically loading a database schema for result processing.

Here's my context for asking:

We have a custom database schema that must be loaded on all of our stations and we'd prefer that it "just works" when our customized database result processing plugin is loaded.

I managed to accomplish this by studying the format of TestStandDatabaseSchemas.ini and writing a parser to insert our schema as necessary. This was a bit painful, though, and the possibility of the format changing without notice has crossed my mind.

Thanks as usual to the R&D team. (Assuming this idea gets some traction! )

Kind regards,

Mr. Jim

View All (5)

Hello,

As we can read in this very good document, we can add information in header for UUT in Report.

It is mentionned that we can do that for StationInfo in the same way:

"The report below includes the custom data in the AdditionalData container. The process for adding custom Station data is similar, but uses the Parameters.ModelData.StationInfo property instead of Parameters.UUT."

In fact, it doesn't work in TestStand 2014 and later, certainly the same for 2013 because the default report plug-ins doesn't support it as you can see in the help of TestStand 2016.

Maybe NI can add it like it is done for UUT.AdditionalData. The goal is to avoid to put some Station Info in UUT result to show it easily in reports.

Best regards.

MaximeR

CLA - CTD

It would be nice to be able to log all requirement links during execution in the report. I think the option should be similar to "Include Attributes".

Currently, loging requirement links in steps is easy as additional result (preconfigured, just include it in step settings).

But logging requirement links in sequences or sequence files is not easily done. It requires either a dummy step which transfers the requirement list to the step requirements or an overelaborate expression in the sequence call step.

I think a drop down would be a good option:

"Log requirements list:

- For all steps

- For steps and sequences

- For steps, sequences and sequence files"

I am not sure if more options are necessary as empty requirement lists wouldn't appear in the report at all.

Norbert

View All (5)

The suggestion is to support logging a datetime with millisecond accuracy to an sql database with an NI_DataOperation step.

I tried to implement this, but the milliseconds are not written to the database.

It would be very usefull to support this feature.

The datetime field in the sql database is defined as follows:

CREATE TABLE

dbo.UUT_RESULTS (

UUT_STARTTIME datetime NOT NULL

)

The datetime is logged to the database, but only up to the seconds, although the format string is defined as "mm-dd-yyyy hh:ii:ss.sss" and the string does contain the milliseconds e.g. "2-10-2016 11:49:15.505".

Software Details: TestStand version 2010 SP1, Operating System: Windows 7

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

Review all idea Exchange and Update status

No selection of any field inside Offline Processing Utility (ORPU) when application starts

Axis labels for graphs in report

Integrate Diff Merge Utility into Sequence Editor

For each StepResult, add StartTime with UNIX time offset

Provide mechanism to disable batch report through "Report Options" dialog box

Simplify exporting arrays of properties

String value - No comparison

Add option to force the report file path expression to be evaluated after the client sequence executes

Create a configurable Model Callback list

Build .sql File button should work

Make TestStand support both local and UTC formats.

Load Schemas Programmatically

Support Additional Station Info into header for standard Report generation plug-ins

2d array as table in report

Have an Option to Include Measurements From a Multiple Numeric Limit Test as a Graph on the Report

Generate a Report of older UUT in database

Option to log all requirement links in report

Logarithmic Graphs in TestStand Reports

Support milliseconds logging to SQL database column with datetime format.