Calypso still generates errant reports

[[Ri...]]

This has been around since v5.x.
And can easily be proven on an offline seat when random data is off.

Calypso may display a characteristic as RED when the dimension is either on the low limit or the high limit of the tolerance as set.
Ex: Ø1.073 +.003,-.000
The feature is created at 1.07300000 (I purposely enter 8 digits, rounding is set to 4 digits in Inch mode).
Run the feature and it calculates 1.0730
The characteristic will either be RED or GREEN, in this example I have two features in different locations of the same size.
One characteristic is GREEN the other is RED. Same reported values.
then you generate a PiWeb report.
Oh boy....
Either they will be GREEN or they will be RED. you cant tell which will happen.

A similar scenario tends to happen with True Positions.
Calypso will report a GREEN characteristic on the high limit and PiWeb will report the same characteristic as RED.

I suspect there is a rounding error either in Calypso and or PiWeb.
I can truthfully say I have seen rounding errors of 0.0001 (Inch) on reports.

[[Ro...]]

Hi Rick,
Calypso doesn't round results, regardless of how many places you have it set to report. If it's out by .00000001 it will report it as OT.
If you report to 8 places you should see that it's out of tolerance.

[[Ri...]]

If I program the feature to absolute 8 digits 1.07300000, and it reports 1.073000001, how is that possible on the Offline seat?
Why is one item GREEN and the other item, which is a copy but relocated, RED?

[[Ro...]]

I was more addressing how Calypso doesn't round results. Not sure what's going on with the offline seat. When the program is run online do you get the same behavior as offline?

[[Ma...]]

Please sign in to view this quote.

I think it is very likely that the behavior you see is due to inch/metric conversion. Even though you program it inches, I bet the actual data is all stored and processed in metric with values only displayed in inch units. There is always rounding occurring with the conversions even if is at double precision floating point resolution.

[[Ri...]]

Please sign in to view this quote.

Offline, Online
Same issue and has been around since about v5.x
I cant count how many reports I've read where a value on the report is not the same the opened characteristic in Calypso.
True Positions are the biggest culprit, where the coordinates result and the deviation do not add up to the nominal, always by ± "0.0001" (Inch).
Cant wait for that to come up in an audit.