Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Ultimaker
Home
+ new post
About this group
Join this group
Missing G0 code
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   6 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Boman33  
View profile  
 More options Jul 5 2012, 3:58 am
From: "Boman33" <Boma...@Vinland.com>
Date: Thu, 5 Jul 2012 03:58:12 -0400
Local: Thurs, Jul 5 2012 3:58 am
Subject: Missing G0 code
Print | Individual message | Show original | Report this message | Find messages by this author

I am amazed that the G0 code is not available since it is such a basic CNC
code.

When manually entering or editing G-code the current one is very messy since
the federate has to keep changing depending on the move type.

Normally there are just two feed commands, set the G0 once or leave it at
max travel speed and set the G1 printing speed.

Then simple:

G0 ..

G1 ..

G1 ..

G0 .

No need to keep reentering the feed rate for each.  It really would clean up
some code sections with small alternative feed type moves.

I suspect there is a chicken-egg situation.  Marlin might not accept it and
is not adding it since the slicers do not generate it.  There could be an
option in the slicers to enable G0 and Marlin ought to accept it regardless.

Bertho


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Daid  
View profile  
 More options Jul 5 2012, 4:11 am
From: Daid <daid...@gmail.com>
Date: Thu, 5 Jul 2012 01:11:01 -0700 (PDT)
Local: Thurs, Jul 5 2012 4:11 am
Subject: Re: Missing G0 code
Print | Individual message | Show original | Report this message | Find messages by this author

Marlin excepts G0 but it does exactly the same as it would with G1. Slic3r
used to have an option to generate G0 for moves, but it was removed as not
all firmwares accept this.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Boman33  
View profile  
 More options Jul 5 2012, 4:59 am
From: "Boman33" <Boma...@Vinland.com>
Date: Thu, 5 Jul 2012 04:59:05 -0400
Local: Thurs, Jul 5 2012 4:59 am
Subject: RE: Missing G0 code
Print | Individual message | Show original | Report this message | Find messages by this author

Thanks Daid for a fast reply.

What do we need to do to make Marlin work properly with G0 & G1?

(remember the two independent feed rates)

Bertho

From:  Daid  Sent: Thursday, July 05, 2012 04:11

Marlin excepts G0 but it does exactly the same as it would with G1. Slic3r
used to have an option to generate G0 for moves, but it was removed as not
all firmwares accept this.

On Thursday, July 5, 2012 9:58:12 AM UTC+2, Bertho wrote:

I am amazed that the G0 code is not available since it is such a basic CNC
code.

When manually entering or editing G-code the current one is very messy since
the federate has to keep changing depending on the move type.

Normally there are just two feed commands, set the G0 once or leave it at
max travel speed and set the G1 printing speed.

Then simple:

G0 ..

G1 ..

G1 ..

G0 .

No need to keep reentering the feed rate for each.  It really would clean up
some code sections with small alternative feed type moves.

I suspect there is a chicken-egg situation.  Marlin might not accept it and
is not adding it since the slicers do not generate it.  There could be an
option in the slicers to enable G0 and Marlin ought to accept it regardless.

Bertho

--
You received this message because you are subscribed to the Google Groups
"Ultimaker" group.

There are also forums, which are the official gathering place for Ultimaker
operators:
http://forum.ultimaker.com/

If you still want to post to this group, send email to
ultimaker@googlegroups.com
To unsubscribe from this group, send email to
ultimaker+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/ultimaker?hl=en

For information about the Ultimaker, visit: http://Ultimaker.com


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Joris [van Tubergen]  
View profile  
 More options Jul 5 2012, 6:37 am
From: "Joris [van Tubergen]" <rooiejo...@gmail.com>
Date: Thu, 5 Jul 2012 12:37:04 +0200
Local: Thurs, Jul 5 2012 6:37 am
Subject: Re: Missing G0 code
Print | Individual message | Show original | Report this message | Find messages by this author

better post this as a feature request at https://github.com/ErikZalm/Marlin/

cheers\joris


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Jelle Boomstra  
View profile  
 More options Jul 5 2012, 7:01 am
From: Jelle Boomstra <je...@protospace.nl>
Date: Thu, 5 Jul 2012 13:01:30 +0200
Local: Thurs, Jul 5 2012 7:01 am
Subject: Re: Missing G0 code
Print | Individual message | Show original | Report this message | Find messages by this author

No it is the slicers that continue this error. Some time way back when a
very silly assumption that G0 would not be needed, and other people
continued in that silly vein. Meanwhile most printer drivers and firmwares
need to jump through some hoops to recognize a G1 move that should have
been a G0.
To me this is one of those stupid traditions that keep progress down, but
unfortunately I have no clout to change it. (grumble grumble).

On Thu, Jul 5, 2012 at 12:37 PM, Joris [van Tubergen]
<rooiejo...@gmail.com>wrote:

--
*Jelle Boomstra*
Lab Manager
Stichting ProtoSpace

*Bezoekadres: Nijverheidsweg 16B, Utrecht
Postadres: Postbus 10152, 3505 AC Utrecht*
*T *+31 (0)30 223 08 75 | *E *je...@protospace.nl | *W *www.protospace.nl
*open inloop: dinsdag middag + donderdag*


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Alessandro Ranellucci  
View profile   Translate to Translated (View Original)
 More options Aug 24 2012, 2:23 pm
From: Alessandro Ranellucci <a...@primafila.net>
Date: Fri, 24 Aug 2012 11:23:28 -0700 (PDT)
Local: Fri, Aug 24 2012 2:23 pm
Subject: Re: Missing G0 code
Print | Individual message | Show original | Report this message | Find messages by this author

Daid wrote:

> Marlin excepts G0 but it does exactly the same as it would with G1. Slic3r
> used to have an option to generate G0 for moves, but it was removed as not
> all firmwares accept this.

Sorry for bringing this old thread up, but I think I would add a bit of
information here.

Slic3r emits G0 when the Mach3 profile is selected. This is because Mach3
handles G0 correctly, so we can take benefit from combining retractions,
layer changes and travel moves. When any other firmware is selected in
Slic3r, it will not emit G0 but just subsequent G1 commands. Infact,
Sprinter and Marlin handle G0 just like G1, which is wrong and doesn't
allow for such combination.

I raised this need to the kind Marlin developers, but they seem not too
interested to work on this before the new ARM electronics are out. As soon
as Marlin or any other firmware announces correct support for G0, I'll just
make the internal switch to emit such codes.

(I should add that the G0 codes can be enforced in Slic3r even by using the
--g0 command line option.)

- Alessandro


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google