-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[BUG] print speed does not return to 100% between prints #3374
Comments
Just edit your start or end gcode to set the 100% speed. This is not a bug, IMHO. |
I think editing gcode should be a last resort, not the "correct" way of getting a sensible behaviour Persisting the speed between prints means there's a context the user must keep track of, For me, subsequent prints are usually not related and even if they are, I think the "right way" to persist a speed setting is by configuring the print to behave that way in the slicer |
thanks, i'm adding |
This issue has been flagged as stale because it has been open for 60 days with no activity. The issue will be closed in 7 days unless someone removes the "stale" label or adds a comment. |
This issue has been closed due to lack of recent activity. |
probably a side effect of fixing #1208 (which appears to be specific to material changes)
Printer type - MK3S+
Printer firmware version - 3.10.1
SD card or USB/Octoprint
it definitely occurs with Octoprint, presumably also from SD card
Describe the bug
overriding the print speed (rotating the knob on the info screen) persists between prints
this means that when adjusting the print speed of a previous print,
the first layer of the next print will print too fast
i've had at least one instance where i compensated for a slow speed by cranking up the speed several hundred percent, and ended up with the first layer on my next print going way too fast
To Reproduce
Expected behavior
print speed to persist between material changes (don't break #1208)
and print speed to reset to 100% at the start of a print
Notes
resetting the speed between prints may bite someone when they were expecting the machine to stay slow
but that's a situation where i think i'd be more likely to go fix the speed in the slicer
some people may rely on the speed setting to persist, but it seems best for them not to, and instead fix it in the slicer
i would expect the gcode to force the printer's speed to 100% at the start, so maybe this is a slicer issue, i believe i've had this issue with prusa slicer and super slicer
The text was updated successfully, but these errors were encountered: