PR 260356 Error on line profile (form only) report depending on best fit meth

huangyhg

Error on line profile (form only) report depending on best fit method
<< Jon Wood  --  03/10/09  14:10:55>>
There's something odd going on but I'm not 100% sure what it is.
I performed a linear open scan, then added a form only profile to it.
I noticed different results between Legacy and FCF's, looking closer I found that one was using Lease Sq, and one used Vector, so I change both to Least Sq.
This gave me consistant results but the OutTol values don't make sense and the graphical analysis shows both green and red!!!!!!!!!
Even on Vector the error bars show out of tol above and below?
It's almost like it's reporting Form and Location?
  
Steps to reproduce:
See attached program and report.
<<END>>

<< Changes made by David Petrizze -- 03/16/09  08:38:02>>
Action:  David Petrizze to Yanhua Huang
<<END>>
<< Don Turcotte  --  03/12/09  14:07:51>>
In PR # 257022, the formonly profile was changed to include a consideration of size.  For example, a formonly profile of a circle can show out of tol if the measured circle is smaller than the nominal circle even if it has perfect form.  This is in conformance with Y14.5.  With this change for formonly,  the linear graphic shows a bi-directional deviation (the same as formandlocation) and the outtol value is based on deviation from the nominal surface.  You can see this more clearly if you turn on the reporting of MAX, MIN.
If you do not want formonly profile to include size, then change the registry setting Option\UseISOCalculations to true (1).  In V44, there is a pulldown list on the Advanced tab of the FCF dialog that allows you to select the GDT Standard (this overrides the registry setting).  So in V44B, if you select GDT Standard of ISO 1101, then formonly will ignore differences in nominal, measured size and the linear graphic will be unidirectional.  The legacy dimensions are still controlled solely by the registry setting.
I did fix one issue in V44B:  when editing an existing FCF to change the GDT standard, the FCF was not recalculating the dimension.
Files inserted to server
------------------------
V44B\MENU\FEATCTRLFRMOUTPUTDLG.CPP

<<END>>
<< Changes made by Don Turcotte -- 03/12/09  14:08:04>>
Action:  Don Turcotte to David Petrizze, Status:  OPEN to REVIEW
<<END>>
<< Changes made by Tim Wernicke -- 03/10/09  09:17:21>>
Action:  Tim Wernicke to Don Turcotte, Assigned:   to Don Turcotte, Priority:  to Critical
<<END>>

huangyhg

<< Changes made by Don Turcotte (Field Changes) -- 04/01/09  14:42:07>>
Action:  Don Turcotte to Yanhua Huang, Status:  OPEN to REVIEW
<<END>>

<< Changes made by Don Turcotte (Resolution Data) -- 04/01/09  14:42:01>>
** Bug Fix - New In Current Version -  - 104422 -  **
<<END>>

<< Don Turcotte (Development Notes)  --  04/01/09  14:40:41>>
I have fixed the updating (again) so when you change from ASME Y14.5 to ISO 1101 (or vice versa) the FCF is re-calculated.

When you select ASME Y14.5, the linear graphic deviation on the left represents the deviation below the surface (turn on reporting of MIN to see this) and the linear graphic deviation on the right represents the deviation above the surface (turn on reporting of MAX to see this).  The center of the graphic represents the nominal surface (0 deviation).

Files inserted to server
------------------------
V44B\DIMENS\FEATCTRLFRM.CPP
<<END>>

<< Changes made by Tim Wernicke -- 03/31/09  08:50:12>>
Action:  Jon Wood to Don Turcotte
<<END>>

<< Changes made by Jon Wood -- 03/31/09  11:43:43>>
Status:  RESOLVED to OPEN
<<END>>

<< Jon Wood  --  03/31/09  11:42:10>>
Just tried changing to Use ISO in the FCF dialog.

I get identical results (i.e. a bi-directional error bar)


Even when the intention is to use ASME how are the error bars meant to be interpreted?
<<END>>

<< Yanhua Huang  --  03/17/09  21:09:22>>
Reviewed, OK.
<<END>>

<< Changes made by Yanhua Huang -- 03/17/09  21:09:26>>
Action:  Yanhua Huang to Jon Wood, Status:  REVIEW to RESOLVED
<<END>>