Dean Hedin wrote: [probing by going to x,y on safe z, than plunging down until probe hits object]
> FYI, It took several hours to probe a 4"x5" surface even at .1 grid > resolution. Hmm, I'm wondering: If I used a probe that is detecting horizontal hits as easily as it detects vertical hits (e.g. a renishaw type probe), wouldn't it normally result in a faster scan to basically: For any x position you want to scan: go to minimum y,z increase y until probe hits (record height minimum_z for all points skipped over by this) retract y until probe doesn't hit loop: increase z by step_z increase y by step_z if the probe hits: retract z until probe doesn't hit, increase again until it hits. (record z) if probe didn't hit: increase z until probe hits. (record z) goto loop until y>max_y Since you don't need to retract z to safe height each time, you would save quite a bit of time, I would assume. Even more savings could be achieved if you did the first part (scanning at minimum_z) from both sides first and only did the detailed surface scan (the loop) for the y-range where the probe hit an object. Unfortunately, this couldn't be done with g-code until now I think. But perhaps the emc2 devs could come up with a C routine one could use from the GUI parts which did that. Would be really neat. regards, Sven ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users