From Saturday, Nov 23rd 7:00 PM CST - Sunday, Nov 24th 7:45 AM CST, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

NI TestStand Idea Exchange

Community Browser
Top Authors
cancel
Showing results for 
Search instead for 
Did you mean: 
Post an idea

Hello Team,

In the additional results of step settings, if we have long list of results to log and like to rearrange the list, it is very effort taking to rearrange using the “Move Selected Results Up/Down” control button.

It would be easy if we have

1. Option to select multiple results  while using the “Move Selected Results”  control button 

2. Option to have drag and drop to move the selected results.

 

 

MultipleResultstoMoveSelection.jpg

 

Thanks

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.

 

MoveSelectedResultUp.png

Thanks

 

Dear,

 

Browsing through NI documentation I could not see whether logging test results in STDF format is already available or not, and for which SW versions.

I believe there must be some updates for NI document (from 2007) under the following link:

http://digital.ni.com/public.nsf/allkb/BDEEB8C8EBA6D89D862572E400438F74

 

Could anyone please clarify the status?

Background:

Currently we are looking into the this as it might be very interesting topic to introduce in our production, where we have the following SW running:

- NI Teststand 4.2.1 & 2.0.1

- LabView 2009 SP1

 

Best regards

Dejan Lisinac

Hello,

 

Everytime you want to update the UUT container, the report generation sequence has to be revalidated. Smiley Mad

 

Please modify these behaviour ! Smiley Tongue

 

These behaviour could be perhaps modified by adding a sub container in the UUT container : UUT.Custom

These container could be "non typed" in order to be customizable without side effect. Smiley Very Happy

 

Thanks a lot!

Hi,

 

It would be nice to have another group of the steps.

 

--send an email,

--send a notification to the syslog server,

--sent a notification to the event log.

 

It could improve sequence reporting and notifications. The coding these functionalities in the modules no longer wouldn't be needed. 

Have an option in Report Options to modify report format. 

 

1. A new tab "Report Format" which can provide the option to generate report in default mode (I call it vertical) or customize to generate in horizontal format.

The Report Format tab can have defined set of options for user to enable in the report. The horizontal format would look like something similar to as shown in the attachment "Report_Horizontal.jpg".

 

2. Have a checkbox to generate report in Horizontal Format on the "Contents" tab. When selected the report will be generated with the similar table columns shown in the attachment "Report_Horizontal.jpg".

 

 

Download All

If have to run 10 different UUTs for each group, the TestStand report should contain a either mass header or footer that shows the UUT group statistics, Example: 10 UUTs total run, 7 Passed 3 Failed, in It would seem almost obvious that the TestStand report would contain this information.UUTGroupResults.JPG

 

 

 

I've encountered on several occassions, customers who assign serial numbers / partnumbers during the test process who still wish to do on-the-fly recording.... and are disatisfied with the default behavior of the reporting because their header persists in showing the blanks etc.

 

While I understand that it's easier to build file paths / headers once, and then append the body content onto them, it would be especially elegant, if there was:

 

(a) a way for me to manually trigger (via a callback perhaps) a refresh of the entire header or

(b) if at the very least, the header section & file path were overwritten/updated once at the very end.

 

Since it seems to me that the header has to be re-written at least partially to account for the failure-chain logic, it wouldn't seem that much more work (or that much more inefficient) to just refresh the whole thing?