Time estimate way above actual time about klipper_estimator HOT 4 CLOSED

Hi @WolfeCub

Your process looks correct. Can you attach a gcode file for testing?

Generally discrepancies like this are caused by macro usage. The tool does not emulate macros.

Best regards,
Lasse

from klipper_estimator.

Now that I look closer at the data, I think you are probably using absolute extrusion coordinates?

The tool defaults to assuming relative coordinates, which is different from klipper itself. I need to document why this is, but the solution is to either use relative coordinates in your slicer or include M82 in your slicer start gcode.

Best regards,
Lasse

from klipper_estimator.

I think you are probably using absolute extrusion coordinates?

Aha! Good eye. I manually edited the gcode and ran it again and it was 5 minutes shy of the actual time which adding in heat up and probing I would say is dead on.

I see where this went wrong now. My M82 command is in my start macro which the tool has no way of seeing inside and I guess superslicer doesn't emit M82 even if the relative extrusion box is unchecked. Is there a flag I can use to force it to use absolute positioning or should I just have my slicer emit an extra M82 before my start macro?

Thanks!

from klipper_estimator.

At this point there's no option, but you are not the first to get bit by this and you won't be the last, so I'll see what I can do potentially to make this easier going forward, if nothing else documenting it.

Best regards,
Lasse

from klipper_estimator.