I am having trouble using the true position report in v4.1. The measured values are way off. Does anyone have advice on using the new TP reporting?
V3.7 to V4.1 True Position?
Collapse
X
-
What's the call that gives you trouble? Does it have a VC on the datums? If so, this can lead to some surprising results, as V3.7 could not handle the VC analysis.
Please post your exact TP calls.
Jan.***************************
PC-DMIS/NC 2010MR3; 15 December 2010; running on 18 machine tools.
Romer Infinite; PC-DMIS 2010 MR3; 15 December 2010.
Comment
-
Originally posted by mwheeler View PostThe feature is a cylinder RFS. The problem I am having is that the measured value is 0. The feature is out of position and this should not be 0. Also what is the section for offset and rotation? Can I use 3.7 reporting stlye?
Thanks,
Mark
Yes, you can get back to 3.7 style dimensioning, by going Insert/Dimension and go all the way to the bottom and click on Use Legacy Dimensions. That does not mean that they are right though... I have tested the 4.2 Xactmeasure GD&T extensively and I find it to be reliable.
Again, please post the complete TP call, INCLUDING the datum calls.
Jan.***************************
PC-DMIS/NC 2010MR3; 15 December 2010; running on 18 machine tools.
Romer Infinite; PC-DMIS 2010 MR3; 15 December 2010.
Comment
-
DATDEF/FEATURE=-A-,DATUM=A
DATDEF/FEATURE=-B-,DATUM=B
DATDEF/FEATURE=-C-,DATUM=C
FCFLOC1 = TRUE POSITION OF 35.6-CYLINDER
FEATCTRLFRAME/SHOWNOMS=NO,SHOWPARAMS=YES,SHOWEXPANDED=YES
CADGRAPH=OFF REPORTGRAPH=OFF TEXT=OFF MULT=10.00 OUTPUT=REPORT UNITS=MM
COMPOSITE=NO,FIT TO DATUMS=YES,OUTPUT ALIGNMENT=Current Alignment
SIZE TOLERANCES/1,DIAMETER,31.5,0.8,0.8
PRIMARY DIMENSION/TRUE POSITION,DIAMETER,2.0,RFS,<PZ>,<len>,A,B,C
SECONDARY DIMENSION/<Dim>,<tol>,<MC>,<PZ>,<len>,<dat>,<dat>,<dat>
NOTE/FCFLOC1
FEATURES/35.6-CYLINDER,,
Comment
-
One thing that immediately strikes me here: you are using a "-" and the "." sign in your feature names. I found that to be highly problematic. Hoedemann has straightened me out on that many times. Change them before you run into more problems. Search for Hoedeman's post on this issue.
Other then that, your call looks clean and it should never give you zero, unless you are dead-on.
Jan.***************************
PC-DMIS/NC 2010MR3; 15 December 2010; running on 18 machine tools.
Romer Infinite; PC-DMIS 2010 MR3; 15 December 2010.
Comment
Related Topics
Collapse
-
by jay RGood afternoon everyone,
I have read here about issues with 3.25 true position reporting but can not seem to find any fixes for it....-
Channel: PC-DMIS for CMMs
10-16-2008, 02:21 PM -
-
by AmberI have a true position call out on a part I'm working on .002|A] in the FCF on my report it is reporting my X and Y as .0064 and .0043 for a true position...
-
Channel: PC-DMIS for CMMs
07-16-2014, 12:51 PM -
-
by gppcdmisWhen reporting true position of a diameter the measured values do not match the actual values that I see on the program section.
They are off up...-
Channel: PC-DMIS for CMMs
06-21-2012, 11:22 AM -
-
by Ken8282I recently did a true position and may 321 alignment to the datums and picked the feature to be true positioned but I get a smaller TP than if I do a...
-
Channel: PC-DMIS for CMMs
04-30-2018, 03:38 PM -
-
by mrwildebeastHi All,
Can anyone explain ( or point to an explanation ) of the maths behind a true position calculation, my gd & t knowledge is...-
Channel: PC-DMIS for CMMs
05-16-2008, 02:01 AM -
Comment