Report problem

[JohanS]

Hi,

I'm having some problems with the reports in the report viewer.

When running Test UUTs on a sequence the report for every run iteration should show up in the report viewer.

This will happen the first time the sequence is run, but the on the second run I get an error in the viewer saying "Unable to load the XML Report End tag was not expected at this location".

After the test is finished the complete report that I get in the viewer looks fine, and all results is there.

I have tried this running the built in Teststand demo Computer Motherboard sequence in the Simple Teststand Operator Interface and get this problem there as well. (pic attached)

[Anand_Jain]

Hi

Couple of questions:

1. What version of TS are you using and can you attach your reportoptions.ini file. 

2. Have you made any changes to the proces model. 

Anand Jain

National Instruments

[JohanS]

Hi Jain,

I am using TS 2013, and I made no alterations to the sequential model that I'm using.

In the folder C:\ProgramData\National Instruments\TestStand 2013\Cfg there don't seem to be a 

TestStandModelReportOptions.ini. 

Strange, should there be one?

I have done some changes to the report options from within TestStand (see pic)

[Anand_Jain]

Hi

Please attach all files under - C:\ProgramData\National Instruments\TestStand 2013\Cfg\ModelPlugins

Anand Jain

National Instruments

[JohanS]

Ok, here they are.

There is a file called Addons.cfg.sources but I had to rename it to get it to attach

[Daniel-E]

Hey Johan,

I attempted to reproduce this on my machine with your files, but was unable to do so. Let me list the steps I took, and please point out any differences in the process:

1. Started LabVIEW simple user interface (<TestStand>\UserInterfaces\Simple\LabVIEW\TestExec.exe)

2. Opened computer motherboard example

3. Execute the sequence with the Test UUTs entry point. 

4. I ran the sequence for two UUTs.

Throughout this process, the report display at the bottom of the user interface window continued to display data and did not show any errors. Is this the same process you took to reproduce the issue? I'll be happy to investigate it further once I can see the behavior you are seeing.