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

    Odd Probing behaviour - Smart Effector

    Scheduled Pinned Locked Moved
    Smart effector for delta printers
    3
    12
    1.9k
    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.
    • Jareryundefined
      Jarery
      last edited by

      All the bed.g G30 commands are similar to these with H0 at end

      G30 P0 X0.00 Y113.00 Z-99999 H0
      G30 P1 X56.50 Y97.86 Z-99999 H0

      I do get the following error :

      G32
      Error: Z probe was not triggered during probing move

      Which is correct, it wasn't triggered since it didn't probing far enough

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

        If it doesn't go down far enough to trigger, this means that the homed height (H parameter) set in your M665 command is too low, and/or the dive height (H parameter again) in your M558 command is too low. I suggest you increase the H parameter in the M558 command to get successful probing. Then run M665 without parameters to establish the new homed height. Edit that into config.g, and run M500 to store the new value in config-override.g if you are using it. Then you can restore the M558 dive height to a lower value, for faster probing.

        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
        • Jareryundefined
          Jarery
          last edited by

          I Just increased the
          M665 H to another 3mm higher

          M665 L360.280 R179.698 H466 B140.0 X0.253 Y0.251 Z0.000

          Changed M558 H to 15 from 5

          ; Smart effector
          M558 P5 R0.4 F1000 H15
          G31 P100 X0 Y0 Z-0.2

          -rebooted

          • Homed printer
          • Auto Calibrate

          Went through 4 probes correct, then skipped 2, then multiple skips on next probe

          Edit : there is no config override file.

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

            If the skips are due to the probe not reaching the bed, you need to increase M558 H more. Try 20.

            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
            • Jareryundefined
              Jarery
              last edited by

              The M558 H (Dive Height) changes how high above it starts though doesn't it not how far below it goes?

              When I change it to 30, it does the auto calibration much higher above the bed,

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

                It changes both how high it starts and how far below z=0 it is prepared to go.

                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
                • Jareryundefined
                  Jarery
                  last edited by

                  Worked the first time.
                  Then today, M558 H set to 30.

                  Reboot system, Home, Auto Calibrate.
                  Probe now stops 30mm above bed center then moves to the outer diameter, then probes down to bed for 3 probes, 4th probe it only goes down about 5mm, very obvious now that the H30 has the effector so far above.

                  So this is not a "settings" issue. Why would it probe down the full 30mm sometimes, and only probe 5mm or so on other random probes.? The green LED does not trigger when it fails to probe.

                  Heres a video:
                  This is after its done 8 probes on the outter diameter successfully and is moving to the inner diameter of the last 8 probes and centre probe.
                  The first 4 probes in the clip are fine, the 5th it stops half way, the 6ths hits and skips.

                  https://www.dropbox.com/s/zwaaiy2wjkf6ibk/File%202017-10-03%2C%203%2058%2058%20PM.mov?dl=0

                  I have tried unsuccessfully about 6 times in a row now to get calibrate to work.

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

                    I suspect that you have a bad crimp connection in one of the wires between the 8-way connector on the effector and the Z probe connector on the Duet. Probably at the effector end of the cable.

                    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
                    • Jareryundefined
                      Jarery
                      last edited by

                      I ripped everything apart, rewired, seemed to go away a while. But its back lately. its always been intermittent so hard say if my rewiring ever did anything.

                      https://www.dropbox.com/s/pymyybrgm1zs47z/duet%20smart%20effector%20false%20trigger.mov?raw=1

                      And I cannot believe its a "bad crimp"

                      It goes down, hits the bed, skips twice, the led does not go off.
                      Then it lifts and goes to the next point, the led fires off the 3 times while its in the air moving.

                      Does that make sense for a "bad crimp".. or a delayed signal, full buffer or something ?

                      Typically after it does one of these , following probes has it dive only part way, and not make it to the board , and continue on to next point where again it only probes a portion of the dive height set.

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

                        That does make sense for a bad crimp. But another possibility is that one of the pins on the 8-pin connector hasn't been soldered. That connector has to be hand soldered, so it's possible that a pin has been missed. Please check. Failing that, it could be a bad solder joint on the effector.

                        What I think is happening is that at or shortly before the probe point that is skipped, the effector is receiving no power. Then the cable flexes and the dodgy connection makes contact. So after a couple of seconds the sensor completes its initialisation, which is why it flashes 3 times.

                        The particular connection i suspect is the one that carries +3.3V to the effector. Try moving the effector in the XY plane as if between probe points with a pause afterwards, and see if you can make the led flash 3 times with the same interval that you get when you first power the printer on.

                        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
                        • First post
                          Last post
                        Unless otherwise noted, all forum content is licensed under CC-BY-SA