On Monday 29 January 2018 18:09:53 Gene Heskett wrote: > Greetings all; > > In my hole finder routine I have run in absolute distances because for > the most part I was only interested in finding the center of the hole, > and was using touch offs to locate one hole at a time. > > But this won't work for the bolt holes in the back of the chuck since > if I make the G38.2 Y motion as a search to function, it adds up in > the run checker and tells me it way too big and exceeds the virtual y > limits of my tables motion. The machine can reach the outer edges of > the holes with around 1/4" to spare. > > So it looks like I will have to use relative movements so I can > restrict the probing searches to around 1.25x the size of the bolt > hole I've lowered the spinning probe into. But when I am in relative > mode, what mode is the value recorded at contact in #5061 & #5062? > relative, or absolute? Or, are they converted, one to the other by > the G90-91 gcodes? > > I'm not allergic to sprinkling G90 and G91's around in the code, but > the figures I obtain must be in absolute from the last touchoff > co-ordinates so I can then know the absolute co-ords for the new drill > holes in the backplate. Which in this case is the center of the bolt > circle as determined by measureing the rear of the chucks center hole > and using that as the touchoff 0,0 to an accuracy of about .00025" > which is the repeatability of this code. > > What I'm saying is that the recorded value in those 2 vars, must for > my uses, be absolute even if I'm doing the g38.2 stuff in relative > mode. > > Thanks for any insight.
The closest I can find in the docs says that the #5061 etc values are in the current co-ordinate system. Zero mention of distance mode. So I am going make a subroutine out of the 8 movements that define a holes location, and write a wrapper for that which will, after locating the rough center of one of these bolt holes, will retract the probeing wire out of whereever it might be, take the machine to that location, lower the probe into the hole, put it into the relative mode, and find the holes center with relative small motions that should not trip the y bounds checking. The values I pick out of #5061 and #5062, should be absolute in the current co-ord system, and after I do the math to determine the center, I can go back to G90 and lift the probe to clear, then drive it to the center of the hole for visual verification thats its at least inside the hole. Change the xy vars to take it to the next hole, lower it into the hole, go to G91 mode and find that hole. Wash, rinse and repeat for all 6 holes. Then I can take that data to the backing plate and cut the slightly oversized holes with an 8mm carbide tool, driving it in a small circle to get the hole size I need, which with 10mm bolts 3 to 4mm for the hole fattener. Does that sound like a plan once I've diddled the plates rotation so as to re-use the 3 existing holes? I could automate that to a very high degree if I could make gladevcp show my camera as I have all the offset and alignment stuffs working just fine. Then I could simply align the co-ord r value. But everytime I get it working, the next update to lcnc kills it. Frustrating... Anyway, tomorrow is another day. And a light rain has started here. Thanks for reading folks. -- Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene> ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
