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

    Probing speed tied to X position

    Scheduled Pinned Locked Moved Unsolved
    Duet Hardware and wiring
    3
    23
    842
    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.
    • JoergS5undefined
      JoergS5 @KP0005
      last edited by JoergS5

      @Matej101 what is also important is the homeall file, please post it.

      While your printer probes, please make a M122 and post this also. This is a reporting tool and if there are serious errors, M122 will show it.

      The general recommendation is to use RRF 3.1.1, because it fixes some problems since 3.01 RC12.

      You have a lot of specific M569 settings for the steppers. To exclude them from a possible reason, you can try removing the specific settings for a test whether the strange behaviour still happen. Is there a reason for using this specific parameters?

      I don't understand the S2 parameter in bed:
      G30 P2 X225 Y95.5 Z-99999 S2
      I cannot find documentation for it, I would remove it. And the X coordinate may be outside or very near the edge of the bed for the probe, because 225 + G31 X offset of 23 is near the M208 X upper limit. If this point is where the probe is fast, I suspect it is fast because the probing doesn't work at this point. But please test removing S2 and setting X a bit lower to test this theory.

      I found a thread about Prinda: https://forum.duet3d.com/topic/13219/rrf-support-for-pinda-probe/3 it mentions temparature correction in G31, but I don't understand this comment, but maybe you know what to configure. (last comment from dc42)

      1 Reply Last reply Reply Quote 0
      • KP0005undefined
        KP0005
        last edited by

        video of the issue: https://photos.app.goo.gl/X2tRCxf1cV6RoKR86

        the individual probe moves in bed.g are for gantry levelling (my z axis has two steppers with leadscrews connected to independent drivers). I thought the S2 parameter was for applying the levelling, I found it on the dozuki.

        my probe is the v1 PINDA, later revisions have a built in thermistor for temperature conpensation.

        1 Reply Last reply Reply Quote 0
        • KP0005undefined
          KP0005
          last edited by

          both firmware and dwc should be on 3.1.1

          JoergS5undefined 1 Reply Last reply Reply Quote 0
          • JoergS5undefined
            JoergS5 @KP0005
            last edited by

            @Matej101 On you video I see only one move down at the right position, is this correct? (video ends after moving one time down).

            Can you please tell me the link where you found S2, I cannot find it.

            KP0005undefined 1 Reply Last reply Reply Quote 0
            • KP0005undefined
              KP0005 @JoergS5
              last edited by

              @JoergS5 no, on my side the video show the entire bed probing process (probe left side, center, right side of the bed, than apply bed tilt correction, than probe the bed on a 5x5 grid)

              I found the S2 here: https://duet3d.dozuki.com/Wiki/Bed_levelling_using_multiple_independent_Z_motors

              1 Reply Last reply Reply Quote 0
              • KP0005undefined
                KP0005
                last edited by

                Well...
                I just started a print and the issue just isn't there. What? Why? I don't understand...

                JoergS5undefined 1 Reply Last reply Reply Quote 0
                • JoergS5undefined
                  JoergS5 @KP0005
                  last edited by JoergS5

                  @Matej101 funny!

                  Thanks for the link, I was not aware of the S2 parameter, it is not mentioned in the common G-Code page. I can see the whole video now also, I made the mistake of viewing the preview only...

                  So it's working now? Don't change anything now... (serious: make a backup and if it reappears after changes, compare the configuration). Maybe it was the update to 3.1.1

                  1 Reply Last reply Reply Quote 0
                  • KP0005undefined
                    KP0005
                    last edited by KP0005

                    The thing is, I didn't change anything. I just turned the printer off, went outside for a few hours, returned, turned on the printer and pressed print. Issue gone.

                    1 Reply Last reply Reply Quote 0
                    • KP0005undefined
                      KP0005
                      last edited by

                      I was already at 3.1.1

                      JoergS5undefined 1 Reply Last reply Reply Quote 0
                      • JoergS5undefined
                        JoergS5 @KP0005
                        last edited by

                        @Matej101 I expect it will appear again, if you didn't find any reason. Maybe a loose connection or a thermal effect. Please tell if it reappears. And if it reappears, you should make a M122 directly after appearing, maybe you can analyze something then.

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