Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    Issues with G32

    Scheduled Pinned Locked Moved
    General Discussion
    2
    3
    925
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • copystringundefined
      copystring
      last edited by

      Hi.
      Usually I try to solve issues myself however with this one I'm at a loss.
      I have a Hypercube Evolution with a duet wifi and created my configuration with the configurator (https://configurator.reprapfirmware.org/).

      Now the issue I have.
      When I home all axis and then enter G1Z0 in the gcode console the nozzle touches the bed just fine since I have configured the Y offset for the BL Touch just fine.
      However, the moment I run G32 the nozzle does not touch the bed anymore after G1Z0. Instead it is way above the bed at about the distance between the bed and the created plane/mesh (this also seems to happen with G29).
      I will attach my config below.

      Not sure what to do anymore. I have read the following topics about probing and followed the instructions and set the offset between the BL Touch and nozzle correctly (since it works before G32):
      https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe
      https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_BLTouch

      My goal is to use two independent z motors to level the bed before every print.
      For that I successfully used this guide: https://duet3d.dozuki.com/Wiki/Bed_levelling_using_multiple_independent_Z_motors

      0_1524933022596_Auto compensation.jpg
      0_1524933051791_Mesh.jpg
      12_1524933365731_tpre0.g 11_1524933365731_tpost0.g 10_1524933365731_tfree0.g 9_1524933365731_stop.g 8_1524933365731_sleep.g 7_1524933365731_resume.g 6_1524933365731_pause.g 5_1524933365731_homez.g 4_1524933365731_homey.g 3_1524933365731_homex.g 2_1524933365731_homeall.g 1_1524933365731_config.g 0_1524933365731_bed.g

      1 Reply Last reply Reply Quote 0
      • dc42undefined
        dc42 administrators
        last edited by

        You haven't set the bltouch trigger height in the G31 command. Also, if you are Z homing using the bltouch, you should use a G30 command, not a G1 S1 command. See https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareCartesianPrinter#Section_Homing_Z and https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe.

        Duet WiFi hardware designer and firmware engineer
        Please do not ask me for Duet support via PM or email, use the forum
        http://www.escher3d.com, https://miscsolutions.wordpress.com

        1 Reply Last reply Reply Quote 0
        • copystringundefined
          copystring
          last edited by

          Yes. That is what it was.
          I guess sometimes it helps when somebody else looks over it after being on it for too long 🙂
          Thank you!

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Unless otherwise noted, all forum content is licensed under CC-BY-SA