Navigation

    Duet3D Logo

    Duet3D

    • Register
    • Login
    • Search
    • Categories
    • Tags
    • Documentation
    • Order

    Mesh leveling with BLTouch

    Tuning and tweaking
    2
    4
    559
    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.
    • mperdue
      mperdue last edited by

      I have recently upgraded a CoreXY printer by installing a Duet WiFi and Duex5. I use a BLTouch probe and have it working properly for homing. Now I’m trying to get it working with G29 for mesh compensation. After i home the machine I enter G29 and it moves to the first XY coordinate. Then it starts moving the Z axis but the probe has not been deployed. I figure I’m missing something in the configuration but I can’t figure out what it might be. Can anyone help steer me in the right direction?

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

        Either write a macro to deploy the probe, run G29 and then retract the probe; or upgrade to firmware 1.19.2. important: read the upgrade notes before you upgrade.

        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
        • mperdue
          mperdue last edited by

          The BLTouch retracts the probe as soon as it contacts the bed surface so deploying it before the G29 will only work for the first point. I’ve updated the firmware to 1.19.2 and it works the same way. This is the first time I’ve updated firmware so I’m not sure which files I need to update. I loaded the Duet WiFi firmware and the server firmware. I’m not sure what the other files are so I haven’t loaded them yet. I’m very new to the Duet world and it’s much different from Marlin. Any help would be appreciated.

          1 Reply Last reply Reply Quote 0
          • mperdue
            mperdue last edited by

            OK, that fixed it. I looked at the deployprobe.g and retractprobe.g and noticed that the M280 codes included I1 at the end. Removing these has resolved the issue.

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