In the TestStand report it uses Limit.Low for equals and LT. This is misleading...

[Taylored_Solution]

I may being too picky but when I have an equals limit I want it called a Equals limit.  When I use the LT it should be the High limit.   I understand from a programming perspective this makes sense but when I show this to my quality inspector I don't want to have to explain myself.  Has anyone else had this "hangup"?  Is there anything I can do?

Step	Status	Measurement	Units	Limits
				Nominal Value	Low Limit	High Limit	Comparison Type
Numeric Limit Test1	Failed	0			9	11	GELE(>= <=)
Numeric Limit Test2	Passed	0			8		LT(<)
Numeric Limit Test3	Failed	0			99		GE(>=)

[pulidotech]

For me the easiest way is to parse the the report afterward.  I tend to use XML reports and I can search the XML for "<Value>LT</Value>" or "<Value>LE</Value>".  Then, the previous property is "Limits".  Within limits is a property for 'Name=Low'; you can change that text to be 'Name=High'.  

[Teds]

I have noticed that too, I was never sure why the limit for an  'LT" was being reported as a Low Limit.  Although, with a bit of explanation to people where I work it was 'accepted' to be OK.

Another option if you are doing HTML reports, is to customize the line using the 'Modify Report Entry' callback.  When you see a numeric limit step come through with the 'LT' comparison type you could then place the Limit Value into the High column in the HTML table for that row.

Good luck,

Teds