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

Delta bl touch auto leveling

Scheduled Pinned Locked Moved
Tuning and tweaking
delta bl touch auto leveling little monster
2
7
2.0k
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.
  • undefined
    Tasos
    last edited by 10 Apr 2018, 10:53

    Hello i bought duet ethernet as an upgrade for TLM ,the wiring and the first calibration of the machine was easy to complete and everything went fine.
    The problem is with bl touch and the auto-leveling ,i follow these instructions,https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe,https://betrue3d.dk/bltouch-on-duet-wifi-duetreprapfirmware/.
    .
    So the when the machine powers up bl touch is self tests and everything is ok ,even when i manually touch the bl touch it triggers.
    But when i hit the delta auto leveling in DWC the efector goes to the trigger height (set it in config.g) the bl touch pin goes down,but doesn't probe the center waits some ms and the moves to the first tower and suddenly the DWC shows the manaul bed leveling in which i have to move down the z axis until the bl touch triggers and if do that the bl touch after the first trigger goes to error mode (RED led blinks) and even if move to the next point the bl touch doesnt respond 0_1523357488108_bed.g 0_1523357491506_config.g 0_1523357494231_homedelta.g

    1 Reply Last reply Reply Quote 0
    • undefined
      dc42 administrators
      last edited by 10 Apr 2018, 13:22

      Check that you have the correct parameters in your M558 command. You should have P9 for bltouch if you are using version 1.21 firmware, or P5 for older firmware.

      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

      undefined 1 Reply Last reply 10 Apr 2018, 13:51 Reply Quote 0
      • undefined
        Tasos @dc42
        last edited by 10 Apr 2018, 13:51

        @dc42 yes all tests that i ve tried is with P9 and with P5 but the results are what i have described above

        1 Reply Last reply Reply Quote 0
        • undefined
          dc42 administrators
          last edited by 10 Apr 2018, 19:12

          Is there an error message in the GCode Console page of Duet Web Control after you run G29? There should be one, if the G29 command quit early.

          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

          undefined 1 Reply Last reply 11 Apr 2018, 07:05 Reply Quote 0
          • undefined
            Tasos @dc42
            last edited by 11 Apr 2018, 07:05

            @dc42 No i tested again the same story, nothing shows up in the console.
            I think the problem is somewhere else , my thought is why it shows me inDWC the manual bed leveling . It supposed to do itself right?.

            undefined 1 Reply Last reply 11 Apr 2018, 12:07 Reply Quote 0
            • undefined
              dc42 administrators @Tasos
              last edited by 11 Apr 2018, 12:07

              @tasos said in Delta bl touch auto leveling:

              @dc42 No i tested again the same story, nothing shows up in the console.
              I think the problem is somewhere else , my thought is why it shows me inDWC the manual bed leveling . It supposed to do itself right?.

              If it pops up the manual bed levelling prompt, then either the M558 command is not being recognised, or the probe type in it is not supported e.g. you have specified probe type 9 but you are not using version 1.21 firmware.

              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
              • undefined
                Tasos
                last edited by 13 Apr 2018, 22:57

                OK i change the P9 to P5 and also Z2 to Z1 and now works
                i run mesh and i got this

                Number of probe points: 109

                Probe area: 452.4 cm²

                Maximum deviations: -0.633 / 0.027 mm

                Mean error: -0.273 mm

                RMS error: 0.161 mm

                0_1523660226736_Capture.PNG

                I m not sure if this is right

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