-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Store calibration results #16
base: main
Are you sure you want to change the base?
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.
Implemented a command TOOL_CALIBRATE_STORE_TOOL_OFFSET that will append results in to a txt file at printer_data/config/tools_calibrate_results/