On Friday 24 August 2018 17:39:50 Les Newell wrote:

> I have another issue that I think others have seen as well. Quite
> often when I run a program on my router I get a warning that the Z
> axis maximum limit will be exceeded. The code runs fine if I ignore
> the warning. The warning appears to be triggered by G53 G0Z0 at the
> end of the code. My maximum limit is Z1, minimum something like -200.
>
> Does anyone have any ideas of what is going on? As a workaround is
> there any way to tell Axis to never show this warning?
>
> Les
>
I think I may not have 100% grokked the z axis homing or tool setup.

Scenario:

Z home switch trips about 50 thou below top of post and offsets are 
supposedly from there in the rest of my homing setup,mainly  because I 
don't care for -z's in my code.

But homing does not apply a TLO, which can vary by 7 or 8 inches 
according to whats in this spindle for a tool at the time with this 
machine. So when I calculate the min limit, I'm effectively putting the 
spindle with no tool in it, about 25 thou from the table. With an r8 
spindle and er20 TTS holders, or a 5/8" drill chuck and drill, there 
simply is no way to achieve a consisten TLO measurement without finding 
the length with a g38.2 and writing that offset into the tool table, 
valid until the collet is loosened or if the drill is changed.

What I have been doing is feeding that offset into the co-ord map, which 
is not a fixed offset from the g53 g0 x0y0z0 mapping.  Since we do have 
an gcode editable tool.tbl, my present method is wrong, grossly so at 
times.

So the question, since theres no z probition in a G10L1, does a z offset 
applied that way, actually get into the tool.tbl for use as TLO with a 
G43 H? Looking at the Doc pdf, it does not say...

If so, then how can I save myself from the inevitable fubar by having an 
invalid flag applied to that H when a tool change is requested, making 
LCNC spit out an error indicating that the new tool is to be measured 
before first use. For me that might be a time killer, but I don't see a 
way around it. Perhaps zero that H, and use it for an error flag? That 
of course won't work if the g53 and the coord in use are not synched.

So I'm open to suggestions on how to proceed. My table has enough scars 
now.

> ----------------------------------------------------------------------
>-------- 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
> 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>

------------------------------------------------------------------------------
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
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to