Estimated Time remaining way longer than actual
 
Notifications
Clear all

Estimated Time remaining way longer than actual  

  RSS
Animu
(@animu)
New Member
Estimated Time remaining way longer than actual

My prusa slicer keeps estimating the remaining time way longer than it is actually. Like it says a 15 min print will take 3hr, it says a 1.5day print will take 9days etc. 

The printer also shows this exaggerated time remaining, and the minutes count down every few sec. This is also not printer specific, all 4 of my prusas show the long time.

How do I fix this? Prusa Slicer 2.2.0

Thanks

Below is what a 1.5day print showed as time remaining


 

Best Answer by Neophyl:

Its your firmware flavor choice.  Under your print settings if you change your firmware type to Marlin another section appears, these are your machine limits.  Slicer uses those limits in there to work out its print time estimate.  With marlin selected and no changes to the values it estimated approx~ 1d 1h.  With Reprap/Sprinter flavor it doesn't have these values so is probably using some wildly conservative internal values or maybe they aren't initialized so you get a crazy long estimate.

Nothing you can do about it in 2.2  However you are in luck.  The 2.3 versions currently in alpha and about to go to beta has different stuff for machine limits.  For example on Marlin you can choose to emit the limits to the gcode or just use them for the time estimate.

I loaded your project into 2.3.0-alpha3 and sliced it, the estimate was 1d 57m so it looks like its using some different internal ones that are better.  I still didn't see any way of adjusting the limits its using for time estimate except when using Marlin.

I also loaded it into Super Slicer (which is a fork of Prusa Slicer and has LOADS more options you can tweak).  The estimate right off the bat was 1d 12h 3m which sounds a lot more like your day and a half actual.  That has similar options for include in gcode (and so override the printer), use for time estimate or do nothing with them.  At least with Super Slicer (SuSie) the machine limits section is available under Reprap/Sprinter so you could read out the actual limits from your machine settings, plug them into the machine limits section so they match and then select use for time estimate.  That should give you the best shot at an accurate estimate.

If you do want to try SuSie its at https://github.com/supermerill/SuperSlicer/releases/tag/2.2.53.4   (the latest stable version)  the 2.2.54.x versions are currently being merged with Prusa Slicer alphas so they are a bit unstable as the PS alphas arent without issues.  Good for experimenting though 🙂

Super Slicer doesnt hold your hand as much as PS and a lot more of the settings are exposed to the user.  Basically a lot of the things people have been crying out for in PS get implemented in SuSie as unlike PS the developer doesn't have to worry about all the normal users that require a massive amount more consideration before it gets done.  

Posted : 24/11/2020 8:15 pm
Neophyl
(@neophyl)
Illustrious Member
RE: Estimated Time remaining way longer than actual

Please save one of your projects that suffers from the problem (file>save as) and then take the resulting .3mf file and zip it up and then attach the zip file here on a reply post.

With the project we can see all the settings you are using for your print, filament and printer profiles.  We should be able to duplicate your exact slice conditions which makes it much much easier to debug these sorts of issues.

Posted : 24/11/2020 9:20 pm
Animu
(@animu)
New Member
Topic starter answered:
RE: Estimated Time remaining way longer than actual

@neophyl

too long

https://forum.prusa3d.com/wp-content/uploads/2020/11/too-long.zip  

Attached is the zipped .3mf

It has been going on for ~6 months. It does not seem to be any print settings that effect it. (At least obviously)

thanks

This post was modified 3 years ago by Animu
Posted : 24/11/2020 9:50 pm
Neophyl
(@neophyl)
Illustrious Member
RE: Estimated Time remaining way longer than actual

Its your firmware flavor choice.  Under your print settings if you change your firmware type to Marlin another section appears, these are your machine limits.  Slicer uses those limits in there to work out its print time estimate.  With marlin selected and no changes to the values it estimated approx~ 1d 1h.  With Reprap/Sprinter flavor it doesn't have these values so is probably using some wildly conservative internal values or maybe they aren't initialized so you get a crazy long estimate.

Nothing you can do about it in 2.2  However you are in luck.  The 2.3 versions currently in alpha and about to go to beta has different stuff for machine limits.  For example on Marlin you can choose to emit the limits to the gcode or just use them for the time estimate.

I loaded your project into 2.3.0-alpha3 and sliced it, the estimate was 1d 57m so it looks like its using some different internal ones that are better.  I still didn't see any way of adjusting the limits its using for time estimate except when using Marlin.

I also loaded it into Super Slicer (which is a fork of Prusa Slicer and has LOADS more options you can tweak).  The estimate right off the bat was 1d 12h 3m which sounds a lot more like your day and a half actual.  That has similar options for include in gcode (and so override the printer), use for time estimate or do nothing with them.  At least with Super Slicer (SuSie) the machine limits section is available under Reprap/Sprinter so you could read out the actual limits from your machine settings, plug them into the machine limits section so they match and then select use for time estimate.  That should give you the best shot at an accurate estimate.

If you do want to try SuSie its at https://github.com/supermerill/SuperSlicer/releases/tag/2.2.53.4   (the latest stable version)  the 2.2.54.x versions are currently being merged with Prusa Slicer alphas so they are a bit unstable as the PS alphas arent without issues.  Good for experimenting though 🙂

Super Slicer doesnt hold your hand as much as PS and a lot more of the settings are exposed to the user.  Basically a lot of the things people have been crying out for in PS get implemented in SuSie as unlike PS the developer doesn't have to worry about all the normal users that require a massive amount more consideration before it gets done.  

Posted : 24/11/2020 11:57 pm
Animu liked
Share: