Logging about klipper_estimator

[dalegaard]

Hi @paulsgale

There's no log as such, but a line is appended to the end of the file with a comment about what slicer was detected.

Are you looking for anything else in particular, that isn't already exposed in estimate or move dump modes?

Best regards,
Lasse

[pgale]

Ok thanks very much. I have it working now but another question if that's ok here?
In superslicer, is it possible to see the time estimated from klipper_estimator in the info panel? If not, what's the best way to integrate this rather than having to send it each time and wait for a print to start?

I know you can output the gcode and then run the estimator on that but is there a simpler way to do this?

Thanks.

[dalegaard]

Hi @pgale

SuperSlicer, and all other slicers as far as I'm aware, do not read back gcode after post processing and so can't show the output of the estimation. The slicers either need to change, or integrate the estimation directly. There's an open SuperSlicer issue on this, but I don't believe any progress has been made on it, or if there's even interest in it.

Best regards,
Lasse

[pgale]

Ok many thanks for clearing that up :) yes I don't expect SS to supoort that as current updates are pretty much non-existent since mid last year :(

[truckershitch]

So I have this comment at the end of my file:

; Processed by klipper_estimator v3.2.1, detected slicer PrusaSlicer 2.6.0-alpha3+linux-x64-GTK3

Could the time in seconds be added to that comment? The time could be extracted to rename the file by grep or something else. I'm unsure what program or script would do that, but the information would be there.

For example, a cron job could run periodically to check for new files in ~/gcode_files at a sane interval on the Kilpper device. That would be pretty easy to write. It probably would not catch a print job sent straight to the printer but it would catch others.

Adding the information could be optional.

[dalegaard]

Hi @truckershitch

In theory yes, but I'd prefer to keep the tool minimal. One could always use the estimate mode from a script, the run time is pretty fast even for big files so should be okay doing a couple of passes even in the worst case.

Moonraker can always extract relevant metadata from the files already, with support for multiple slicers.

Best regards
Lasse