Where'd "Pierce CAD on 3D Rotate" go? It's not in F5 anymore? (It seems that Pierce CAD on 3D Rotate has been incorporated into the software, it just doesn't always work. It seems to sometimes require that when you click to rotate, you first give it a second to realize that there is CAD there. Other times it works exactly as expected.)
I don't see "Save on Execute" in there either.
2017 R1 does indeed fix the Find Hole/Check Distance problem.
I have experienced another bug: Creating a SCN of constructed points which are extracted hits from a circle.
I have 4 radii on a irregular shaped conical feature. I have a program where each hit from each circle is put into individual constructed points, put those points into a SCN and then measured the profile. In 2017 I get an crazy high number that is out of norm. However, this works in 2016 and lower (as this is a few year old program). So what I did to test this out, I created a scan from each circle's hit and measured that and I get what I expect. See code below:
SCN1 =FEAT/SET,CARTESIAN
THEO/<13.985,0,0>,<-1,0,0>
ACTL/<13.98,-0.02,-0.026>,<-1,0,0>
CONSTR/SET,BASIC,PNT5,PNT4,PNT3,PNT2,PNT1,PNT6,PNT7,PNT8,PNT9,PNT10,PNT22,PNT21,PNT20,PNT19,PNT18,PNT11,PNT14,PNT15,PNT16,PNT17,,
DIM 1= PROFILE OF SURFACE OF SET SCN1 FORMONLY VECTOR_LST_SQR UNITS=MM ,$
GRAPH=OFF TEXT=OFF MULT=10.00 ARROWDENSITY=100 OUTPUT=BOTH
AX NOMINAL MEAS +TOL -TOL MAX MIN DEV OUTTOL
M 0.000 0.303 0.204 0.000 0.303 0.188 0.303 0.201 ---|--->
SCN2 =FEAT/SET,CARTESIAN
THEO/<13.985,0,0>,<-1,0,0>
ACTL/<13.98,-0.02,-0.026>,<-1,0,0>
CONSTR/SET,BASIC,CIR11.HIT[1..CIR11.NUMHITS],CIR12.HIT[1..CIR12.NUMHITS],CIR13.HIT[1..CIR13.NUMHITS],CIR14.HIT[1..CIR14.NUMHITS],,
DIM PROF1= PROFILE OF SURFACE OF SET SCN2 FORMONLY VECTOR_LST_SQR UNITS=MM ,$
GRAPH=OFF TEXT=OFF MULT=10.00 ARROWDENSITY=100 OUTPUT=BOTH
AX NOMINAL MEAS +TOL -TOL MAX MIN DEV OUTTOL
M 0.000 0.061 0.204 0.000 0.025 -0.036 0.061 0.000 --#|#---
All the constructed points in SCN1 are the same as .HIT based points in SCN2.
Maybe there's a problem on vectors, so that the scan hasn't the good compensation ? (even if it works in older versions... you should check it ! The little goblin of PC-DMIS is sometimes surprising !!!!!)
I prefer the 2nd solution, it's less long to create !!!!!!!!
That's what I was thinking. In addition, creating vector points in the same spots as the .HIT's results in similar measurement as the .HIT scan. So something is goofy with the carry through extracting each hit from the auto feature into the constructed points.
I created the first new program in 2017 last week and noticed the same thing with t.p. Get everything dialed in, hit create and then watch the spinning wheel for 2-3 minutes. Pretty annoying when you're trying to get something done.
Just ran my first program that I wrote in 2013....Ran nice no glitches minus my gd&t true pos not coming out on the report....I'm sure its nothing but any help would be appreciated
