As I understand the parsing
G1z1x1y1
is the same as
g1z1
x1y1
or
g1z1x1
y1
or
g1
z1
x1
y1
I am sure that a end of line or cr/lf or any combination is not part
of the parser rules regarding a command structure. I have generated
gcode which has no line breaks in 4MB of gcode. But that runs under
Rainer Schmidt wrote:
As I understand the parsing
G1z1x1y1
is the same as
g1z1
x1y1
or
g1z1x1
y1
or
g1
z1
x1
y1
I am sure that a end of line or cr/lf or any combination is not part
of the parser rules regarding a command structure. I have generated
gcode which has no line breaks
On Sat, Jun 13, 2009 at 10:30:01AM -0400, Rainer Schmidt wrote:
As I understand the parsing
G1z1x1y1
is the same as
g1z1
x1y1
Certainly not. The first is one move. The second is two moves.
I am sure that a end of line or cr/lf or any combination is not part
of the parser rules regarding
Hi all,
It is my understanding that a rapid move (G0) should fully complete before a
subsequent motion command will start. In this case I am doing two successive
G0 moves, where in very rare occasions, the second G0 move will start to
move before the first entirely completes.
For example:
G0 X20
2009/6/12 Eric H. Johnson ejohn...@camalytics.com:
It is my understanding that a rapid move (G0) should fully complete before a
subsequent motion command will start. In this case I am doing two successive
G0 moves, where in very rare occasions,
I don't think that is necessarily true. Look at
G0 should not be used for cutting. It is only for positioning when the tool is
at safe Z height (out of workpiece and clamps etc.). I have worked with Fanuc
and Siemens controllers. In these controllers when G0 move is programmed, all
the axis used in G0 move starts moving at rapid feeds (set
On Fri, Jun 12, 2009 at 6:24 PM, Shabbir Hussains_hussai...@yahoo.com wrote:
G0 should not be used for cutting. It is only for positioning when the tool
is at safe Z height (out of workpiece and clamps etc.). I have worked with
Fanuc and Siemens controllers. In these controllers when G0 move
It seems clear to me that the described behavior is a bug. You should
file a bug report.
Ken
Rainer Schmidt wrote:
On Fri, Jun 12, 2009 at 6:24 PM, Shabbir Hussains_hussai...@yahoo.com wrote:
G0 should not be used for cutting. It is only for positioning when the tool
is at safe Z height
Yes, G0Z10 should be executed first.
Then the other move G0X5Y8
Regards,
--- On Fri, 6/12/09, Rainer Schmidt lemonn...@gmail.com wrote:
From: Rainer Schmidt lemonn...@gmail.com
Subject: Re: [Emc-users] Successive G0 moves
To: Enhanced Machine Controller (EMC) emc-users
] Successive G0 moves
Reply-To: Enhanced Machine Controller \(EMC\) emc-
us...@lists.sourceforge.net
On Fri, Jun 12, 2009 at 6:24 PM, Shabbir
Hussains_hussai...@yahoo.com wrote:
G0 should not be used for cutting. It is only for positioning when
the tool is at safe Z height (out of workpiece
Hi all,
Wait, are you sure this is a bug?
I don't know how the motion controller works in EMC2 as
far as its in-position system. I don't see any .ini
parameters listed to set in-position tolerances.
(Q: What *are* EMC2's in-position tolerance settings,
and how are they adjusted if not in the
Rainer Schmidt wrote:
On Fri, Jun 12, 2009 at 6:24 PM, Shabbir Hussains_hussai...@yahoo.com wrote:
G0 should not be used for cutting. It is only for positioning when the tool
is at safe Z height (out of workpiece and clamps etc.). I have worked with
Fanuc and Siemens controllers. In
On Fri, Jun 12, 2009 at 11:37:22AM -0400, Eric H. Johnson wrote:
my real question is, should one be able to trust that one
G0 command will complete before a subsequent G0 command starts?
EMC has always blended G0 moves. Program a square path of four
rapids, run it, and look at the backplot.
K.J. Kirwan wrote:
Hi all,
Wait, are you sure this is a bug?
I don't know how the motion controller works in EMC2 as
far as its in-position system. I don't see any .ini
parameters listed to set in-position tolerances.
(Q: What *are* EMC2's in-position tolerance settings,
and how are they
14 matches
Mail list logo
