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

    Bed leveling Anycubic Predator Delta

    Scheduled Pinned Locked Moved
    Tuning and tweaking
    2
    13
    984
    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.
    • gpermanundefined
      gperman @gperman
      last edited by gperman

      Removing M558 H30 did not solve the issue.
      I am currently running g29 and triggering the probe prematurely to see if it stops the carriage which it does not. Otherwise, I believe it would continue on and crash into the bed. I would not like to find that out the hard way.

      Can someone define or walk me through how to actually level a bed using an Anycubic Predator microswitch Z probe?

      I assume the main function for determine the level of the bed is g29 which appears in the dropdown menu of Auto Calibration.

      I have tried multiple codes in the config m558 P4, P5, C"e0stop", C3...
      on duet web control the e0 endstop hit shows no change. The z probe stays at 1000, no change.

      Tested the switch through the harness all the way to the connector that shows normally closed still and switching when pressed. Plus the e0 LED blinks when the switch is pressed. It's just not recognized in the software.

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

        Is that a probe that you have to attach to the print head before using it?

        Z-Bot CoreXY Build | Thingiverse Profile

        gpermanundefined 1 Reply Last reply Reply Quote 0
        • gpermanundefined
          gperman @Phaedrux
          last edited by gperman

          @Phaedrux yes.

          Also, i got the probe to recognize and change values in the interface by depinning and connecting it to the z probe connector on the board instead of e0.

          It starts at 0 and displays 1000 when triggered.

          Have not seen an effect on anything from adding ! As suggested.
          I need to try and see if the single z probe g code command works. I’m going to have to risk it potentially ramming into the bed i guess.

          Triggering the z probe whilst manually jogging the axes down does not stop the effector which is not encouraging.

          Ran G32 which did not touch the bed. Perhaps i am misunderstanding "probing." does the effector just glide along the bed? It doesn't stop at each point, dive down until the probe triggers then rise again like it did on the factory firmware/board.

          I assumed setting up the config tool using a microswitch would result in a behavior similar to the factory setup.

          I lowered G31 Z16.95 to Z12. The probe touches the bed now but I get an Error: Z probe already triggered at start of probing move.

          1 Reply Last reply Reply Quote 0
          • gpermanundefined
            gperman
            last edited by

            Yea, still havent figured this out. Ran bed.g as a macro, ran G29, G30, G31, G32. The probe just moves around to the XY coordinates but doesnt stop, doesnt dive, doesnt probe.

            I have no idea why.

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

              Is the switch normally open or normally closed?
              Do you have it connected to the in and ground terminals of the z probe connector?

              Use, M558 P5 C"zprobe.in" H5 F120 T6000
              I don't think you need the modulation pin because this isn't an analogue probe.

              Z-Bot CoreXY Build | Thingiverse Profile

              gpermanundefined 2 Replies Last reply Reply Quote 0
              • gpermanundefined
                gperman @Phaedrux
                last edited by gperman

                @Phaedrux i have it connected to the zprobe.in pin and zprobe.mod pin. It is a normally closed digital microswitch.

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

                  I'm just going from this: https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_Mode_Num_5

                  Z-Bot CoreXY Build | Thingiverse Profile

                  1 Reply Last reply Reply Quote 0
                  • gpermanundefined
                    gperman @Phaedrux
                    last edited by

                    @Phaedrux said in Bed leveling Anycubic Predator Delta:

                    Is the switch normally open or normally closed?
                    Do you have it connected to the in and ground terminals of the z probe connector?

                    Use, M558 P5 C"zprobe.in" H5 F120 T6000
                    I don't think you need the modulation pin because this isn't an analogue probe.

                    YES! This solved it! Thank you so much. This was a huge headache.

                    Removing the zprobe.mod allowed it to recognize as a digital switch instead of analogue and now it probes.

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

                      Glad that worked. I think the issue is that the configurator has the zmod pin selected by default and it's not easy to know beforehand what it is and why it's selected and that you should actually unassign it.

                      I think I'm going to suggest that it is unassigned by default in the configurator.

                      Z-Bot CoreXY Build | Thingiverse Profile

                      1 Reply Last reply Reply Quote 0
                      • gpermanundefined
                        gperman
                        last edited by

                        Or selectable by a check box in the z probe section under endstops.

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