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

    Rostock Max V3 Z-Probe Issues

    Scheduled Pinned Locked Moved
    General Discussion
    4
    21
    861
    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.
    • dc42undefined
      dc42 administrators @Phishing Fish
      last edited by

      @Phishing-Fish you can run M665 with no parameters to see what the current value is.

      Also check what coordinates DWC reports after homing. X and Y should be zero, and Z should be about 5mm lower than the current M665 H parameter, if you are using our standard homedelta.g file.

      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

      Phishing Fishundefined 1 Reply Last reply Reply Quote 0
      • Phishing Fishundefined
        Phishing Fish @dc42
        last edited by

        @dc42 M665 results: Diagonals 291.500:291.500:291.500, delta radius 142.500, homed height 200.000, bed radius 145.0, X 0.000°, Y 0.000°, Z 0.000°.

        After homing, DWC reports X and Y at zero, Z at 195. I would make my M665 H value 190 then, and see if it stops before crashing? Also, I'm unsure if I'm using the stand homedelta.g file, so I've attached it here.

        ; homedelta.g
        G91                          ; relative positioning
        G1 H1 X750 Y750 Z750 F5000   ; move all towers to the high end stopping at the end-stops (first pass)
        G1 H2 X-5 Y-5 Z-5 F5000      ; go down a few mm
        G1 H1 X10 Y10 Z10 F500       ; move all towers up once more (second pass)
        G1 Z-5 F1000                 ; move down a few mm so that the nozzle can be centered
        G90                          ; absolute positioning
        
        dc42undefined 1 Reply Last reply Reply Quote 0
        • dc42undefined
          dc42 administrators @Phishing Fish
          last edited by dc42

          @Phishing-Fish are you certain that you have the correct steps/mm set? For example, if you home the printer and then command Z to reduce by 25mm, does the effector drop 25mm?

          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

          Phishing Fishundefined 1 Reply Last reply Reply Quote 0
          • Phishing Fishundefined
            Phishing Fish @dc42
            last edited by

            @dc42 This looks like a potential issue. I brought the nozzle down to the bed and pressed the Z+25 button. Measuring it, it looks like it went up nearly 65mm. How do I go about corrected/calibrating this?

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

              @Phishing-Fish said in Rostock Max V3 Z-Probe Issues:

              How do I go about corrected/calibrating this?

              That's a pretty substantial difference. What are the motors you're using? 1.8 or 0.9 degree? Belt pitch? Idler tooth count? Microstepping?

              Z-Bot CoreXY Build | Thingiverse Profile

              Phishing Fishundefined 1 Reply Last reply Reply Quote 0
              • Phishing Fishundefined
                Phishing Fish @Phaedrux
                last edited by

                @Phaedrux Motors are Automation Technology KL17H248-15-4A. Looking at what I can find online, I couldn't find anything related to 1.8 or 0.9 degree, but I did find a step angle of 1.8° ± 5%. For belt pitch, it's 2mm. Belts can be found here: https://www.seemecnc.com/products/gt2-timing-belt. Looking at the build guide for this printer, it seems like the idlers do not have teeth and looking at my printer don't see any. For micro stepping, this is what I have in my config.g: M350 X16 Y16 Z16 E16:16 I1

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

                  @Phishing-Fish your M92 command shows 200 steps/mm. With x16 microstepping, that would be correct if the motors are 0.9 degrees and the motor pulleys have 16 teeth. If the motors are 1.8deg then it would be 100 steps/mm with 16 tooth pulleys, or 80 steps/mm with 20 tooth pulleys.

                  If the correct steps/mm for your machine is actually 80 instead of 200, that would cause a commanded 25mm movement to move 62.5mm.

                  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

                  Phishing Fishundefined 1 Reply Last reply Reply Quote 0
                  • A Former User?
                    A Former User
                    last edited by

                    This post is deleted!
                    1 Reply Last reply Reply Quote 1
                    • Phishing Fishundefined
                      Phishing Fish @dc42
                      last edited by

                      @dc42 That worked! Changing the steps/mm to 80 in config.g and now the auto-calibration stops when it hits the board. Thinking back on it now, I should have known the motors were running faster than they should have, but it never crossed my mind. To confirm, I should run the auto-calibration, then M500 to save the results in override-config.g, and then put M501 at the end of config.g, so that override-config.g is used?

                      Thank you both so much for the continued help!

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

                        @Phishing-Fish said in Rostock Max V3 Z-Probe Issues:

                        To confirm, I should run the auto-calibration, then M500 to save the results in override-config.g, and then put M501 at the end of config.g, so that override-config.g is used?

                        yes

                        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