UltiMaker uses functional, analytical and tracking cookies. Tracking cookies enhance your experience on our website and may also collect your personal data outside of Ultimaker websites. If you agree with the use of tracking cookies, click “I agree, continue browsing”. You can withdraw your consent at any time. If you do not consent with the use of tracking cookies, click “Refuse”. You can find more information about cookies on our Privacy and Cookie Policy page.
I start my prints from a console on my PC by sending M23 and M24. That allows me to use M25 to pause a print.
Doing that leaves the nozzle in contact with the print and will always leave a scar. So I necessarily send a script to Pause the current print, move the Z up, and park the print head. The previous XYZE locations must be figured out so they can be passed along when the print is resumed so they are correct when the gcode starts flowing again.
You might be able to send "M0" or "M1" (they are both Emergency Stop) to force a pause. Depending on your firmware there may be other commands that can be used. Most pauses will result in the nozzle simply stopping right where it happens to be.
Link to post
Share on other sites
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
The full stable release of UltiMaker Cura 5.4 is here and it makes it easier than ever to remove brims and supports from your finished prints. UltiMaker S series users can also look forward to print profiles for our newest UltiMaker PET CF composite material!
Recommended Posts
GregValiant 1,110
I start my prints from a console on my PC by sending M23 and M24. That allows me to use M25 to pause a print.
Doing that leaves the nozzle in contact with the print and will always leave a scar. So I necessarily send a script to Pause the current print, move the Z up, and park the print head. The previous XYZE locations must be figured out so they can be passed along when the print is resumed so they are correct when the gcode starts flowing again.
You might be able to send "M0" or "M1" (they are both Emergency Stop) to force a pause. Depending on your firmware there may be other commands that can be used. Most pauses will result in the nozzle simply stopping right where it happens to be.
Link to post
Share on other sites