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!
Here comes Cura 5.9 and in this stable release we have lots of material and printer profiles for UltiMaker printers, including the newly released Sketch Sprint. Additionally, scarf seams have been introduced alongside even more print settings and improvements. Check out the rest of this article to find out the details on all of that and more
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
GregValiant 1,408
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