X limit for stealthchanger/tapchanger

General Discussion
1

Basic Information:

Printer Model:
Voron 2.4 350mm
MCU / Printerboard:
Leviathan
Host / SBC
4b
klippy.log
don’t seem to have one anymore???

Describe your issue:

…
I am trying to configure tapchanger/stealthchanger and when homing, it won’t move X past 300. It will go Y 350, but won’t find X, giving a ‘no trigger after max movement’ warning. I have my limits set correctly for steppers in printer.cfg and I can’t find anything else that would be reducing this. I am using a physical X endstop, and I had to add an arm to trigger it, but it isn’t even getting close, I measured it and it is stopping at 300x300 like that is the bed size.

What should I check? Can anyone help? thank you

2

Attach your log please → How-To Ask for Help

3

klippy(15).log (5.7 MB)

4

Unfortunately, it seems this Klipper is heavily modified with 3rd party changes. Either roll back the changes and demonstarte the issue with an original Klipper or revert to the respective author of these modifications.

From a “pure” Klipper perspective the x-axis is correctly defined with a range between 0 and 350.

5

The base install of klipper is standard, I have installed a single add-on, which is KAMP, plus the necessary toolchanger software.

What modification has been made that you believe makes this unsolvable?

I might note that everything worked fine before I started modding for toolchanger. The printer worked, with this same klipper install.

6 
Untracked files: klippy/extras/bed_thermal_adjust.py, klippy/extras/multi_fan.py, klippy/extras/rounded_path.py, klippy/extras/tool.py, klippy/extras/tool_probe.py, klippy/extras/tool_probe_endstop.py, klippy/extras/toolchanger.py, klippy/extras/tools_calibrate.py
7

So you won’t help because it is a toolchanger?

8

We won’t help because some 3rd party modifications are altering Klipper’s standard behavior and we do not support 3rd party modifications.

There are basically endless such modifications somewhere in the www. Some of decent quality, some of terrible quality and a lot in between.
Unless somebody is around who is using more or less the same hardware with the same modification, we simply cannot judge

  • what they are doing
  • what the settings mean
  • if they are free of bugs
  • …
1 Like
9

I am using the good old standard stealthchanger and its instructions for toolchanger/tapchanger and nothing more than that

Look, where might I want to search for conflicts that would fool the printer into thinking the bed size is smaller during homing? Or how would I check to see what size the printer thinks the bed is? Or how might I approach troubleshooting this?

10

I am not getting past this in homing_override so I don’t think it is the macro, I tried it with and without the line I added


[homing_override]
axes: xyz
gcode:
  RESPOND TYPE=echo MSG='INITIALIZE TOOLCHANGER'
  INITIALIZE_TOOLCHANGER
  STOP_TOOL_PROBE_CRASH_DETECTION
  {% if printer.probe.last_query  %}
         RESPOND TYPE=echo MSG='Z Probe triggered, cannot home.'
  {% else %}
    SET_GCODE_OFFSET X=0.0 Y=0.0 Z=0.0
    {% set max_y = printer.configfile.config["stepper_y"]["position_max"]|float %}
    
    {% set max_x = printer.configfile.config["stepper_x"]["position_max"]|float %} # added by me
    
    {% set home_all = 'X' not in params and 'Y' not in params and 'Z' not in params %}

    {% if home_all %}
      # G90 ; absolute mode
      G28 Z
      G0 Z10 F1000
    {% endif %}

    # {% if home_all or 'X' in params %}
    {% if home_all or 'Y' in params or 'X' in params %}
      RESPOND TYPE=echo MSG='HOME Y'
      G28 Y F5000
    {% endif %}

    {% if home_all or 'X' in params %}
      RESPOND TYPE=echo MSG='HOME X MANUAL'
      G28 X F5000
    {% endif %}