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

    Homing issues on 2 delta printers after upgrading to 3.1.1

    Scheduled Pinned Locked Moved
    Firmware installation
    5
    36
    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.
    • sLpFhaWKundefined
      sLpFhaWK @dc42
      last edited by

      @dc42 said in Homing issues on 2 delta printers after upgrading to 3.1.1:

      @sLpFhaWK said in Homing issues on 2 delta printers after upgrading to 3.1.1:

      G1 Z-5 F6000 ; move down a few mm so that the nozzle can be centred

      If you refer to my earlier post, I suggested to @mhackney that he change that line.

      David you are correct, and I did change that and even though it worked for Michael it did not work for me.

      -sLpFhaWK
      Ultibots K250v
      Rostock Max v2 Soon to be Full MetalMax
      Mini Kossel

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

        @sLpFhaWK said in Homing issues on 2 delta printers after upgrading to 3.1.1:

        @dc42 said in Homing issues on 2 delta printers after upgrading to 3.1.1:

        @sLpFhaWK said in Homing issues on 2 delta printers after upgrading to 3.1.1:

        G1 Z-5 F6000 ; move down a few mm so that the nozzle can be centred

        If you refer to my earlier post, I suggested to @mhackney that he change that line.

        David you are correct, and I did change that and even though it worked for Michael it did not work for me.

        So why did you post the old homedelta.g instead of the modified one? How do you expect me to help you if it appears to me that you have ignored my suggestions?

        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

        sLpFhaWKundefined 1 Reply Last reply Reply Quote 0
        • sLpFhaWKundefined
          sLpFhaWK @dc42
          last edited by

          @dc42
          David, with all due respect I haven't ignored your suggestions. I am unsure why the homedelta.g I posted didn't have your change in it, at the time I copied and pasted what Michael had sent to me in a messenger chat.

          But I am also confused, is that line supposed to be in the homedelta.g twice? If you look at my original code it is in there on line 5. Do I delete line 6?

          a5333773-3c81-4fb5-9554-35f30f380351-image.png

          This is what I have now, and even now I'm not sure it's correct.

          G91                            ; relative positioning
          G1 H1 X1200 Y1200 Z1200 F2500  ; move all towers to the high end stopping at the endstops (first pass)
          G1 H2 X-6 Y-6 Z-6 F2500        ; go down a few mm
          G1 H1 X7 Y7 Z7 F360         ; move all towers up once more (second pass)
          G1 H2 X-5 Y-5 Z-5 F6000
          ; G1 Z-20 F6000                   ; move down a few mm so that the nozzle can be centred
          G90                            ; absolute positioning
          G1 X0 Y0 F6000                 ; move X+Y to the centre
          

          -sLpFhaWK
          Ultibots K250v
          Rostock Max v2 Soon to be Full MetalMax
          Mini Kossel

          1 Reply Last reply Reply Quote 0
          • mhackneyundefined
            mhackney
            last edited by

            @dc42 So, this is odd and probably related to his issue too...

            As I reported above, when I made the one line change you suggested, homing worked fine. Then I homed, jogged down in Z by 200mm and reset the Duet. Now I am getting the same error - and even odder - even issuing G28 (or clicking home) multiple times, the printer does the home cycle and then generates the target not reached error.

            Here is my homedelta.g after making your change:

            ; Homing file for RepRapFirmware on UltiBots D300VS
            G91							; use relative positioning
            G1 H1 X1000 Y1000 Z1000 F2500		; move all carriages up 1000mm, stopping at the endstops
            G1 H2 X-5 Y-5 Z-5			; move all carriages down 3mm
            
            G1 H1 X6 Y6 Z6 F250			; move carriages slowly up 6mm, stopping at the endstops
            G1 H2 X-5 Y-5 Z-5 F6000 ; move down a few mm so that the nozzle can be centred
            G90							; back to absolute positioning
            G1 X0 Y0 F2000				; center the head and set a reasonable feed rate
            

            I have not touched my scripts and after I made your change earlier today I tested homing and jogging in Z and X-Y many (>10) times with no issues. But now after a reboot it is failing.

            My 3D Printing blog: http://www.sublimelayers.com
            Coming this summer: "3D Printing Strategies - the art of perfecting your designs and prints"

            1 Reply Last reply Reply Quote 0
            • mhackneyundefined
              mhackney
              last edited by

              And removing the last 2 G1 lines as you originally requested, the error is not generated.

              My 3D Printing blog: http://www.sublimelayers.com
              Coming this summer: "3D Printing Strategies - the art of perfecting your designs and prints"

              1 Reply Last reply Reply Quote 0
              • mhackneyundefined
                mhackney
                last edited by

                I've tried lowering 15 mm in the G1 H2 line third from the bottom to give a bit more room. That fails too.

                If I only comment the last G1 X0 Y0 F2000 no error is generated but any jog move in Z generates this error:

                M120 G91 G1 Z-5 F6000 G90 M121
                Error: G0/G1: target position not reachable from current position
                

                My 3D Printing blog: http://www.sublimelayers.com
                Coming this summer: "3D Printing Strategies - the art of perfecting your designs and prints"

                1 Reply Last reply Reply Quote 0
                • Phaedruxundefined
                  Phaedrux Moderator
                  last edited by

                  I'm not really a delta guy, but from past instances of that error it was usually enough to drop all carriages in Z to resolve the error, which from what I understand means that the requested move would require one of the carriages to raise above the endstop to be reached.

                  Z-Bot CoreXY Build | Thingiverse Profile

                  1 Reply Last reply Reply Quote 0
                  • mhackneyundefined
                    mhackney
                    last edited by mhackney

                    Thanks Phaedrux. Mechanically, nothing has changed on these printers and mine are workhorses. The error message seems logical and your first post above made sense so I tried -15mm drop in Z on my machine but still getting this error.

                    It is true that a movement in XY on a delta causes at least 1 carriage to move up the tower and that does seem to be what this error message is telling us. But at 15mm down from the home switches there should be enough room for small X-Y movements. So as a test I did the final downward move to:

                    G1 H2 X-100 Y-100 Z-100 F6000 ; move down a few mm so that the nozzle can be centred

                    So now I see the home sequence, the slow descent of 100mm, then a final X-Y adjustment presumably for the M666 endstop offset adjustments and THEN the error is raised.

                    David, you asked about my M665 and M666 before, they are copied from my 2.x config.g. They seem correct. Hmm, this got me thinking, maybe my config-override.g has some bad stuff in it. I commented out the M665 and M666 in it and now homing seems to be working again. Here is what I commented out in config-override:

                    ;M665 L376.890:376.890:376.890 R209.670 H450.462 B140.0 X0.114 Y0.283 Z0.000
                    ;M666 X0.107 Y-0.648 Z0.542 A0.00 B0.00
                    

                    My 3D Printing blog: http://www.sublimelayers.com
                    Coming this summer: "3D Printing Strategies - the art of perfecting your designs and prints"

                    1 Reply Last reply Reply Quote 1
                    • mhackneyundefined
                      mhackney
                      last edited by

                      Well, nope, I am still getting the error when I change the final move from 100 back to 5mm.

                      My 3D Printing blog: http://www.sublimelayers.com
                      Coming this summer: "3D Printing Strategies - the art of perfecting your designs and prints"

                      1 Reply Last reply Reply Quote 0
                      • mhackneyundefined
                        mhackney
                        last edited by mhackney

                        Ok, maybe this will help narrow it down...

                        When I home and get this error, take a look at X Y and Z in DWC. X and Y should be 0 and Z 450.32mm.

                        Screen Shot 2020-07-14 at 4.49.00 PM.png

                        If I reset and home when the printer is "near" the home position, I get no error and the correct tool position. However, if I jog down 100mm (for example) and reset, I get this error when trying to home.

                        This is certainly an odd situation.

                        If I then do a G92 X0 Y0 Z-450 after I get the error and see the odd tool position then I can home with no errors.

                        My 3D Printing blog: http://www.sublimelayers.com
                        Coming this summer: "3D Printing Strategies - the art of perfecting your designs and prints"

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

                          @mhackney, after resetting, please run just these commands:

                          G91
                          G1 H1 X1000 Y1000 Z1000 F2500

                          and then report what XYZ coordinates are reported.

                          Also, please post the contents of config-override.g.

                          PS - you could also try deleting config-override.g to see if that fixes the problem, then recreate it (using M500) after running auto calibration.

                          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

                          sLpFhaWKundefined 1 Reply Last reply Reply Quote 0
                          • sLpFhaWKundefined
                            sLpFhaWK @dc42
                            last edited by

                            @dc42

                            So I tried this, I homed normal near my home position dropped 150mm and then reset the printer, my max home height is 452mm drops 15mm after home so everytime I reset the printer it thinks its at 437mm. After I run your commands, it stayed at the top and read 602mm and I had deleted the override file and I still got that error, without the override I got the same error even homing normally with it at it's correct height.

                            ; This is a system-generated file - do not edit
                            ; Delta parameters
                            M665 L377.470 R206.427 H451.666 B140.0 X0.252 Y0.460 Z0.000
                            M666 X0.578 Y-1.992 Z1.414 A-1.07 B-0.18
                            ; Heater model parameters
                            M307 H0 A90.0 C700.0 D10.0 S1.00 V0.0 B1
                            M307 H1 A512.9 C267.0 D9.0 S1.00 V0.0 B0
                            M307 H2 A340.0 C140.0 D5.5 S1.00 V0.0 B0
                            M307 H3 A340.0 C140.0 D5.5 S1.00 V0.0 B0
                            M307 H4 A340.0 C140.0 D5.5 S1.00 V0.0 B0
                            M307 H5 A340.0 C140.0 D5.5 S1.00 V0.0 B0
                            M307 H6 A340.0 C140.0 D5.5 S1.00 V0.0 B0
                            M307 H7 A340.0 C140.0 D5.5 S1.00 V0.0 B0
                            
                            

                            -sLpFhaWK
                            Ultibots K250v
                            Rostock Max v2 Soon to be Full MetalMax
                            Mini Kossel

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

                              Thanks, now we know why it's giving the error... but not why it thinks the height is 602mm after homing. Can you confirm that it has triggered all 3 homing switches? Confirm this by running those commands with the 3 carriages starting at different heights.

                              PS - also, please run M665 and M666 without parameters, and confirm that it reports the same values as in your M665 and M666 commands in config.g.

                              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

                              sLpFhaWKundefined 1 Reply Last reply Reply Quote 0
                              • sLpFhaWKundefined
                                sLpFhaWK @dc42
                                last edited by

                                @dc42

                                I can confirm that yes, all 3 switches are being triggered when they were all at different heights.

                                367e333a-51c7-4882-b853-a60e6941ff20-image.png

                                5926a597-6e02-422c-b7a5-5b602ed3e6f5-image.png

                                -sLpFhaWK
                                Ultibots K250v
                                Rostock Max v2 Soon to be Full MetalMax
                                Mini Kossel

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

                                  What XYZ coordinates does DWC or M114 report after running those 2 commands, with the towers starting at different heights?

                                  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

                                  sLpFhaWKundefined 1 Reply Last reply Reply Quote 0
                                  • droftartsundefined
                                    droftarts administrators @sLpFhaWK
                                    last edited by droftarts

                                    @sLpFhaWK
                                    Is this how your endstops are still set?

                                    M574 X1 S1 P"xstop"   ; X min active high endstop switch
                                    M574 Y1 S1 P"ystop"   ; Y min active high endstop switch
                                    M574 Z1 S1 P"zstop"   ; Z min active high endstop switch
                                    

                                    If so, they are set as LOW END endstops, ie when axis is at minimum, with X1, Y1 and Z1! They should be X2, Y2 and Z2.

                                    You don't appear to have an M584 command in your config.g (which sets the drive mapping). Add:

                                    M584 X0 Y1 Z2 E3                           ; Set drive mapping
                                    

                                    after the M665 and M666 lines, but before the M350 line, in your config.g. I don't think this is causing your issue, but it should be defined with RRF3.

                                    Also, might be worth setting axis limits with M208, something like:

                                    ; Axis Limits
                                    M208 Z-0.2 S1                               ; Set minimum Z
                                    

                                    Ian

                                    Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

                                    sLpFhaWKundefined 1 Reply Last reply Reply Quote 1
                                    • droftartsundefined
                                      droftarts administrators @sLpFhaWK
                                      last edited by

                                      @sLpFhaWK said in Homing issues on 2 delta printers after upgrading to 3.1.1:

                                      M350 X64 Y64 Z64 E16 I1

                                      Also, as you're using Duet 2 Wifi, you won't get interpolation (I1) with microstepping set to x64. The TMC2660 stepper drivers only provide interpolation at x16.

                                      Ian

                                      Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

                                      sLpFhaWKundefined mhackneyundefined 2 Replies Last reply Reply Quote 0
                                      • sLpFhaWKundefined
                                        sLpFhaWK @dc42
                                        last edited by

                                        @dc42

                                        This is where I started.

                                        c5daa268-d72b-46b3-896c-d9a15f69f6fd-image.png

                                        Then I'll run the 2 commands you set.

                                        G91
                                        G1 H1 X1000 Y1000 Z1000 F2500

                                        This is what I got with the M114

                                        bac0fc4d-7c51-414c-ad99-281fdd022bc8-image.png

                                        -sLpFhaWK
                                        Ultibots K250v
                                        Rostock Max v2 Soon to be Full MetalMax
                                        Mini Kossel

                                        1 Reply Last reply Reply Quote 0
                                        • sLpFhaWKundefined
                                          sLpFhaWK @droftarts
                                          last edited by

                                          @droftarts said in Homing issues on 2 delta printers after upgrading to 3.1.1:

                                          @sLpFhaWK
                                          Is this how your endstops are still set?

                                          M574 X1 S1 P"xstop"   ; X min active high endstop switch
                                          M574 Y1 S1 P"ystop"   ; Y min active high endstop switch
                                          M574 Z1 S1 P"zstop"   ; Z min active high endstop switch
                                          

                                          If so, they are set as LOW END endstops, ie when axis is at minimum, with X1, Y1 and Z1! They should be X2, Y2 and Z2.

                                          You don't appear to have an M584 command in your config.g (which sets the drive mapping). Add:

                                          M584 X0 Y1 Z2 E3                           ; Set drive mapping
                                          

                                          after the M665 and M666 lines, but before the M350 line, in your config.g. I don't think this is causing your issue, but it should be defined with RRF3.

                                          Also, might be worth setting axis limits with M208, something like:

                                          ; Axis Limits
                                          M208 Z-0.2 S1                               ; Set minimum Z
                                          

                                          Ian

                                          Ian, I haven't touched anything in the config, so if that is where you pulled the code from they are indeed unchanged.

                                          I'll add the M584 and change the XYZ from 1 to 2.

                                          Also where in the config should the m208 go?

                                          -sLpFhaWK
                                          Ultibots K250v
                                          Rostock Max v2 Soon to be Full MetalMax
                                          Mini Kossel

                                          droftartsundefined 1 Reply Last reply Reply Quote 0
                                          • sLpFhaWKundefined
                                            sLpFhaWK @droftarts
                                            last edited by

                                            @droftarts said in Homing issues on 2 delta printers after upgrading to 3.1.1:

                                            @sLpFhaWK said in Homing issues on 2 delta printers after upgrading to 3.1.1:

                                            M350 X64 Y64 Z64 E16 I1

                                            Also, as you're using Duet 2 Wifi, you won't get interpolation (I1) with microstepping set to x64. The TMC2660 stepper drivers only provide interpolation at x16.

                                            Ian

                                            Ian, so should I change the

                                            M350 X64 Y64 Z64 E16 I1

                                            to

                                            M350 X16 Y16 Z16 E16 I1

                                            or just remove

                                            M350 X64 Y64 Z64 E16

                                            I'm sorry I got help from Michael when he configured this printer for Brad, so I, and pretty much everyone else who bought one from Ultibots is running the same values.

                                            -sLpFhaWK
                                            Ultibots K250v
                                            Rostock Max v2 Soon to be Full MetalMax
                                            Mini Kossel

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