Hi all, long time user, first time needing to post.
10,000 FT summary:
Our summary upon end of program execution shows OUTTOL=2, which is (falsely) alerting our auditors.
The data output from CSV shows all dimensions are well within print tolerances.
Details:
We are running 2012 MR1.
As standard practice for all my programs, they are looped and report to CSV. These two programs in question are unique, solely that they are using generic features for dimension output.
I have determined the OUTTOL values visibly display in edit window as a RED dim result, upon the execution of ONLY the first loop, every time. However, the data output for all loops show passing results, every time.
All subsequent loops function as intended with zero contribution to the OUTTOL count, and zero visible red DIM outputs.
--Yes, we validated all our dimensioned nominals and tolerance bands within PC-DMIS are exactly per print, and likewise with our SPC software (Measurlink).
I can easily remedy the issue by omitting the generic features (report means for average values and max values) from the routine, but at a cost of repeatability; which would also induce another gage R&R.
The big question I'm looking for an answer to: Is this a 2012 MR1 glitch? Has anyone else experienced this?
Thanks in advance! -Louis
Code examples of generic assignments. (V6=0, V7=0.007 (V7 = a BASIC offset value))
10,000 FT summary:
Our summary upon end of program execution shows OUTTOL=2, which is (falsely) alerting our auditors.
The data output from CSV shows all dimensions are well within print tolerances.
Details:
We are running 2012 MR1.
As standard practice for all my programs, they are looped and report to CSV. These two programs in question are unique, solely that they are using generic features for dimension output.
I have determined the OUTTOL values visibly display in edit window as a RED dim result, upon the execution of ONLY the first loop, every time. However, the data output for all loops show passing results, every time.
All subsequent loops function as intended with zero contribution to the OUTTOL count, and zero visible red DIM outputs.
--Yes, we validated all our dimensioned nominals and tolerance bands within PC-DMIS are exactly per print, and likewise with our SPC software (Measurlink).
I can easily remedy the issue by omitting the generic features (report means for average values and max values) from the routine, but at a cost of repeatability; which would also induce another gage R&R.
The big question I'm looking for an answer to: Is this a 2012 MR1 glitch? Has anyone else experienced this?
Thanks in advance! -Louis
Code examples of generic assignments. (V6=0, V7=0.007 (V7 = a BASIC offset value))
Code:
AH_P1 =FEAT/CONTACT/VECTOR POINT/DEFAULT,CARTESIAN
THEO/<-0.007,0.155,0.0025>,<0,1,0>
ACTL/<-0.007,0.155,0.0025>,<0,1,0>
TARG/<-0.007,0.155,0.0025>,<0,1,0>
SNAP=NO
SHOW FEATURE PARAMETERS=NO
SHOW CONTACT PARAMETERS=NO
AH_P2 =FEAT/CONTACT/VECTOR POINT/DEFAULT,CARTESIAN
THEO/<-0.007,0.155,0>,<0,1,0>
ACTL/<-0.007,0.155,0>,<0,1,0>
TARG/<-0.007,0.155,0>,<0,1,0>
SNAP=NO
SHOW FEATURE PARAMETERS=NO
SHOW CONTACT PARAMETERS=NO
AH_P3 =FEAT/CONTACT/VECTOR POINT/DEFAULT,CARTESIAN
THEO/<-0.007,0.155,-0.0025>,<0,1,0>
ACTL/<-0.007,0.155,-0.0025>,<0,1,0>
TARG/<-0.007,0.155,-0.0025>,<0,1,0>
SNAP=NO
SHOW FEATURE PARAMETERS=NO
SHOW CONTACT PARAMETERS=NO
ASSIGN/V5=SUM(AH_P1.Y+AH_P2.Y+AH_P3.Y)/3
AH_PNT1 =GENERIC/POINT,DEPENDENT,CARTESIAN,$
NOM/XYZ,<V6,V5,V6>,$
MEAS/XYZ,<V6,V5,V6>,$
NOM/IJK,<V6,1,V6>,$
MEAS/IJK,<V6,-1,V6>
AG_T1 =FEAT/CONTACT/VECTOR POINT/DEFAULT,CARTESIAN
THEO/<-0.007,0.005,0.1323>,<0,0,1>
ACTL/<-0.007,0.005,0.1323>,<0,0,1>
TARG/<-0.007,0.005,0.1323>,<0,0,1>
SNAP=NO
SHOW FEATURE PARAMETERS=NO
SHOW CONTACT PARAMETERS=NO
AG_T2 =FEAT/CONTACT/VECTOR POINT/DEFAULT,CARTESIAN
THEO/<-0.007,0.0025,0.1323>,<0,0,1>
ACTL/<-0.007,0.0025,0.1323>,<0,0,1>
TARG/<-0.007,0.0025,0.1323>,<0,0,1>
SNAP=NO
SHOW FEATURE PARAMETERS=NO
SHOW CONTACT PARAMETERS=NO
AG_T3 =FEAT/CONTACT/VECTOR POINT/DEFAULT,CARTESIAN
THEO/<-0.007,0,0.1323>,<0,0,1>
ACTL/<-0.007,0,0.1323>,<0,0,1>
TARG/<-0.007,0,0.1323>,<0,0,1>
SNAP=NO
SHOW FEATURE PARAMETERS=NO
SHOW CONTACT PARAMETERS=NO
AG_T4 =FEAT/CONTACT/VECTOR POINT/DEFAULT,CARTESIAN
THEO/<-0.007,-0.0025,0.1323>,<0,0,1>
ACTL/<-0.007,-0.0025,0.1323>,<0,0,1>
TARG/<-0.007,-0.0025,0.1323>,<0,0,1>
SNAP=NO
SHOW FEATURE PARAMETERS=NO
SHOW CONTACT PARAMETERS=NO
AG_T5 =FEAT/CONTACT/VECTOR POINT/DEFAULT,CARTESIAN
THEO/<-0.007,-0.005,0.1323>,<0,0,1>
ACTL/<-0.007,-0.005,0.1323>,<0,0,1>
TARG/<-0.007,-0.005,0.1323>,<0,0,1>
SNAP=NO
SHOW FEATURE PARAMETERS=NO
SHOW CONTACT PARAMETERS=NO
ASSIGN/V8=MAX(ARRAY(AG_T1.Z,AG_T2.Z,AG_T3.Z,AG_T4.Z,AG_T5.Z))
ASSIGN/V9=IF(V8==AG_T1.Z,AG_T1.ALL,IF(V8==AG_T2.Z,AG_T2.ALL,IF(V8==AG_T3.Z,AG_T3.ALL,IF(V8==AG_T4.Z,AG_T4.ALL,AG_T5.ALL))))
AG_TOP =GENERIC/POINT,DEPENDENT,CARTESIAN,$
NOM/XYZ,<V7,V9.Y,V9.Z>,$
MEAS/XYZ,<V7,V9.Y,V9.Z>,$
NOM/IJK,<V6,V6,1>,$
MEAS/IJK,<V6,V6,1>