NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Distinguishing High limit, Low Limits in databse

I have a numeric test performing a measurement lets say X<-2.0V. So -2.0
is my high limit. The test works fine, but in the databse it is storing it as
a low limit. So basically, my database spits out contradictory information
saying that the step passed but the data is lower then the low limit. I am
not sure what the cause of this problem is. Any help is appreciated. Thanks
guys.

example:

Meas XXXX Numeric Limit Test, x < -2.0
Meas XXXX Numeric Limit Test, x >2.0

     Query1
UUT_SERIAL_NUMBER STEP_NAME   HIGH_LIMIT  LOW_LIMIT   UNITS       DATA          XXXXX                              Meas XXXX                                  -2               V          -2.8416816
                 
XXXXX                              Meas XXXX                                  2                   V       2.8423303
 
Both queries return a passed status.
 
 
Seems like everyother test I do that I only specify one limit, it puts it automatically into the low limit field.
                 
0 Kudos
Message 1 of 3
(2,712 Views)

When the comparison type only requires one limit, we always store the value in the LowerLimit.  The default schema stores information regarding the Comparison Type, so you would notice GT or LT as values to determine if the test passed or failed.

Allen P.

NI

0 Kudos
Message 2 of 3
(2,708 Views)
Thanks... I saw that, I just didn't know it automatically put it into the low limit fields.   Thanks again.
0 Kudos
Message 3 of 3
(2,703 Views)