Good morning. I hope all is well with everyone. Just wondering, does pc dmis have an option to search for the fatest measurement routine? Thaks for your insight.
YES FLYMODE!
A few other tricks to increase routine runtime include (advanced, use extreme caution when implementing)
-reduce prehit/retract distance after "finding" the part, as long as your method is stable enough.
-implement move/increments in lieu of move/clearplanes or move/points.
-if you implement multiple move/increments with flymode on, it will round all those incremental commands simultaneously and make one swift arc-shaped move to the next prehit. Beware, it will clip a significant amount off the distances when it does this.
-assess touchspeed reproducibility. if you don't NEED 0.0001" accuracy, you can easily increase touchspeed to be much higher than the typical 2mm/sec. I've had routines pass MSA using TP200 at 8mm/sec.
-make sure movespeed is max (either 100%, or when using absolute: the maximum that your firmware can accept)
-make sure your firmware's accel parameters reflect the machine's maximum acceleration values.
Oh and implement STAR probes as much as you can, to reduce probe rotations.
YES FLYMODE!
A few other tricks to increase routine runtime include (advanced, use extreme caution when implementing)
-reduce prehit/retract distance after "finding" the part, as long as your method is stable enough.
-implement move/increments in lieu of move/clearplanes or move/points.
-if you implement multiple move/increments with flymode on, it will round all those incremental commands simultaneously and make one swift arc-shaped move to the next prehit. Beware, it will clip a significant amount off the distances when it does this.
-assess touchspeed reproducibility. if you don't NEED 0.0001" accuracy, you can easily increase touchspeed to be much higher than the typical 2mm/sec. I've had routines pass MSA using TP200 at 8mm/sec.
-make sure movespeed is max (either 100%, or when using absolute: the maximum that your firmware can accept)
-make sure your firmware's accel parameters reflect the machine's maximum acceleration values.
Oh and implement STAR probes as much as you can, to reduce probe rotations.
