Estimated time longer

[BelgianGuyWithALaser]

Hi Dalegaard,

I was using this script and noticed that on my print that SS estimated 9 1/2 hours it went down to 8h 26min.

After a print I rechecked the time it needed and this was 8hours 3min

I also saw you mentioned that it should be withing 1min on a +12 hour print or it would be considered a bug.

I've printed this on a Voron V2 (if you need more info to look into this, let me know)

regards.

[dalegaard]

Hi!

Can you send a config(use the dump-config command) along with the gcode file? If you don't want it public you can send it to me at dalegaard@gmail.com. I'll take a look at what's going on! If you can send me a Klippy.log as well that would be very useful!

Thanks!

Best regards,
Lasse

[BelgianGuyWithALaser]

this is the dump config

as for the gcode, I had to zip it to upload it directly to github :
Body2.zip

and for the klippy log :
klippy.log

[dalegaard]

Hi!

Thanks for the files. Your config doesn't seem to match up with your klipper config. The config has accel and accel_to_decel at 3000, but the Klipper config has them at 5000 and 2500 respectively. If I change those in the config and re-run I get 7h56m12s.

Can you verify what settings the actual print was done with?

Best regards,
Lasse

[BelgianGuyWithALaser]

Hey,

sorry for the late reply. Yeah sorry was doing some experimenting with my acceleration/deacceleration value's. it was printed with the 3k accel , 3k deaccel.

I might have found the culptrit for the extra time, is it possible that the estimator doesn't count in my whole "start_print" macro? (QGL, nozzle heating, nozzle whipe)

Best regards,
Jordy

[dalegaard]

Hi!

The estimator counts all macros as 0 seconds, as it can't know how long they will take. Depending on when Klipper/Moonraker starts counting "Print start time" that will affect how off the result is.

Best regards,
Lasse

[dalegaard]

@BelgianGuyWithALaser

I've discovered that the time shown in the print history in Fluidd(not sure if you are using Fluidd or Mainsail) is the Total time, not the Actual print time. This means that time will include heatup and everything. From a print I just did:

Maybe this is simply what happened in your case?

Best regards,
Lasse

[dalegaard]

I'll close this for now, feel free to post any updates here and we'll re-open if relevant :)

Best regards
Lasse