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

    Bed Leveling compensates to 1.5~3.5 mm below printing surface

    Scheduled Pinned Locked Moved
    Smart effector for delta printers
    4
    18
    931
    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.
    • worekarolisundefined
      worekarolis @Veti
      last edited by

      @veti

      I haven't done any new changes as everything was working perfectly. Will have to go though that later today I guess.

      1 Reply Last reply Reply Quote 0
      • Vetiundefined
        Veti
        last edited by

        @worekarolis said in Bed Leveling compensates to 1.5~3.5 mm below printing surface:

        I haven't done any new changes as everything was working perfectly

        you wrote that you did upgrades to your delta.

        worekarolisundefined 1 Reply Last reply Reply Quote 0
        • worekarolisundefined
          worekarolis @Veti
          last edited by

          @veti
          I mean I have not done changes to configuration or structure. Just added a fan and filament sensor

          1 Reply Last reply Reply Quote 0
          • worekarolisundefined
            worekarolis @milangupta1
            last edited by

            This post is deleted!
            1 Reply Last reply Reply Quote 0
            • worekarolisundefined
              worekarolis @milangupta1
              last edited by

              @milangupta1

              There is G90 in there so no need for G92 as much as I understand

              1 Reply Last reply Reply Quote 0
              • Vetiundefined
                Veti
                last edited by

                as milangupta1 said. your bed config should look something like this (adjust for your bed)
                and the M665 and M666 should be in the config.g

                ; bed.g
                ; called to perform automatic delta calibration via G32
                ;
                ; generated by RepRapFirmware Configuration Tool v2.0.0 on Thu Aug 29 2019 14:53:59 GMT+0200 (Mitteleuropäische Sommerzeit)
                M561 ; clear any bed transform
                ; Probe the bed at 12 peripheral and 0 halfway points, and perform 6-factor auto compensation
                ; Before running this, you should have set up your Z-probe trigger height to suit your build, in the G31 command in config.g.
                G30 P0 X0 Y84.9 H0 Z-99999
                G30 P1 X42.45 Y73.53 H0 Z-99999
                G30 P2 X73.53 Y42.45 H0 Z-99999
                G30 P3 X84.9 Y0 H0 Z-99999
                G30 P4 X73.53 Y-42.45 H0 Z-99999
                G30 P5 X42.45 Y-73.53 H0 Z-99999
                G30 P6 X0 Y-84.9 H0 Z-99999
                G30 P7 X-42.45 Y-73.53 H0 Z-99999
                G30 P8 X-73.53 Y-42.45 H0 Z-99999
                G30 P9 X-84.9 Y0 H0 Z-99999
                G30 P10 X-73.53 Y42.45 H0 Z-99999
                G30 P11 X-42.45 Y73.53 H0 Z-99999
                G30 P12 X0 Y0 H0 Z-99999 S6
                ; Use S-1 for measurements only, without calculations. Use S4 for endstop heights and Z-height only. Use S6 for full 6 factors
                ; If your Z probe has significantly different trigger heights depending on XY position, adjust the H parameters in the G30 commands accordingly. The value of each H parameter should be (trigger height at that XY position) - (trigger height at centre of bed)

                worekarolisundefined 1 Reply Last reply Reply Quote 0
                • worekarolisundefined
                  worekarolis @Veti
                  last edited by

                  @veti

                  sorry, I've labeled this incorrectly. M665 and M666 are in the config overide. Correcting post.

                  1 Reply Last reply Reply Quote 0
                  • Vetiundefined
                    Veti
                    last edited by

                    are you using mesh bed compensation?
                    i.e. loading the heightmap somewhere

                    worekarolisundefined 2 Replies Last reply Reply Quote 0
                    • worekarolisundefined
                      worekarolis @Veti
                      last edited by

                      @veti

                      I've used it, but now its disabled.

                      1 Reply Last reply Reply Quote 0
                      • worekarolisundefined
                        worekarolis @Veti
                        last edited by

                        @veti

                        coud this be a problem?

                        G29 S1 ; load a previously-generated height map

                        Vetiundefined 1 Reply Last reply Reply Quote 0
                        • Vetiundefined
                          Veti @worekarolis
                          last edited by

                          @worekarolis
                          yes. loading it will change the z=0 based on the values in the heightmap.

                          worekarolisundefined 1 Reply Last reply Reply Quote 0
                          • worekarolisundefined
                            worekarolis @Veti
                            last edited by

                            @veti
                            Removing it haven't changed behavior

                            1 Reply Last reply Reply Quote 0
                            • fcwiltundefined
                              fcwilt
                              last edited by

                              Hi,

                              The trigger height setting for your Z-probe might be wrong.

                              The H parameter to M665 might be wrong.

                              Either one can result in Z=0 not being the surface of the bed.

                              Frederick

                              Printers: a E3D MS/TC setup and a RatRig Hybrid. Using Duet 3 hardware running 3.4.6

                              1 Reply Last reply Reply Quote 0
                              • worekarolisundefined
                                worekarolis
                                last edited by worekarolis

                                After updating to 2.04RC1 (2019-07-14b1) issue is gone.

                                Many thanks for your help!

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