Time estimate way above actual time #31
Comments
|
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, |
|
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 Best regards, |
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! |
|
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, |
I wanted to test out klipper_estimator so I downloaded a few already printed gcode files and ran them through the estimate function. They all estimated longer than they actually took and some were a large amount longer. For example:
I first ran
klipper_estimator--config_moonraker_url $IP_ADDRESS dump-config > config.jsonwhich produced the following file:{ "max_velocity": 300.0, "max_acceleration": 3000.0, "max_accel_to_decel": 1500.0, "square_corner_velocity": 5.0, "instant_corner_velocity": 1.0, "move_checkers": [ { "axis_limiter": { "axis": [ 0.0, 0.0, 1.0 ], "max_velocity": 5.0, "max_accel": 100.0 } }, { "extruder_limiter": { "max_velocity": 79.82432411074329, "max_accel": 798.2432411074329 } } ] }I then ran
klipper_estimator --config_file ./config.json estimate file.gcodewhich produced the following output:The estimate command says that the print should take
1d8h23m41.648showever it actually only took21h 30m 55sto complete (superslicer predicted19h 28m 55s).Apologies if I'm doing something stupid. Is there any setup or configuration I'm missing or is this not working properly for some other reason?
Thanks!
The text was updated successfully, but these errors were encountered: