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

    Different XY speed for probing moves

    Scheduled Pinned Locked Moved
    Tuning and tweaking
    8
    30
    1.8k
    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.
    • tekkydaveundefined
      tekkydave @dc42
      last edited by

      @dc42 Cheers. I still think the Z lift speed should have it's own M558 param but I'll shut up and go away now 😛

      ~ tekkydave ~
      D-Bot: 300x300mm | Duet WiFi + Duex2 | 3 independent z motors | X,Y & Z linear rails | E3D Titan Aero + V6 | Precision Piezo z-probe
      FreeCAD, PrusaSlicer

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

        @tekkydave said in Different XY speed for probing moves:

        @dc42 Cheers. I still think the Z lift speed should have it's own M558 param but I'll shut up and go away now 😛

        Did we verify that the T parameter is actually being used for the Z lift speed?

        Or does it simply use the Z max speed from M203?

        If the Z max speed is putting on limit on the Z lift speed you, in effect, have the "missing" speed parameter from M558. Just temporarily set Z max with a M203 before you begin probing and restore it when done.

        I would test it myself if I didn't already have a two page "to-do" list that I need to attend to to get ready for summer. 😉

        Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

        tekkydaveundefined 1 Reply Last reply Reply Quote 0
        • tekkydaveundefined
          tekkydave @fcwilt
          last edited by

          @fcwilt Just tested it by changing my M558 from:

          M558 P1 C"zprobe.in" R0.25 H3 F360 T9000 A5 S0.03
          

          to

          M558 P1 C"zprobe.in" R0.25 H3 F360 T540 A5 S0.03
          

          and the lift speed went down from 10mm/s (z max speed) to 9mm/s (540mm/min)

          so yes - it is using the T param to control the Z speed.

          ~ tekkydave ~
          D-Bot: 300x300mm | Duet WiFi + Duex2 | 3 independent z motors | X,Y & Z linear rails | E3D Titan Aero + V6 | Precision Piezo z-probe
          FreeCAD, PrusaSlicer

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

            @tekkydave said in Different XY speed for probing moves:

            @fcwilt Just tested it by changing my M558 from:
            so yes - it is using the T param to control the Z speed.

            Thanks much.

            I've never encountered this issue before because I have always set my max speeds based on testing well before I get around to dealing with a probe.

            Good to know how it actually works.

            Frederick

            Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

            1 Reply Last reply Reply Quote 0
            • Nahsiroundefined
              Nahsiro @fcwilt
              last edited by

              @fcwilt I actually set all the probing move speed a lot lower when I wasn't printing a lot but it was apparent to some extent. I kinda just lived with it because it doesn't skip steps when the rods are clean and lubed. Also, things like the dive height also affected how quickly it would start to loose steps. A short dive height < 5mm worked better. And probing a single point was not as dramatic as multiple points. My max z-axis speed is probably somewhere between 600 and 700 mm/min, so depending on how much friction the threaded rods experienced, it would z probe fine or not.
              I also only truly started to investigate when I started getting "motor phase may be disconnected errors".
              I checked all the motor wires and found no issue there
              Then I started visibly seeing step lost in Z. Plus I also wanted to probe faster and be hands-off as much as possible in the pre-print process.
              Lessons learned:

              • keep threaded rod lubricated (obviously)

              • Read the fine print of my gcode commands and understand how they inter-relate

              • give myself some room around the max limits of the machine in the config.

              Thanks to you all for helping me learn a bit and solve this issue.
              Thanks @dc42 for adding the note in the documentation.
              @tekkydave I second having the z lift speed independent for probing.👍

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

                Does it really need to be a separate parameter in M558? It's got nearly a dozen as it is and it's quite easy to modify the Z max speed before and after probing. bed.g and mesh.g seem like the right place to control this and it's possible right now.

                Z-Bot CoreXY Build | Thingiverse Profile

                tekkydaveundefined 1 Reply Last reply Reply Quote 2
                • tekkydaveundefined
                  tekkydave @Phaedrux
                  last edited by

                  @phaedrux I can't disagree with the number of parameters on M558 but equally I can't understand why we have the Z lift speed being controlled by a parameter intended for XY movement.
                  In theory I could have my Z max speed set to a crazy value but it not affect any other movements as they all have their own speeds specified. Only M558 will cause issues when it tries to lift the probe at say 150mm/s.
                  Sure every printer should have it's limits set up correctly but for me it's an inconsistency in the probing process that needs looking at.

                  ~ tekkydave ~
                  D-Bot: 300x300mm | Duet WiFi + Duex2 | 3 independent z motors | X,Y & Z linear rails | E3D Titan Aero + V6 | Precision Piezo z-probe
                  FreeCAD, PrusaSlicer

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

                    @tekkydave said in Different XY speed for probing moves:

                    Only M558 will cause issues when it tries to lift the probe at say 150mm/s.
                    Sure every printer should have it's limits set up correctly but for me it's an inconsistency in the probing process that needs looking at.

                    Well I'd say if you don't have a sane limit set for Z max speed the issue will arise at some point eventually. I'll admit though I was surprised that M558 T had an effect on Z at all. I had assumed it would have just used the Z max speed as default.

                    Z-Bot CoreXY Build | Thingiverse Profile

                    gloomyandyundefined 1 Reply Last reply Reply Quote 2
                    • gloomyandyundefined
                      gloomyandy @Phaedrux
                      last edited by

                      @phaedrux I may be wrong, but doesn't the F parameter to G0/G1 apply to all axis (including Z)? Isn't the T parameter to M588 simply specifying a feedrate to be used during probe operations? If both of the previous statements are true, then I'd be surprised if T did not apply to Z.

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

                        @gloomyandy Yes. And usually the Z axis max speed would be set low enough to limit it to a safe speed in all cases so it's never really noticed.

                        Z-Bot CoreXY Build | Thingiverse Profile

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