typqxq / ktc Goto Github PK

klippy.log
ktc.log

Hi,

After i home my axis with init, i want to set the default temperatures. However i seem to be getting an error.

When i leave out the CHNG_STATE=? part of the command (so for example $ KTC_TOOL_SET_TEMPERATURE TOOL=0 ACTV_TMP=200 STDB_TMP=180 STDB_TIMEOUT=1 SHTDWN_TIMEOUT=300 i dont get the error until i want to pick up a tool with T0

Let me know if you want me to change the KTC log_level2 or logfile_level4 to something else

Accidentally used an old syntax KTC_TOOL_SET_STATE based on the complete example config. Got an error that this command is unknown, because it's been updated to KTC_SET_STATE.

The main documentation is up to date, but the internal error message still suggests the old syntax.

Hi, I am working on a ratrig style toolchanger and having some issues with setting up the filament standby and active temps. Is there a guide or examples to some start_print macro or g code for the slicer to set this up?

I am setting up the temperatures like normal, but then when it does a tool change all tools are set to 0.
SET_TOOL_TEMPERATURE TOOL=1 CHNG_STATE=1

On Klipper v0.12.0-290, M104.cfg and M09.cfg throw errors on the rename_existing field.

However, removing the rename_existing field removes the error.

Did something happen to M104.1 and M109.1 commands in later releases?
Is the M104 command expecting M104.1 to be called in the macro?

This is on a fresh install of Klipper and KTC.

https://github.com/TypQxQ/KTC/blame/ed288bf0cebdd1d7cec572ee3e8f37c13e413878/macros/base/M106.cfg#L26
KTC_SET_AND_SAVE_PARTFAN_SPEED{newparameters}
Tigger error if no tools is enabled, witch stop the print many sliccer send M107 by default at begenin of the Gcode
I modified M106 to
{% if myself.selected_tool|default("none")|lower == ktc.TOOL_NONE|lower %} KTC_SET_AND_SAVE_PARTFAN_SPEED{newparameters} {% endif %}
Maybe we can send an information and not an error on KTC code

KTC_TOOL_OFFSET_SAVE is giving me somewhat unexpected behavior

Before using the command to set an offset, KTC_TOOL_OFFSET_SAVE T=0 effectively "reads" the currently stored offsets for T0.

Running KTC_TOOL_OFFSET_SAVE T=0 X=-0.438000 Y=-32.505000 Z=3.18225 sets offsets as expected.

Then, running `KTC_TOOL_OFFSET_SAVE T=1' immediately afterwards sets T1 to the XYZ offsets just used above, even though none were included with the command.

The expected behavior from my interpretation of the documentation would be to read the current offsets without setting anything. I would not expect any existing offsets to change from running the command without explicitly providing an X/Y/Z parameter to the command.