Homing Z-Axis with BL-Touch: Pin outside bed limits

  • Hello to all!

    At first my big thank to all those who work almost day and night to help us newbies with those "strange lands"...

    Being new to Duet 2 Ethernet I´ve finished almost all setup and wiring by following the guides.
    Just one issue remained: when homing the (single) head X and Y axis home fine, but the Z-axis can´t be homed because the head isn´t far enough moved forward on the Y-axis to place the BLT pin over the bed.

    X and Y are exactly at zero pos, then the head should move to X52 and Y40 to get the pin on the first probe point (in my understanding of the highlited G1 command)

    But Y movement is only about 6mm from zero where the BLT pin still is not inside the bed dimensions!

    Probe offsets are set to X -37 and Y -25 and these values are correct in my mechanical design.
    But even when I change the Y offset to -10 or -40 in the config tool nothing changes after upload and restart!

    Firmware version is: 2.05 (2019-12-13b1)

    Attached my "homez.g" below - the same G1 command also exists in homeall.g

    ; homez.g
    ; called to home the Z axis
    ; generated by RepRapFirmware Configuration Tool v2.1.4 on Sat Dec 28 2019 23:10:10 GMT+0100 (Mitteleuropäische Normalzeit)
    G91 ; relative positioning
    G1 H2 Z5 F6000 ; lift Z relative to current position
    G90 ; absolute positioning
    G1 H2 X52 Y40 F6000 ; go to first probe point
    G30 ; home Z by probing the bed

    ; Uncomment the following lines to lift Z after probing
    ;G91 ; relative positioning
    ;G1 H2 Z5 F100 ; lift Z relative to current position
    ;G90 ; absolute positioning

    Can someone please give me a hint of what I might miss in the setup?
    I did not change anything in the gcodes as I´m just too new in this stuff, all setup was solely done in the config tool!

    Thanks a lot in advance!

  • @alexprint said in Homing Z-Axis with BL-Touch: Pin outside bed limits:

    G1 H2 X52 Y40 F6000 ; go to first probe point

    assuming you have a corexy remove the h2 part

  • This post is deleted!

  • @Veti Thank you so much, that was the solution!

    Happy new year to you! (hope I´ll be fine with the rest) 😀

Log in to reply