has anyone tried running routines in 2017r1 with blank moves? ( MOVE/POINT,NORMAL,<,-0.6704,> ) Just had several cmm crashes where these move types seem to be driving to 'zero' instead of 'blank'.
So awhile back I learned this trick of leaving some of the fields blank in a MOVE/POINT, NORMAL.
I immediately did not trust it, even after my coworkers showed me that it worked (this was using 2013 MR1).
My gut feeling was that this trick was probably exploiting a loophole where Wilcox forgot to disallow blank fields like they do
everyotherfield.
And now it looks like they closed that loophole.
Best Practice = do not leave any fields blank.
The only time I have this issue is when there are Move Points in the program containing variables. Then PC-DMIS will sometimes fill in the blank axis in the Move Point with a number or another variable. I am using 2017 R1 with a program that has a Move point with the X,Y Axis blank with no issues on line during testing. But those blank axis Move Points are only used for collision testing in offline mode. I use these Blank Axis Move Points when I disable the Increment moves in my template. As Josh stated "Best Practice = do not leave any fields blank".
The only time I have this issue is when there are Move Points in the program containing variables. Then PC-DMIS will sometimes fill in the blank axis in the Move Point with a number or another variable. I am using 2017 R1 with a program that has a Move point with the X,Y Axis blank with no issues on line during testing. But those blank axis Move Points are only used for collision testing in offline mode. I use these Blank Axis Move Points when I disable the Increment moves in my template. As Josh stated "Best Practice = do not leave any fields blank".
