Does not save last tool head loaded #44
Unanswered
Rneil-ca
asked this question in
Configuring
Replies: 3 comments 1 reply
|
Hi, Switched the config back to original and now it is initializing without error (think it just had to get that unknown tool out of the variables file), but I still get an error when I select the same tool. I know how to get around this with the advanced commands, but think I am still missing something as the tool is sitting in the Engaged status. states from ktc_variables: |
0 replies
|
Strange. Please attach klippy.log and ktc.log so I can backtrack. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment



Uh oh!
There was an error while loading. Please reload this page.
HI,
I think I am missing something in my config as I have been able to get everything working, but the KTC does not seem to remember which toolhead it last loaded. With this config in the init_gocde set to this:
init_gcode:
{% if myself.selected_tool|default("none")|lower == ktc.TOOL_NONE|lower %}
KTC_TOOLCHANGER_DISENGAGE TOOLCHANGER={myself.name}
KTC_SET_ACTIVE_TOOL TOOL={ktc.TOOL_NONE}
KTC_SET_STATE TOOLCHANGER={myself.name} STATE=READY
RESPOND MSG="Toolchanger {myself.name} initialized unlocked, without tool"
{% else %}
KTC_TOOLCHANGER_ENGAGE TOOLCHANGER={myself.name} IGNORE_ENGAGED=True
RESPOND MSG="Toolchanger {myself.name} initialized with tool {myself.selected_tool}"
{% endif %}
I get the following error:
Unknown tool already mounted.Can't automatically deselect unknown tool before selecting new tool.
I have been able to get the KTC to work with the following init_gcode:
init_gcode:
KTC_TOOLCHANGER_DISENGAGE TOOLCHANGER={myself.name}
KTC_SET_ACTIVE_TOOL TOOL={ktc.TOOL_NONE}
KTC_SET_STATE TOOLCHANGER={myself.name} STATE=READY
RESPOND MSG="Toolchanger {myself.name} initialized unlocked, without tool"
So I figure I am missing something somewhere but have look through all the documentation and example configs and can not figure out what I am missing.
Thank you for all your hard work on this project!
Ryan
All reactions