On Monday 02 November 2020 14:58:59 Craig Hodne via Emc-users wrote:
> > Here is the code I have adapted from counterbore.py's output to try
> > and be position independent: Single stepped from MDI input
> > =
> > (counterbore sub)
> > o100 SUB
> > (SHCS Counterbore, Diameter
Here is the code I have adapted from counterbore.py's output to try and
be position independent: Single stepped from MDI input
=
(counterbore sub)
o100 SUB
(SHCS Counterbore, Diameter = 0.3900, Depth = 0.1750 )
(Number of Cuts 7, Depth of Cut 0.0250)
(Tool Diameter =
On Monday 02 November 2020 09:59:59 Stuart Stevenson wrote:
> Gene,
>
> The first thing I would try is as follows:
>
> change from
> G3 X0. Y-0.0700 Z-0.0250 J0.0700 (dies here)
> G3 X0. Y-0.0700 Z-0.0250 J0.0700
> G3 X0. Y-0.0700 Z-0.0250 J0.0700
> G3 X0. Y-0.0700 Z-0.0250
Gene,
The first thing I would try is as follows:
change from
G3 X0. Y-0.0700 Z-0.0250 J0.0700 (dies here)
G3 X0. Y-0.0700 Z-0.0250 J0.0700
G3 X0. Y-0.0700 Z-0.0250 J0.0700
G3 X0. Y-0.0700 Z-0.0250 J0.0700
G3 X0. Y-0.0700 Z-0.0250 J0.0700
G3 X0. Y-0.0700 Z-0.0250 J0.0700
On Sunday 01 November 2020 05:59:13 andy pugh wrote:
> On Sat, 31 Oct 2020 at 20:48, Gene Heskett
wrote:
> > Yes Jon, r1 does not equal r2. Gawd I wish that error window was
> > copy/pastable. The code straight out of counterbore.py has exactly
> > the same error.
>
> G90 / G91 and G90.1 /
On Sat, 31 Oct 2020 at 20:48, Gene Heskett wrote:
> Yes Jon, r1 does not equal r2. Gawd I wish that error window was
> copy/pastable. The code straight out of counterbore.py has exactly the
> same error.
G90 / G91 and G90.1 / G91.1 need to match the assumptions of the G-code.
--
atp
"A
On Saturday 31 October 2020 20:25:07 Jon Elson wrote:
> On 10/31/2020 03:46 PM, Gene Heskett wrote:
> > Yes Jon, r1 does not equal r2. Gawd I wish that error window was
> > copy/pastable. The code straight out of counterbore.py has exactly
> > the same error. Is there a newer version of it?
On 10/31/2020 03:46 PM, Gene Heskett wrote:
Yes Jon, r1 does not equal r2. Gawd I wish that error window was
copy/pastable. The code straight out of counterbore.py has exactly the
same error. Is there a newer version of it? Where?
I never use IJ arcs, but only R arcs. Saves me a LOT of
On Saturday 31 October 2020 16:46:16 Gene Heskett wrote:
> On Saturday 31 October 2020 15:53:50 Jon Elson wrote:
> > On 10/31/2020 12:01 PM, Gene Heskett wrote:
> > > G0 Z4.2500 (clear fixtures etc) (works)
> > > G0 X0. Y-0.0700 (pre-position to start a G3 move) (works)
> > > (spiral down in
On Saturday 31 October 2020 15:53:50 Jon Elson wrote:
> On 10/31/2020 12:01 PM, Gene Heskett wrote:
> > G0 Z4.2500 (clear fixtures etc) (works)
> > G0 X0. Y-0.0700 (pre-position to start a G3 move) (works)
> > (spiral down in relative, so just step z down in additive mode)
> > G91 (relative
On Saturday 31 October 2020 15:20:29 marcus.bow...@visible.eclipse.co.uk
wrote:
> Gene,
>
> I am probably barking up the wrong tree, but:
>
> As a general method, I would position the controlled point where I
> wanted the routine to begin.
> (Say at X40 Y25 Z10)
> Then I would call the
On 10/31/2020 12:01 PM, Gene Heskett wrote:
G0 Z4.2500 (clear fixtures etc) (works)
G0 X0. Y-0.0700 (pre-position to start a G3 move) (works)
(spiral down in relative, so just step z down in additive mode)
G91 (relative distance mode)
G3 X0. Y-0.0700 Z-0.0250 J0.0700 (dies here)
OK, you
Gene,
I am probably barking up the wrong tree, but:
As a general method, I would position the controlled point where I
wanted the routine to begin.
(Say at X40 Y25 Z10)
Then I would call the subroutine.
Inside the subroutine, I would use G92 to set the current position to
zero (or some other
Greetings all;
Here is the code I have adapted from counterbore.py's output to try and
be position independent: Single stepped from MDI input
=
(counterbore sub)
o100 SUB
(SHCS Counterbore, Diameter = 0.3900, Depth = 0.1750 )
(Number of Cuts 7, Depth of Cut 0.0250)
(Tool
14 matches
Mail list logo
