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

    DuetWifi 1.01 Updated to 1.24 - No Z Axis after update

    Scheduled Pinned Locked Moved
    Firmware installation
    4
    24
    1.5k
    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.
    • Phaedruxundefined
      Phaedrux Moderator
      last edited by

      What does the settings page say you have installed for firmwares?

      Z-Bot CoreXY Build | Thingiverse Profile

      dirtybirdnjundefined 1 Reply Last reply Reply Quote 0
      • dirtybirdnjundefined
        dirtybirdnj @Phaedrux
        last edited by

        @phaedrux

        First off thank you so much for your help with this!

        Settings / software info

        Your G31 needs to define the X and Y offset between the probe and the nozzle.

        !!!! wow lol seems like a critical thing to be missing... measuring this now and figuring out the distance 😌

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

          Looks like you're all up to date.

          This may help with getting the probe setup: https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe#Section_Static_test_of_the_Z_probe

          Z-Bot CoreXY Build | Thingiverse Profile

          1 Reply Last reply Reply Quote 0
          • nopheadundefined
            nophead
            last edited by

            Seems like a bug if missing or incorrect probe offsets can cause the X and Y axes to crash. Once they are homed shouldn't they be limited to their defined range regardless of what G-code is executed?

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

              Did adding the X and Y parameters to G31 fix it?

              Z-Bot CoreXY Build | Thingiverse Profile

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

                @nophead said in DuetWifi 1.01 Updated to 1.24 - No Z Axis after update:

                Seems like a bug if missing or incorrect probe offsets can cause the X and Y axes to crash. Once they are homed shouldn't they be limited to their defined range regardless of what G-code is executed?

                The probe offsets default to zero; so leaving them out won't cause a crash.

                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
                • dc42undefined
                  dc42 administrators @dirtybirdnj
                  last edited by dc42

                  @dirtybirdnj said in DuetWifi 1.01 Updated to 1.24 - No Z Axis after update:

                  M558 is definiltey responding to the extra settings, but I still have to run M564 H0 to home the z-axis.

                  Do you mean you always need to run M564 H0 to home the Z axis; or only if you try to home the Z axis before X and Y have been homed?

                  When homing Z with a Z probe, the firmware won't let you do it if X and Y have not been homed first; otherwise it would probe at unknown XY coordinates.

                  Did you add the S2 parameter to the following command in homez.g as @Phaedrux said?

                  G1 Z1 F200 ; raise head 1mm to ensure it is above the Z probe trigger height

                  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

                  dirtybirdnjundefined 1 Reply Last reply Reply Quote 0
                  • dirtybirdnjundefined
                    dirtybirdnj @dc42
                    last edited by

                    @dc42

                    Do you mean you always need to run M564 H0 to home the Z axis; or only if you try to home the Z axis before X and Y have been homed?

                    Yes, this is exactly the case. Please see the screenshot above, I posted a log from the g-code console to document this.

                    Did you add the S2 parameter to the following command in homez.g as @Phaedrux said?

                    I did and the S2 allows for upward movement before the probe, but it still refuses to execute the G30 that does Z-probing unless I run M564 H0 first.

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

                      Can you try deleting the deployprobe.g and retractprobe.g files?

                      Z-Bot CoreXY Build | Thingiverse Profile

                      dirtybirdnjundefined 1 Reply Last reply Reply Quote 0
                      • dirtybirdnjundefined
                        dirtybirdnj @Phaedrux
                        last edited by

                        @phaedrux

                        Can you try deleting the deployprobe.g and retractprobe.g files?

                        THIS WORKED 🙌 The "random movements" issue has been solved! I didn't delete the files I just commented out their contents, but I'll prob remove them soon for good measure.

                        Still need to run M564 H0 before z-axis is unlocked, but I feel way more confidant about doing some test prints now that the machine is homing correctly and behaving as expected again.

                        Phaedruxundefined 2 Replies Last reply Reply Quote 0
                        • Phaedruxundefined
                          Phaedrux Moderator @dirtybirdnj
                          last edited by

                          @dirtybirdnj said in DuetWifi 1.01 Updated to 1.24 - No Z Axis after update:

                          Still need to run M564 H0 before z-axis is unlocked

                          Repost your homing files. There is a G1 move in there somewhere that needs S2.

                          Z-Bot CoreXY Build | Thingiverse Profile

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

                            @dirtybirdnj said in DuetWifi 1.01 Updated to 1.24 - No Z Axis after update:

                            I just commented out their contents

                            What did they contain?

                            Z-Bot CoreXY Build | Thingiverse Profile

                            dirtybirdnjundefined 1 Reply Last reply Reply Quote 0
                            • dirtybirdnjundefined
                              dirtybirdnj @Phaedrux
                              last edited by

                              @phaedrux said in DuetWifi 1.01 Updated to 1.24 - No Z Axis after update:

                              @dirtybirdnj said in DuetWifi 1.01 Updated to 1.24 - No Z Axis after update:

                              I just commented out their contents

                              What did they contain?

                              I copied the contents of the files over to a scratch pad before I commented them out, here they are. I don't recall setting these up so it seems like something that was on the SD card that the previous firmware didn't run / care about? Not sure... either way I am elated that I had two successful prints tonight!

                              // deployprobe.g
                              ; Probe deployment routine for Mini Kossel
                              M564 S0					; don't apply limits
                              G1 X25 Y93 Z40 F10000	; put probe arm next to belt
                              G1 X-5 F500				; move probe arm across belt
                              G1 X12 F1000			; move probe back
                              G1 X0 Y0 F10000			; move to somewhere sensible
                              M564 S1					; apply limits again
                              
                              
                              //retractprobe.g
                              ; Probe retraction routine for Mini Kossel
                              M564 S0					; don't apply limits
                              G1 Z40 F10000			; raise head
                              G1 X-59 Y66 Z35			; move over the post
                              G1 Z7 F500				; push probe down on post
                              G1 Z35 F10000			; raise head again
                              G1 X0 Y0				; move to somewhere sensible
                              M564 S1					; apply limits again
                              

                              After taking a look at these I can clearly see it's setting M564 S1 at the end of each which is prob what was causing the "axes not homed" errors! I commented out the M654 H0 in my config.g and it homes the Z with no problem now. These files also account for the "random" x+y movements that were happening with the homing process as well... mysteries solved and case closed.

                              This thread can be marked solved! Thanks again to @dc42 @Phaedrux for your help!

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

                                Glad it's all working now.

                                Z-Bot CoreXY Build | Thingiverse Profile

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