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

Switch the gcode flavor in slicer to RepRap, it will disable machine limits. #5378

Closed
violetbp opened this issue Dec 5, 2020 · 3 comments
Closed

Comments

@violetbp
Copy link

violetbp commented Dec 5, 2020

Setting gcode to RRF hides machine limits but still seems to use them.
increasing machine max acceleration, max feedrate, and max jerk in the INI file my print time dropped.

Switch the gcode flavor in slicer to RepRap, it will disable machine limits.
Related to #1089, #1234, #3776.
Originally posted by @rtyr in #4107 (comment)

@rtyr
Copy link
Collaborator

rtyr commented Dec 5, 2020

It is now possible to disable machine limits without switching the gcode flavor (PrusaSlicer 2.3.0-beta).

ml

@rtyr
Copy link
Collaborator

rtyr commented Dec 5, 2020

Machine limits should not be used for time estimate with reprap/sprinter though.

@lukasmatena
Copy link
Collaborator

This should be fixed (9605e23) in 2.3.0-rc1. Could you please retest and close the issue if happy? Thanks.

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

No branches or pull requests

3 participants