Jump to content
twue

CURA 3.3.1 GCode Flavour - Wrong Acceleration

Recommended Posts

Posted · CURA 3.3.1 GCode Flavour - Wrong Acceleration

Hallo,

 

I used Cura 3.3.1 to generate gcode to use on a Creality CR-10 S5 and ran into massive problems with slipping layers mainly on y-axis.

After a long research I found this threat about the wrong gcode flavour of Cura in older versions:

http://www.crforums.com/showthread.php/50-Using-Cura-along-with-the-updated-Marlin-firmware

 

Apparently the gcode in Version 3.3.1 inserts very high travel acceleration and jerk by default like this:

M204 S5000
M205 X30 Y30

 

As far as I understand is the Marlin firmware expecting the gcode as following so it cannot use the M204 but the M205:

M204 [P<accel>] [R<accel>] [T<accel>]

M205 [B<µs>] [E<jerk>] [S<feedrate>] [T<feedrate>] [X<jerk>] [Y<jerk>] [Z<jerk>]

 

So I am not so sure what's happening with the acceleration or if its not used so just the jerk causes the slipping.

Anyways I rolled back to Cura 2.7 in which M204/M205 is not used by default but changing feed rates for the movements. No slipping, everythings prints fine!

 

My question if there is a way to set in preferences max jerk and acceleration for the printer so that I don't have to open all the speed parameters.

The question is also how to bring the M204 in the right flavour so that Marlin will understand what’s happening?

 

Cheers

Tom

Share this post


Link to post
Share on other sites
Posted · CURA 3.3.1 GCode Flavour - Wrong Acceleration

Hello @twue,

 

To change the default values for jerk/acceleration you can either edit the printer definition file and add entries to the override section or, even easier, install the new printer settings plugin that was recently announced on this forum and set the accel/jerk in there.

As regards to M204, Marlin has changed its implementation of M204 (see http://reprap.org/wiki/G-code#M204:_Set_default_acceleration)

Cura supports the earlier implementation that uses S and T params.

 

Hope this helps.

  • Like 1

Share this post


Link to post
Share on other sites
Posted · CURA 3.3.1 GCode Flavour - Wrong Acceleration

Hi smartavionics,

 

thanks for your reply.

I installed the Printer Settings plugin but I could not change the parameters, they always switched back to the preset numbers which are far out of range...

image.thumb.png.1272e29951a988dceffa117256637446.png

 

Where can I find the printer definition file you mentioned?

 

The main question is still why does the M204 gcode command does not translate right when Cura is set to marlin flavour and the change is three years old!?

http://reprap.org/wiki/G-code#M204:_Set_default_acceleration

"Marlin notes: After Mar11-2015, the M204 options have changed in Marlin:

P = Printing moves

R = Retract only (no X, Y, Z) moves

T = Travel (non printing) moves"

 

Please let me know if I am wrong in this case but I think it would be great if the gcode translation would be implemented right in Cura so that the commands work as aspected.

 

Cheers

tom

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Our picks

    • Ultimaker Cura 4.0 | Stable available!
      Ultimaker Cura 4.0 is mainly focused on the improved user interface and cloud integration.
      As always, we want to collect your user feedback for this release. If there are any improvements you can think of, feel free to mention it here and help us to shape the next release.
      • 87 replies
×
×
  • Create New...

Important Information

Welcome to the Ultimaker Community of 3D printing experts. Visit the following links to read more about our Terms of Use or our Privacy Policy. Thank you!