Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

machine_max_acceleration_retracting ignored (Marlin acceleration G-code change) #1994

Closed
guestisp opened this issue Mar 20, 2019 · 3 comments

Comments

@guestisp
Copy link

guestisp commented Mar 20, 2019

Version: 1.42.0-beta+linux64 but probably even older one.

I've set machine_max_acceleration_retracting as 1500mm/s and machine_max_acceleration_printing as 500mm/s but the generated gcode only add a single M204 P500 R1500 T500 ; sets acceleration (P, T) and retract acceleration (R), mm/sec^2

There is a little bit confusion here. The tooltip says that machine_max_acceleration_retracting is M204 T but M204 T is the travel acceleration, the retract acceleration is M204 R

So, how can I set a travel acceleration different from the retract acceleration ?
Slic3r seems to wrongly use the same value for both, regardless the tooltip.

I think a field is missing:

machine_max_acceleration_extruding is correct as M204 P
machine_max_acceleration_retracting tooltip is wrong. The proper gcode command is M204 R but M204 T is shown in tooltip
machine_max_acceleration_traveling is missing. The proper gcode command is M204 T but currently is exported with the same value as machine_max_acceleration_extruding

http://marlinfw.org/docs/gcode/M204.html

@bubnikv
Copy link
Collaborator

See #1089 for the discussion

@guestisp
Copy link
Author

Thank you. But tooltip is still wrong.

@bubnikv bubnikv changed the title machine_max_acceleration_retracting ignored machine_max_acceleration_retracting ignored (Marlin acceleration G-code change) Apr 13, 2019
@bubnikv
Copy link
Collaborator

Marlin's M204 PRT implemented in PrusaSlicer 2.4.0-alpha1 by splitting the Marlin firmware flavor to "legacy" and "Marlin 2"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants