TEST_SPEED Sending X Axis past Set Maximum

[bailboy91]

When using TEST_SPEED after the initial homing of axis the macro will move Y to 214 (215 is configured max in printer.cfg) and then the macro attempts to send X to 368 (configured max in printer.cfg is 245)

I cannot make heads or tails as to where in the macro it is getting well X move well beyond my maximum. I have attempted to hard code X min and max with no luck. Other than the macro crashing the tool head in an attempt to go past X Max the macro performs as intended.

[AndrewEllis93]

Can you provide your klippy.log please?

[bailboy91]

I just noticed after rebooting the pi and the printer. After the initial homing of X Y Z, the macro no longer homes X. It will Home Y and Z again but never X.

Google drive of klippy.log
https://drive.google.com/file/d/1YeMZod5MTXLPLT6-bnWtsJVyd8uozrtz/view?usp=sharing

[ethanjgibbs]

I have had the same issue running the macro on a V0.2 with senseless homing. The sensorless homing macro was changing the positioning mode and the test speed macro did not change it back. That would account for the difference in the coord calculation, and the macro asking for an out of bounds move. This was my log for the issue.

klippy-4.log

[HelloThisIsFlo]

I had the same issue (SV06, sensorless homing). Thanks to you @ethanjgibbs I was able to pay close attention to what's happening around the G28.

And, for me, the fix was simply to add a M400 (wait for current moves to finish) before the last 2 G28 (this one and this one)

[nanokatz]

I had the same issue (SV06, sensorless homing). Thanks to you @ethanjgibbs I was able to pay close attention to what's happening around the G28.

And, for me, the fix was simply to add a M400 (wait for current moves to finish) before the last 2 G28 (this one and this one)

This worked for me as well. Thank you!

[Joebus1]

I had the same issue (SV06, sensorless homing). Thanks to you @ethanjgibbs I was able to pay close attention to what's happening around the G28.

And, for me, the fix was simply to add a M400 (wait for current moves to finish) before the last 2 G28 (this one and this one)

Hi, I added the M400 in just before the two G28s and it will still move out of bounds. "
klippy (4).log
Move out of range: 229.000 229.000 5.000 [0.000]"

This is on a voron0.2

[alexstone]

And, for me, the fix was simply to add a M400 (wait for current moves to finish) before the last 2 G28 (this one and this one)

@HelloThisIsFlo's suggestion worked for me, too. THANK YOU! 🥳

[Joebus1]

And, for me, the fix was simply to add a M400 (wait for current moves to finish) before the last 2 G28 (this one and this one)

@HelloThisIsFlo's suggestion worked for me, too. THANK YOU! 🥳

Are you using a Voron 0.2?

[alexstone]

@Joebus1 No. Custom build machine using sensorless homing.

[Joebus1]

@alexstone Ok, thank you. I only ask because even with the fixes above I still receive the same error on my Voron 0.2. I need to double check the rest of my config.

[AndrewEllis93]

@Joebus1
Your _HOME_X and _HOME_Y macros (called by G28 with your homing_override) set G91 (relative positioning mode) and do not set it back. The TEST_SPEED macro sets G90 but then your homing override changes it.
Try throwing a G90 after each G28. Ideally your homing macros should save/restore state or at least set the positioning mode back to what it was before.
I will add those as a foolproofing measure.
I'm not 100% sure here, looks like your _HOME_Z sets G90, but worth a try.

Hmm actually my memory was wrong, the macro already sets G90 after each G28. Still reading over your log here

[the1snm]

I was having the same issues with my V0.2 as @Joebus1 mentioned and looked at the macro I downloaded a short while ago. I saw in the homing section the G90 you mentioned after the first homing but not after the 2nd one. I inserted G90 after the 2nd G28 X Y and everything worked for me after that. For anyone else reading in with the same problem this is the line I'm talking about it's 4th from the bottom.

# Home and get position for comparison later:
    M400 # Finish moves - https://github.com/AndrewEllis93/Print-Tuning-Guide/issues/66
    G28
    # QGL if not already QGLd (only if QGL section exists in config)
    {% if printer.configfile.settings.quad_gantry_level %}
        {% if printer.quad_gantry_level.applied == False %}
            QUAD_GANTRY_LEVEL
            G28 Z
        {% endif %}
    {% endif %} 
    # Move 50mm away from max position and home again (to help with hall effect endstop accuracy - https://github.com/AndrewEllis93/Print-Tuning-Guide/issues/24)
    G90
    G1 X{printer.toolhead.axis_maximum.x-50} Y{printer.toolhead.axis_maximum.y-50} F{30*60}
    M400 # Finish moves - https://github.com/AndrewEllis93/Print-Tuning-Guide/issues/66
    G28 X Y
    G90     #<-----added this line
    G0 X{printer.toolhead.axis_maximum.x-1} Y{printer.toolhead.axis_maximum.y-1} F{30*60}
    G4 P1000 
    GET_POSITION

[Mazaka2018]

I was having the same issues with my V0.2 as @Joebus1 mentioned and looked at the macro I downloaded a short while ago. I saw in the homing section the G90 you mentioned after the first homing but not after the 2nd one. I inserted G90 after the 2nd G28 X Y and everything worked for me after that. For anyone else reading in with the same problem this is the line I'm talking about it's 4th from the bottom.

# Home and get position for comparison later:
    M400 # Finish moves - https://github.com/AndrewEllis93/Print-Tuning-Guide/issues/66
    G28
    # QGL if not already QGLd (only if QGL section exists in config)
    {% if printer.configfile.settings.quad_gantry_level %}
        {% if printer.quad_gantry_level.applied == False %}
            QUAD_GANTRY_LEVEL
            G28 Z
        {% endif %}
    {% endif %} 
    # Move 50mm away from max position and home again (to help with hall effect endstop accuracy - https://github.com/AndrewEllis93/Print-Tuning-Guide/issues/24)
    G90
    G1 X{printer.toolhead.axis_maximum.x-50} Y{printer.toolhead.axis_maximum.y-50} F{30*60}
    M400 # Finish moves - https://github.com/AndrewEllis93/Print-Tuning-Guide/issues/66
    G28 X Y
    G90     #<-----added this line
    G0 X{printer.toolhead.axis_maximum.x-1} Y{printer.toolhead.axis_maximum.y-1} F{30*60}
    G4 P1000 
    GET_POSITION

Without the G90, I was getting "Move out of range: 684.000 684.000 4.000 [0.000]" on my Voron 2.4 after removing my sensors and setting up sensorless. I used the manual found on Eric's git: https://github.com/EricZimmerman/VoronTools/blob/main/Sensorless.md
After adding the G90 all works well again. Thanks!