On Thursday 31 July 2014 03:05:27 Marcus Bowman did opine And Gene did reply: > On 31 Jul 2014, at 05:20, Gene Heskett wrote: > > I have an autoz routine that measures the length of a mill or drill > > bit to precisely set the etching depth of a pcb being milled. > > > > The typical .drill file from eagle may need 6 or 7 drills before its > > done. > > > > I wasn't having what I would call predictable results from using the > > tool length adjuster, G43.1 I think it is, so I switched to the G10 > > L2 P# method, > > Have you tried G10 L20 P~ X~ Y~ Z~
No > Does it suffer from the same problem? Unk. I'll check the users docs, but ISTR I saw something that discouraged me. Basically, I want something that will overwrite any existing offsets, as opposed to adding to the existing ones at the instant of the call. Looking it up and reading it on that machine, that line about "calculated" is the confusing part. Whats "calculated" about G10 L20 P1 z#101 if it sets G55's z to the contents of #101? likewise G10 L20 P2 z#101 for G56's Z If that is in fact what it does, replacing the current value there, then its exactly what I want to do, eg replace any value currently stored in G55 and G56's image of Z, as opposed to adding #101 to it. Which is what the L2 version seems to be doing. And its costing me money in the form of broken tooling at $10 to $20 a mill, and in damaged pallets. If in fact replacement is what it does, and I will check that after I have finished a nights sleep, what the heck does it mean by "calculated" BUG REPORT: I also ran into a 2.6.0 showstopper yesterday, I ran an axis into the limit switch, in 5 minutes it had not timed out to re-enable linuxcnc so the ignore limits could even be checked. I was forced to power down the motors and manually move it off the switch, goto another screen and force a reboot. Thats a showstopper since I had to change tools, and go through the homing operation, which for pcb etching is a bit elaborate & time consuming since its G38.2 based homing, all over again. In 2.5.4 it timed out in 15 seconds or so and was recoverable. I do not see the utility in forcing the timeout. Its purpose? > > Marcus > > > since I run the top of the board stuff in G55, and the bottom of > > the board stuff in G56. > > > > But that isn't working all that well, and I have deduced that > > everytime I use it, even though I use it from the G54 environment, > > the resultant offsets are acting cumulative. Is there a fix for > > that, or do I need to first reset it to a zero offset based on the > > current machine's G53, then issue the command to set the Z offset > > from that known Z location to re- init it, then do the P1, P2 > > versions? Thanks Marcus. 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> US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS ------------------------------------------------------------------------------ Infragistics Professional Build stunning WinForms apps today! Reboot your WinForms applications with our WinForms controls. Build a bridge from your legacy apps to the future. http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
