Store calibration results - #16
Conversation
Command TOOL_CALIBRATE_STORE_TOOL_OFFSET will save calibration result in to a file
|
Hi guys, I have been on the fence about how useful this feature is for for a while. Now that I have had a proper thought about. This might actually be pretty handy for a dynamic hardware config, like MissChanger, where the multi-tool-head hardware is designed to be quickly removable. At the moment, even if I can disconnect all the hardware in less than a minute, I will still need to manually go to the In this context, to have the data being saved in a separate file, from which I can use a script to automatically re-import into Therefore, I propose that we put what you got here, and any feature that related to data management into a separate |
|
An option that could be used is a [save_variables] file in Klipper, from each of the tool_calibrate_tool_offset call a separate macro to store and update the offsets: [save_variables] [gcode_macro save_offsets_to_disk] Then you can load them from the file at run time in a macro: And adjust your offsets from there. |
|
Same idea, but using the last_result to set Gcode macro variables (since everything in IDEX land is hacked together with macros) |
I actually totally forgot that existed. Thanks. |
|
I found it. |
Only wait if there's an actual temp change, otherwise we will be waiting for no reason.
https://github.com/joseph-greiner/klipper_tc_automatic_offset_calibration/tree/main just linking this here, supposedly this is what requested (and could be modified further as a workaround) |
use crash_gcode instead of raise gcmd.error to prevent klipper shutdown
suboptimal
…into viesturz-main
You want to calibrate Z offset with active bedmesh
Implemented a command TOOL_CALIBRATE_STORE_TOOL_OFFSET that will append results in to a txt file at printer_data/config/tools_calibrate_results/