On 31 Jul 2014, at 16:14, Gene Heskett wrote:

> On Thursday 31 July 2014 08:22:34 John Thornton did opine
> And Gene did reply:
>> I think your focused on the word "calculated" and stop comprehending
>> the rest of the sentence. So let me try and word what G10 L2 and G10
>> L20 do in a different way.
>> 
>> G10 L2 P1 Z-1.5 sets the offset of G54 Z to -1.5, (which is #5223)
>> 
>> G10 L20 P1 Z0 calculates the value needed to make the current location
>> of G54 Z0
> 
> Now, if L20 p2 does that for G55, and L20 P3 does that for G56, its 
> exactly what I want.  Because I want to replace, not modify, what is there 
> in the co-ordinate system p3 represents.  So it seems I should be in G54 
> mode when making my measurements intended to update the G55 and G56 co-
> ordinates, right?
> 

Offsets are defined in relation to the absolute machine co-ordinates, but it is 
certainly useful to have a consistent reference to avoid brain-bending 
visualisation when other offsets are in play, so using G54 to set offsets is a 
good idea, I think.
But G54 is defined by offsets from the absolute machine co-ordinates, just like 
the other G55-59 co-ordinate systems.
I don't know where absolute co-ordinates live (and that's a conversation that 
has run here before, as I recall) but it doesn't matter because everything is 
relative in the G54-59 world. A bit like life...

Marcus

> But one last question, what co-ord system should I be in when I do it?  
> IOW, it won't be #5023, so perhaps I need to repeat, copying my code so it 
> only effects the top or bottom offsets?
> 
>> Lets say I jog the Z axis to absolute machine coordinate -1.5 and my
>> drill bit is just touching the top of the material. I want that point
>> to be Z0.
>> 
>> Now if I do G10 L2 P1 Z0 it sets the #5223 offset to 0, probably not
>> what I wanted. The DRO reads Z-1.5000 because I stored an offset of 0
>> in #5223.
>> 
>> Ok if I do G10 L20 P1 Z0 it calculates that it needs to set the offset
>> to -1.5 so the G54 coordinate is equal to Z0.0000 and the DRO now reads
>> 0.0000 for Z.
>> 
>> To see what your current offset is just look on the DRO tab.
>> 
>> If you break a drill bit you need to stop running code and start doing
>> "chicken checks". If I'm not 100% sure I've got an offset correct I jog
>> that axis to a position that I know what it should be and check the
>> DRO. Using coordinate systems and offsets can be confusing so take
>> your time and check, check, check.
>> 
>> It does seem to me you should be setting the tool table not the
>> coordinate system but I'm not fully sure of what your trying to do or
>> what value is in #101. Perhaps a few lines of your G code might help...
> 
> For z adjustments I thought so too, but I wasn't getting the results I 
> needed. Thinking back from my easy chair here, it may be that I wasn't 
> actually applying the offset? I'll check that as I originally was doing 
> that 18 months ago, with somewhat random results.  But now my Z is quite a 
> bit more accurate, so I'll give that another shot too.
> 
> That z code, yes, but the holefinder code which deals with X&Y locationsis 
> nearly 250 lines, many of them comments so I can decipher what I was doing 
> today, so I'll not blast the list with that.  I will do that with the 
> autoz code if I can't make it work right this time.  Currently its maybe 
> 75 LOC.  But first, snug up my X gibs, & fix the pallet and add a lost 
> recovery stanza file before I even run tholefinder, which is designed to 
> run without any machine motion other than driving it roughly to the center 
> of the contact pipe in the pallet and executing the holfinder from there.  
> Since that diddles everything but z, only tracking it internally, I think 
> executing the "lost" procedure might be a good idea.
> 
> All of this discussion has given me a better insight into what I am trying 
> to do.  Obviously there is more than one way to skin this cat, the beauty 
> of LCNC.
> 
> Thanks John.
> 
>> JT
>> 
>> On 7/31/2014 5:10 AM, Gene Heskett wrote:
>>> 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"
>> 
>> -----------------------------------------------------------------------
>> ------- 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.c
>> lktrk _______________________________________________
>> Emc-users mailing list
>> Emc-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/emc-users
> 
> 
> 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


------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to