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.
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".
This technique is actually described in the help section, if you look up move points. This leads me to believe that the ability was put there by design. That's where I first heard of it, and have found it to be pretty handy.
"Moving In Only 1 or 2 Axes
In the Edit window's Command mode, you can set one of the axis values to blank (meaning you completely delete the value) to give the axis a relative move of zero during measurement routine execution. This essentially lets you have a hybrid relative and absolute move point behavior using the MOVE/POINT command.
This only works fully in Command mode. If you use Summary mode to do this, the field disappears from the Edit window. If you want to then set it back to a number value, you need to do so in Command mode.
For example, suppose you want to move in only two axes. Create an Edge Point feature followed by a MOVE/POINT command. Execute the measurement routine. Now delete the X value of the command and execute the measurement routine again. There won't be any X component in the move point motion, regardless of where you take the edge point."
Number Games you are correct. This is how I learned this Move Point process from the Help section. Hexagon either needs to Fix this issue with the blank Axis in the Move Points and Fix the issue with the Increment Move in offline mode with the virtual Machine. If not then Hexagon needs to remove the Blank Axis Move Point from the Help section.
