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.
Posted
(edited)
· Cura 2.3.1 time prediction on UM2+ display
OctoPrint does the same thing. It just takes the amount time taken to process the gcode data so far and estimates the time left based on amount of data left to process.
Rafts print a lot slower and are mostly straight lines (very little gcode commands printing very slowly), so it thinks to process the rest of the print will be just as slow.
After the rafts are done, print speeds up and commands become more frequent and complex, so the printer chews through them faster and the time estimate drops.
Edited by Guest
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!
In the Cura 5.8 stable release, everyone can now tune their Z seams to look better than ever. Method series users get access to new material profiles, and the base Method model now has a printer profile, meaning the whole Method series is now supported in Cura!
We are happy to announce the next evolution in the UltiMaker 3D printer lineup: the UltiMaker Factor 4 industrial-grade 3D printer, designed to take manufacturing to new levels of efficiency and reliability. Factor 4 is an end-to-end 3D printing solution for light industrial applications
Recommended Posts
DaHai8 74
OctoPrint does the same thing. It just takes the amount time taken to process the gcode data so far and estimates the time left based on amount of data left to process.
Rafts print a lot slower and are mostly straight lines (very little gcode commands printing very slowly), so it thinks to process the rest of the print will be just as slow.
After the rafts are done, print speeds up and commands become more frequent and complex, so the printer chews through them faster and the time estimate drops.
Edited by GuestLink to post
Share on other sites