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)
· Wrong estimated print time in Cura
Cura bases the estimate on the speed and acceleration that are entered into the Cura settings. If your printer has lower "Max Speed" and "Max Acceleration" then those become the speed limits and the time Cura estimated will be off. (It isn't usually that bad though.)
The Vyper printer definition file doesn't list the Accel numbers and so the default Cura FDMPrinter numbers are used of 3000mm/sec°. But within your printer the M201 acceleration maximum might be 500 and it's that number that will override whatever is in the gcode.
If you have PrintRun/Pronterface installed you can send M503 to the printer via the usb and see the result. It will tell you what the printer settings are. If you enter numbers at or below those limits into Cura you will find the estimate is much closer to reality.
A while back there was a post here regarding the Cura estimated print time versus the PrusaSlicer estimated print time. That turned out to be a settings issue as the poster was using a 7mm retraction distance at a speed of 1mm/sec in Cura but at 20mm/sec in PrusaSlicer. Every retraction/prime cycle was taking 14 seconds in Cura and 0.7 seconds in PrusaSlicer.
When there is an equivalency (apples and apples) between the printer settings and the Cura settings you will find that although it's not exact, it's not far off. Certainly not by a factor of 2..
Edited by GregValiant
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!
🚀 Help Shape the Future of Cura and Digital Factory – Join Our Power User Research Program!
We’re looking for active users of Cura and Digital Factory — across professional and educational use cases — to help us improve the next generation of our tools.
Our Power User Research Program kicks off with a quick 15-minute interview to learn about your setup and workflows. If selected, you’ll be invited into a small group of users who get early access to features and help us shape the future of 3D printing software.
🧪 What to Expect:
A short 15-minute kickoff interview to help us get to know you If selected, bi-monthly research sessions (15–30 minutes) where we’ll test features, review workflows, or gather feedback Occasional invites to try out early prototypes or vote on upcoming improvements
🎁 What You’ll Get:
Selected participants receive a free 1-year Studio or Classroom license Early access to new features and tools A direct voice in what we build next
👉 Interested? Please fill out this quick form
Your feedback helps us make Cura Cloud more powerful, more intuitive, and more aligned with how you actually print and manage your workflow.
Thanks for being part of the community,
The full stable release of Cura 5.10 has arrived, and it brings support for the new Ultimaker S8, as well as new materials and profiles for previously supported UltiMaker printers. Additionally, you can now control your models in Cura using a 3D SpaceMouse and more!
Recommended Posts
GregValiant 1,492
Cura bases the estimate on the speed and acceleration that are entered into the Cura settings. If your printer has lower "Max Speed" and "Max Acceleration" then those become the speed limits and the time Cura estimated will be off. (It isn't usually that bad though.)
The Vyper printer definition file doesn't list the Accel numbers and so the default Cura FDMPrinter numbers are used of 3000mm/sec°. But within your printer the M201 acceleration maximum might be 500 and it's that number that will override whatever is in the gcode.
If you have PrintRun/Pronterface installed you can send M503 to the printer via the usb and see the result. It will tell you what the printer settings are. If you enter numbers at or below those limits into Cura you will find the estimate is much closer to reality.
A while back there was a post here regarding the Cura estimated print time versus the PrusaSlicer estimated print time. That turned out to be a settings issue as the poster was using a 7mm retraction distance at a speed of 1mm/sec in Cura but at 20mm/sec in PrusaSlicer. Every retraction/prime cycle was taking 14 seconds in Cura and 0.7 seconds in PrusaSlicer.
When there is an equivalency (apples and apples) between the printer settings and the Cura settings you will find that although it's not exact, it's not far off. Certainly not by a factor of 2..
Edited by GregValiantLink to post
Share on other sites