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

2.03RC2 leveling issue

Scheduled Pinned Locked Moved
General Discussion
7
23
1.7k
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
    dc42 administrators
    last edited by 16 May 2019, 14:59

    Thanks for those files.

    What is the exact sequence you are going through that causes this issue? Is it auto calibration that causes the height shift, or G29 mesh bed probing, or both?

    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
      PaulHew
      last edited by 16 May 2019, 15:39

      I must admit I am having levelling issues also.
      Cartesian Printer. BL Touch v2, glass bed, locked bed nuts.

      I knew something was not right so I dropped the Z axis to 0 using paneldue and could get a number of sheets of paper between the nozzle and the bed.
      Went throught this procedure again. https://forum.duet3d.com/topic/10017/bl-touch-issues where I thought I had nailed the process.
      Changed the G31 P500 X-48 Y-10 Z1.28 to my new value, rebooted.
      Ran mesh level, waited for it to finish, piece of paper under the nozzle, Z axis to 0 and still a large gap.
      Re did it all again and it was still off.
      And again and it worked, maybe a little close but at least the filament is sticking!

      Was going to write a post whether it is possible to keep the BL touch as my Z but using manual bed levelling instead.

      RailCore II - Duet Mini + 1LC, Voron V0.1 - Duet Mini
      Voron 2.4 disassembled..... Waiting for the RailCore Mini....

      undefined 1 Reply Last reply 17 May 2019, 13:19 Reply Quote 0
      • undefined
        Caveman
        last edited by Caveman 16 May 2019, 20:04

        first bed level, home, then mesh level

        this works ok on 2.02 but not on 2.03

        mesh level is when this problem occurs

        undefined 1 Reply Last reply 17 May 2019, 11:31 Reply Quote 0
        • undefined
          dc42 administrators @Caveman
          last edited by 17 May 2019, 11:31

          @caveman said in 2.03RC2 leveling issue:

          first bed level, home, then mesh level

          this works ok on 2.02 but not on 2.03

          mesh level is when this problem occurs

          Your machine is a delta. When you say "first bed level", do you mean autocalibrate?

          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
            dc42 administrators
            last edited by 17 May 2019, 13:17

            @Caveman, I have tried to reproduce this issue, but failed. I have done multiple G29 bed probes, with or without homing between then, with or without a deliberate height error in the M665 command. The height map comes out the same every time I probe, apart from an offset equal to any deliberate height error I set.

            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
              dc42 administrators @PaulHew
              last edited by 17 May 2019, 13:19

              @paulhew said in 2.03RC2 leveling issue:

              I must admit I am having levelling issues also.
              Cartesian Printer. BL Touch v2, glass bed, locked bed nuts.

              I knew something was not right so I dropped the Z axis to 0 using paneldue and could get a number of sheets of paper between the nozzle and the bed.
              Went throught this procedure again. https://forum.duet3d.com/topic/10017/bl-touch-issues where I thought I had nailed the process.
              Changed the G31 P500 X-48 Y-10 Z1.28 to my new value, rebooted.
              Ran mesh level, waited for it to finish, piece of paper under the nozzle, Z axis to 0 and still a large gap.
              Re did it all again and it was still off.
              And again and it worked, maybe a little close but at least the filament is sticking!

              Was going to write a post whether it is possible to keep the BL touch as my Z but using manual bed levelling instead.

              Is this behaviour consistent when you use 2.03RC2, and absent when you revert to 2.02?

              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 17 May 2019, 19:04 Reply Quote 0
              • undefined
                PaulHew @dc42
                last edited by PaulHew 17 May 2019, 19:04

                @dc42 You asked me to use 2.03 RC1last week because of another problem.

                It has happened again, I put my borosilicate glass back on, piece of paper, jog Z to lightly grip paper, reset Z, test probing to configure G31. etc, reboot.
                Home all, move to centre, piece of paper, jog to Z0 and there is a gap again. Grrr!!
                Did not run mesh bed levelling.
                Does not seem to take on 1st second or 3rd tries.
                Rebooted everything and started afresh.

                RailCore II - Duet Mini + 1LC, Voron V0.1 - Duet Mini
                Voron 2.4 disassembled..... Waiting for the RailCore Mini....

                undefined 1 Reply Last reply 17 May 2019, 19:11 Reply Quote 0
                • undefined
                  deckingman @PaulHew
                  last edited by 17 May 2019, 19:11

                  @paulhew Are you using config.override.g by any chance? It sounds to me a bit like you have a G31 or something in there that is overriding what is in config.g.

                  Ian
                  https://somei3deas.wordpress.com/
                  https://www.youtube.com/@deckingman

                  undefined 1 Reply Last reply 17 May 2019, 19:16 Reply Quote 0
                  • undefined
                    PaulHew @deckingman
                    last edited by PaulHew 17 May 2019, 19:16

                    @deckingman said in 2.03RC2 leveling issue:

                    @paulhew Are you using config.override.g by any chance? It sounds to me a bit like you have a G31 or something in there that is overriding what is in config.g.

                    I have checked that file multiple times. I also just realised I am running RC1.
                    This is contents of my config.overide.g
                    ; This is a system-generated file - do not edit
                    ; Heater model parameters
                    M307 H0 A90.0 C700.0 D10.0 S1.00 V0.0 B1
                    M307 H1 A340.0 C140.0 D5.5 S1.00 V0.0 B0
                    M307 H2 A340.0 C140.0 D5.5 S1.00 V0.0 B0

                    Also it is not just once or twice I have had this problem, but I perfected my routine when I had the problem a few weeks ago.
                    The amount of post its with 10 sets of probe numbers is unreal!!!

                    RailCore II - Duet Mini + 1LC, Voron V0.1 - Duet Mini
                    Voron 2.4 disassembled..... Waiting for the RailCore Mini....

                    undefined 1 Reply Last reply 17 May 2019, 19:30 Reply Quote 0
                    • undefined
                      deckingman @PaulHew
                      last edited by 17 May 2019, 19:30

                      @paulhew Ahh, OK - there is nothing sinister in your config-override that might cause the issue. I suspect it must be something to do with levelliing or mesh compensation in that case, but I don't use either so can't advise. I just happened across this thread and had an idea but it isn't that.

                      Ian
                      https://somei3deas.wordpress.com/
                      https://www.youtube.com/@deckingman

                      1 Reply Last reply Reply Quote 0
                      • undefined
                        PaulHew
                        last edited by 17 May 2019, 19:32

                        Not a problem, anything to get to the bottom of this issue will be good!
                        Tempted to scrap the BL Touch and go back to Manual Mesh Bed Levelling!

                        RailCore II - Duet Mini + 1LC, Voron V0.1 - Duet Mini
                        Voron 2.4 disassembled..... Waiting for the RailCore Mini....

                        1 Reply Last reply Reply Quote 0
                        • undefined
                          Veti
                          last edited by 18 May 2019, 04:37

                          @paulhew said in 2.03RC2 leveling issue:

                          Tempted to scrap the BL Touch and go back to Manual Mesh Bed Levelling!

                          have a look at a Film Pressure Probe. they can be bought for 2 euros.

                          undefined 1 Reply Last reply 18 May 2019, 06:32 Reply Quote 0
                          • undefined
                            PaulHew @Veti
                            last edited by PaulHew 18 May 2019, 06:32

                            @veti Thats what the Two Trees Saphire uses, I think. DPT did a review and I quite like it, the printer that is. (Your not the guy behind DPT are you?)
                            Overnight I was thinking about my issue, I am pretty sure it is not the Bed Levelling routine, as I have not even got to that stage.
                            It is something in the initial setup when setting up the probe height.
                            Piece of paper etc etc, set height in the G31 command, reboot and drop nozzle to bed with paper under and at Z0 it was 0.2 - 0.3 higher. I had to disable axis limits to get it to go down.
                            Eventually it goes to where it should be after a couple of tries.

                            I do not know everything, but from your and others help I have this routine down to an art and have questioned myself if I had done it right many a time.
                            Maybe it is something to do with the BL Touch.
                            Tempted to order another BLT and see if it is that, but I am off to France on Monday for a week to sort a network out so will prob order another end of week ready for me at the weekend to try again.

                            RailCore II - Duet Mini + 1LC, Voron V0.1 - Duet Mini
                            Voron 2.4 disassembled..... Waiting for the RailCore Mini....

                            1 Reply Last reply Reply Quote 0
                            • undefined
                              dc42 administrators
                              last edited by 18 May 2019, 06:44

                              @PaulHew, do you home Z using the BLTouch or using an endstop switch?

                              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 18 May 2019, 06:58 Reply Quote 0
                              • undefined
                                PaulHew @dc42
                                last edited by 18 May 2019, 06:58

                                @dc42 Morning David, I use the BL Touch.

                                RailCore II - Duet Mini + 1LC, Voron V0.1 - Duet Mini
                                Voron 2.4 disassembled..... Waiting for the RailCore Mini....

                                1 Reply Last reply Reply Quote 0
                                • undefined
                                  PaulHew
                                  last edited by 18 May 2019, 07:03

                                  This might give you an idea how many times I tried to setup!
                                  0_1558163003226_IMG_20190518_080057.jpg

                                  RailCore II - Duet Mini + 1LC, Voron V0.1 - Duet Mini
                                  Voron 2.4 disassembled..... Waiting for the RailCore Mini....

                                  1 Reply Last reply Reply Quote 1
                                  • undefined
                                    Caveman
                                    last edited by 18 May 2019, 18:18

                                    To me this started happening since 2.03 rc1

                                    1 Reply Last reply Reply Quote 0
                                    • undefined
                                      dc42 administrators
                                      last edited by 25 May 2019, 15:00

                                      Do you use babystepping? I fixed a bug relating to babystepping and the Z offset in 2.03RC3.

                                      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
                                      15 out of 23
                                      • First post
                                        15/23
                                        Last post
                                      Unless otherwise noted, all forum content is licensed under CC-BY-SA