On Tuesday 28 August 2018 11:24:03 Gene Heskett wrote:
> On Tuesday 28 August 2018 10:06:53 Les Newell wrote:
> > Hi Gene,
> >
> > > 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 c
Hi Gene,
Which for you are metric. I do a lot of metric, but the machine was
originally setup in inches.
No problem. Just change the G21 to G20 in toolset.ngc
Neat, but my screws limit me to on table positions, so I usually just
superglue a piece of dbl-sided pcb to some handy place near the
On Tuesday 28 August 2018 10:06:53 Les Newell wrote:
> Hi Gene,
>
> > 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 wit
Hi Gene,
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.
Yes, Homing is just es
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 b
On Monday 27 August 2018 09:49:50 Les Newell wrote:
> After a few more hours head scratching I figured out most of what is
> going on. In some cases LinuxCNC is calculating the work envelope
> incorrectly. The axis limit warnings are based on the work envelope.
> From my testing it looks like it
After a few more hours head scratching I figured out most of what is
going on. In some cases LinuxCNC is calculating the work envelope
incorrectly. The axis limit warnings are based on the work envelope.
From my testing it looks like it is sometimes messing up the tool
offsets when it does a si
I've been doing more testing on this one and there is definitely
something really odd going on here. This is some test code I am using:
N0040 G21 (Units: Metric)
N0050 G40 G90
N0120 G43 H6
N0150 G00 X2177 Y884
N0160 G01 Z50 F2000.0
N0310 M30
Ignore the odd line numbers - it has been hacked out o
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 maximu
