Massive overestimate of print time about klipper_estimator

[dalegaard]

Hi @FrnchFrgg

You are using absolute extrusion but klipper_estimator expects relative extrusion unless told otherwise. You can fix the issue by using relative extrusion or adding M82 in your slicer start gcode. The tool can't see M83 in your print start macro.

Best regards
Lasse

[FrnchFrgg]

I saw a bug where you told that. I checked before I filed this bug and there is an M82 in the gcode file itself.
cat spool-holder_0.2mm_PLA_Chiron_6h21m.gcode | grep M82 returns a line. So klipper_estimator should see it. Note that I also tried to put some M82 in the gcode too and that didn't change the timings.

[dalegaard]

Ah it's after the prime line. I'll take a closer look then

Best regards
Lasse

[dalegaard]

Hi @FrnchFrgg

Your klipper config file or the start of a klippy.log would be useful to help diagnose the issue. Everything looks correct on a test run.

Best regards,
Lasse

[FrnchFrgg]

config.zip

[dalegaard]

Hi @FrnchFrgg

Thanks for reporting. This was caused by the junction deviation not being updated after parsing the config. Since you have no acceleration control(like many users do) there were no commands that ever updated the value and masked the bug.

I've verified with your gcode file, taking out the macros, that Klippy and estimator now agree on the total time (20482.533s).

Best regards,
Lasse

[FrnchFrgg]

Since my acceleration settings in SuperSlicer are the same than the klipper ones I selected "for estimation only". Thanks for the quick fix.