hexagon logo

Path Optimizer

Do you guys ever use the path optimizer? Does it work well? Does it really save as much time as it claims?

I tried using it on some smaller programs I have and it crashes the computer every time so I haven't actually utilized it. However when it calculates the new path it claims something like 70% optimization. what does that 70% mean?

Is it worth using?
  • As the programmer, YOU are the Path Optimizer Rolling eyes

    I don't use it. I tried a few times and it just gave me a bunch of stupid move points that made it slower lol (huge shocker there)
  • As the programmer, YOU are the Path Optimizer Rolling eyes

    I don't use it. I tried a few times and it just gave me a bunch of stupid move points that made it slower lol (huge shocker there)


    Thats kind of what i figured.
  • I once left on vacation and one of the operators "Optimized" one of my programs on accident and it reordered all my features to be "fast".

    Needless to say it broke the program and I had to rewrite it because he saved over the good file. (I could have had IT recover it but we have a 3rd party guy and it was faster to rewrite)

    I am not a huge fan of optimize path. I would rather run collision detection then go back and fix crashes case by case
  • As the programmer, YOU are the Path Optimizer Rolling eyes

    I don't use it. I tried a few times and it just gave me a bunch of stupid move points that made it slower lol (huge shocker there)


    That was my experience too. I tried it on some simple parts that was just a whole bunch of vector points in a mold cavity using just one probe angle. It chose to measure the points in a most bizarre order. I think it considers the 3D distance between features rather than the distance the probe would actually have to travel around other features to get between them.

    The fun part is when I put in the auto move points to avoid collisions. The moves were all over the place. Watching it run with fly mode on was kinda fun. The probe was bouncing around all over the place in a very cringe inducing manner. It could be a fun way to mess with a skittish CMM operator. Stuck out tongue closed eyes
  • Tried it once on a program, but it actually made the program slower.


  • That was my experience too. I tried it on some simple parts that was just a whole bunch of vector points in a mold cavity using just one probe angle. It chose to measure the points in a most bizarre order. I think it considers the 3D distance between features rather than the distance the probe would actually have to travel around other features to get between them.

    The fun part is when I put in the auto move points to avoid collisions. The moves were all over the place. Watching it run with fly mode on was kinda fun. The probe was bouncing around all over the place in a very cringe inducing manner. It could be a fun way to mess with a skittish CMM operator. Stuck out tongue closed eyes


    I use fly mode on every program, i like how it rounds off corners & makes things look a little more cool (IMO) lol. i turn it off if i am going into a tight area of the part though


  • I do use fly mode though, on every single program, i like how it rounds off corners & makes thins look a little more cool (IMO) lol. i turn it off if i am going into a tight are of the part though


    Fly Mode is something i havent ever used. that and Fast Probe mode. What does fast probe mode do? does it just increase the machine speed?


  • Fly Mode is something i havent ever used. that and Fast Probe mode. What does fast probe mode do? does it just increase the machine speed?


    My understanding is that fast probe mode makes an analog probe work more like a TTP. When you take a hit with an analog probe it will first approach the part until the probe deflects past the trigger force. Then it will slowly back off and record the point position at the instant that trigger force is reached. It makes it more accurate. With fastprobemode I think it records the hit position on the approach and immediately rapids away. It makes touch points measure faster, but looses some accuracy (just a little). Not all analog probes/controllers will do it. I think most Renishaw probes aren't supported on that feature anymore. I once had a B&S machine with a SP25 that supported the feature. I only used it when taking points for the rough alignment. Saved a few seconds.


  • I use fly mode on every program, i like how it rounds off corners & makes things look a little more cool (IMO) lol. i turn it off if i am going into a tight area of the part though


    Fly mode scares me because collision detection doesn't take fly mode in to consideration. How can you tell if it is going to crash or not when you cant see where it is moving?