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.
Hey Josh Carpenter or Don Ruggieri, when using the new SIZE feature, there are options for Any Cross Section or Specific Fixed Cross Section. How can I specify the fixed cross section location of a cylinder? Or I am interpreting this incorrectly?
bfire85 To use SCS correctly, you will need to create the cross section feature at the specified location and use it as the input. Typically this means the input is a circle rather then a cylinder.
I use move points only when moving way above my part when switching probes. I noticed that when I type in, let's say... MOVE/POINT<0,0,14> it switches to MOVE/POINT<0,0,1>. I then need to retype in 14 for it to change to 14. This has happened a couple of times on me. I notice it right away, so its an easy fix, but this "could" cause problems.
Has anybody else been using the measurement strategies for an autoplane, specifically TTP Plane Circle? If so, have you had any issues? I don't know what the algorithms are doing behind the scenes but it seems to be getting glitchier by the minute here. When I first created the program everything looked fine. Upon opening it a week later and attempting to run it, my first DCC plane was not probing in the right locations. Upon trying to edit it, first it stopped showing any pathlines and now it won't let me even set the number of hits. I type in 16 and it changes to 3. I type in 16 again and it changes to 1...
Apparently I'm the only one to experiment with this new feature and I think that I'm done with it. I've already spent far too many hours scratching my head over this. Problems range from pathlines not showing to incorrect hit locations to feature not running at all (no error pops up but machine just sits as if it's waiting for something) to software crashes. These planes worked okay in another measurement routine, so I don't know what's going on. The only differences that I can come up with between that program and this one are the installation of sp1 and the fact that I'm using viewpoints in this program.
So, I was literally just having this exact issue. A 2 segment 13mm hole was giving me either 5 hits, with one hit not equally spaced or it would force 3 hits, even while the dialog box was calling for 5. For some reason void detection was on. I've never turned this option on, ever. Turned it off, everything went back to normal...
Thanks for the reply.
