11-13-2015 02:31 AM
Hello,
I'm using TestStand 2013.
Background
I have a number of tests which involve an electronic handshake with the UUT. Unfortunately, the handshake is quite time-sensitive, and I believe that the jitter in the test station (which runs Windows) sometimes causes the test station to respond about 50ms too slowly to the UUT's message, and the handshake fails.
This is a reasonably rare event though, so the most sensible solution is to simply let the test system re-try the test a few times.
Attempted solution
To support re-tries, I enabled Looping:
Unfortunately, this adds multiple rows to the XML report to each test. Even though I unchecked "Record Result of Each Iteration", TestStand still logs the following:
Questions
Thanks!
Solved! Go to Solution.
11-16-2015 11:28 AM
Hi JKSH,
To disable logging the results from looping, refer to the Properties window of the step and in the Run Options Tab, select "Disable" in the 'Result Recording Option' drop-down menu.
Looping works for what you're doing, but you may want to also look into Callbacks to see if that would be more elegant for your application. This White Paper will give more details on the different types of callbacks and how they are used.
http://www.ni.com/white-paper/6605/en/
Cheers,
Hannah Zimmerman
Applications Engineer
National Instruments
11-16-2015 08:02 PM
@ZannahBanana wrote:
To disable logging the results from looping, refer to the Properties window of the step and in the Run Options Tab, select "Disable" in the 'Result Recording Option' drop-down menu.
Hi Hannah,
Thanks for your suggestion and link! The callbacks look quite powerful; I'll have to study these in detail.
Unfortunately, I can't disable the "Result Recording Option" because I still want to see the step itself in the report. I just want to suppress the parts in the blue box in my screenshot above, but I want to log the step name, status, and measurement.
For now, I've simply implemented the loop in a LabVIEW VI, so that TestStand itself isn't aware of the loop.
11-17-2015 09:24 AM
Hi JKSH,
I should have also added that whichever variables you'd like to see in the report can be added to the results list, as shown in this article:
http://www.ni.com/white-paper/8289/en/#toc6
Check out part 6: Adding Custom Data to the Report. That way you can add only the variables you'd like to see. Implementing in LabVIEW definitely works too, but I just wanted to make sure you had this information as well!
Hannah Zimmerman
Applications Engineering
National Instruments
11-22-2015 07:36 PM
11-23-2015 03:34 AM
Hi JKSH,
You can modify Style Sheet (for me: tr5_horizontal.xsl) in Report Options.
I use standard XML comments:
<!-- Comment -->
I spent comment out lines 884-909
<!-- <xsl:if test="ts:NumLoops"> <tr> <td style="padding-left:{$gSingleSpaceValue}px;">Number of Loops:</td> <td colspan="{$gValueSpan};"> <xsl:value-of select="ts:NumLoops/@value"/> </td> </tr> <tr> <td style="padding-left:{$gSingleSpaceValue}px;">Number of Passes:</td> <td colspan="{$gValueSpan};"> <xsl:value-of select="ts:NumPassed/@value"/> </td> </tr> <tr> <td style="padding-left:{$gSingleSpaceValue}px;">Number of Failures:</td> <td colspan="{$gValueSpan};"> <xsl:value-of select="ts:NumFailed/@value"/> </td> </tr> <tr> <td style="padding-left:{$gSingleSpaceValue}px;">Final Loop Index:</td> <td colspan="{$gValueSpan};"> <xsl:value-of select="ts:EndingLoopIndex/@value"/> </td> </tr> </xsl:if> -->and lines 1406-1419
<!-- <xsl:if test="$endingLoopIndex"> <tr> <td style="padding-left:15px;"> <xsl:choose> <xsl:when test="@callerName"> <xsl:value-of select="@callerName"/> </xsl:when> <xsl:otherwise> <xsl:value-of select="@name"/> </xsl:otherwise> </xsl:choose> (Loop Indices) </td> </tr> </xsl:if> -->Wtih this modified Style Sheet, i haven't loop info in my report.
11-23-2015 07:42 PM