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

    End Stop Problems

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    9
    22
    4.2k
    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.
    • Jackalundefined
      Jackal
      last edited by

      Please show the type of end stop you are using and current wiring

      1 Reply Last reply Reply Quote 0
      • T3P3Tonyundefined
        T3P3Tony administrators
        last edited by

        Sounds like the endstop wiring is causing an issue. Have a look here for a good start point:

        https://duet3d.com/wiki/Connecting_endstop_switches

        www.duet3d.com

        1 Reply Last reply Reply Quote 0
        • elmoretundefined
          elmoret
          last edited by

          Some photos of the endstops and how you have them connected would be helpful. If connected improperly they can short 3.3v to ground.

          1 Reply Last reply Reply Quote 0
          • brianundefined
            brian
            last edited by

            Sorry dont know how to load a pic here.

            Have been to duet wifi sites but havent had much success. I loaded a different config.g file so now when endstops are triggered they stop the axis but then a reboot is needed to run any other macros or moves.

            Also with all endstops connected (3) the z axis will only go in one direction from macros. The move command on paneldue will move it in either direction but way too fast.

            1 Reply Last reply Reply Quote 0
            • brianundefined
              brian
              last edited by

              Has anyone upgraded from a Rumba? I may have to return to the rumba if i cant this running. It should be easy but its not, why?

              1 Reply Last reply Reply Quote 0
              • elmoretundefined
                elmoret
                last edited by

                A lot of us have upgraded from Rumba to Duet Wifi, myself included. I found it straightforward, was up and running in about 20 minutes.

                The requested photo(s) will help with the endstop configuration. It sounds like the config file is telling the firmware that your z-axis is always triggered. Endstops can be active high or active low, and need to be configured appropriately.

                You can upload images to imgur, then use the image button in the posting tools to attach to the post. You can also just copy/paste the URL into the post.

                1 Reply Last reply Reply Quote 0
                • Cataundefined
                  Cata
                  last edited by

                  @brian:

                  Has anyone upgraded from a Rumba? I may have to return to the rumba if i cant this running. It should be easy but its not, why?

                  Because you don't read the wiki

                  1 Reply Last reply Reply Quote 0
                  • brianundefined
                    brian
                    last edited by

                    I've read it over and over, thx.

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

                      Use an ohm/volt meter or the like to verify the end stop switches are doing what you think they are.

                      Use the M119 command from the web interface to verify the state of your end stops.

                      Configuring the end stops is one of the easier things to do since you can quickly verify they are correct with the M119 command.

                      You just have to take it one step at a time - check you hardware first and then the config.

                      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
                      • Rlcundefined
                        Rlc
                        last edited by

                        I just replaced my Rumba this weekend… The endstops are not plug and play you have to change the wires. They use the two outer pins on the Duet Wifi. Also be aware that the Z endstop is not used. You have to connect the Z end stop to the E0 Endstop and set the probe type to 4. example "M558 P4 X0 Y0 Z1 F500 T5000 H3" for probing to work correctly.

                        Im thinking about writing a guide from what I did but its all slowly fading. May write some stuff down after work.

                        ~Roy

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

                          You can use a Z endstop switch connected to the Z endstop connector if you wish, it all depends on whether you have your homing files configured to use a Z probe or an endstop switch for Z homing. See https://duet3d.com/wiki/Configuring_RepRapFirmware_for_a_Cartesian_printer#Homing_Z_using_a_Z_probe and https://duet3d.com/wiki/Configuring_RepRapFirmware_for_a_Cartesian_printer#Homing_Z_without_a_Z_probe.

                          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
                          • brianundefined
                            brian
                            last edited by

                            If i enter gcode in the console on the paneldue, the z axis stops when endstop is triggered, however if i put same code into the homez.g file the z axes just pushes past the endstop and wont stop powered down.

                            1 Reply Last reply Reply Quote 0
                            • brianundefined
                              brian
                              last edited by

                              @Rlc:

                              I just replaced my Rumba this weekend… The endstops are not plug and play you have to change the wires. They use the two outer pins on the Duet Wifi. Also be aware that the Z endstop is not used. You have to connect the Z end stop to the E0 Endstop and set the probe type to 4. example "M558 P4 X0 Y0 Z1 F500 T5000 H3" for probing to work correctly.

                              Im thinking about writing a guide from what I did but its all slowly fading. May write some stuff down after work.

                              ~Roy

                              Ok thanks i will try changing to the E0 endstop. Yes i have changed the wiring pins as you say. Please do write a guide!

                              1 Reply Last reply Reply Quote 0
                              • brianundefined
                                brian
                                last edited by

                                These are the same endstops

                                https://www.bing.com/images/search?view=detailV2&ccid=i5mGSJ61&id=56250BAECF05955774D9E09E268DFBE23FCD6E2B&thid=OIP.i5mGSJ61KzNWaR7gAITkgwEsDn&q=endstops&simid=608009852723005880&selectedIndex=172&ajaxhist=0

                                1 Reply Last reply Reply Quote 0
                                • brianundefined
                                  brian
                                  last edited by

                                  Calvinx, thx for your advise. I had already changed the pins, basically flipping the connectors. If the pins are the same way as rumba then wifi will not connect. I rec'd some new endstops of the same kind and replaced the z one just in case it may have been defective but it doesnt make any difference.

                                  I changed the S2 to S0 which then makes the x axis go the wrong way. It also didnt help the z, which still pushes past endstops and keeps going.

                                  1 Reply Last reply Reply Quote 0
                                  • brianundefined
                                    brian
                                    last edited by

                                    RLC, changed the position of z pin to E0 and the M558 setting in config.g file, and it makes no difference.

                                    1 Reply Last reply Reply Quote 0
                                    • brianundefined
                                      brian
                                      last edited by

                                      Big thanks to dc42 for taking time to look at my posts. I have gone thru those wiki files several times without success, will try again to see if i missed something or misinterpreted.

                                      1 Reply Last reply Reply Quote 0
                                      • deckingmanundefined
                                        deckingman
                                        last edited by

                                        @brian:

                                        …...............I changed the S2 to S0 which then makes the x axis go the wrong way...............

                                        Defining whether switches are active low or active high shouldn't make any difference to the way axes move. It's just the same as using a micro switch and telling the Duet whether it is wired to use the normally open contacts or the normally closed contacts. Did you set S0 in M574 or somewhere else? Also, the S parameter can only be 1 or 0. The Wiki is pretty good but it seems that you've got confused somewhere along the line.

                                        Lets take one axis at a time and see if I can make clearer. So for just the X axis you'd have M574 Xnnn Snnn. The nnn after the X tells the machine where abouts on the axis the switch is fitted. The most common configuration is X = 0 as the left hand side and that's where the switch is fitted (low end in the Wiki). So in that case you'd have M574 X1….. You could fit the switch at the other end of the X axis (right hand side) but still have X=0 as being on the left. In which case you'd have M574 X2 (high end in the Wiki). In the case of a high end switch (on the right but X=0 is on the left) when you home the printer, it will move the head to the right until it "sees" the switch. At which point it will know that it is nnn (whatever your axis maximum is set to) mm away from X=0, so when you tell the machine to go to X=0 it will go left by nnn mm from the homing point. That's "high end" and "low end" covered. The only other value you could have after the "X" is 0 (zero) which means there is no switch at all for that axis.

                                        Then the nnn after the "S" is either 0 or 1. As explained above, if you had a simple switch which was normally closed but became open when something touches it, it's called "active high" and you use S1. If the switch is normally open but becomes closed (makes a circuit) when something touches it, you use S0. Not all end stop switches are simple micro switches which is why the terms "Active High" and "Active Low" are used instead of "Normally Open" or "Normally Closed"

                                        HTH
                                        Ian

                                        Ian
                                        https://somei3deas.wordpress.com/
                                        https://www.youtube.com/@deckingman

                                        1 Reply Last reply Reply Quote 0
                                        • brianundefined
                                          brian
                                          last edited by

                                          deckingman, nicely explained.

                                          So i have my endstops set ; M574 X1 Y1 Z1 S1 and the x and y work properly, the z does not. When home z, nothing happens. All axis move properly using the paneldue move command or the web console move commands. Z moves but does not stop at the endstop.

                                          With all axis homed or at 0, the z endstop light is on, x and y endstop lights are off. On the board only the z light is on. In the web console head position show at 0.0, In the head movement window show x and y axis homed, z axis not homed.
                                          The M119 command shows x y z and z probe at min. stop. Note there is no z probe connected.

                                          This is the the config.g file in part;

                                          ; General preferences
                                          M111 S0 ; Debugging off
                                          G21 ; Work in millimetres
                                          G90 ; Send absolute coordinates…
                                          M83 ; ...but relative extruder moves
                                          M555 P2 ; Set firmware compatibility to look like Marlin
                                          M208 X0 Y0 Z0 S1 ; Set axis minima
                                          M208 X200 Y200 Z140 S0 ; Set axis maxima

                                          ; Endstops
                                          M574 X1 Y1 Z1 S1 ; Define active high microswitches
                                          M558 P4 X0 Y0 Z0 H3 F500 T5000 ; Set Z probe type to unmodulated, the axes for which it is used and the probe + travel speeds
                                          G31 P500 X0 Y0 Z1.1 ; Set Z probe trigger value, offset and trigger height
                                          M557 X25:175 Y25:175 S25 ; Define mesh grid

                                          ; Drives
                                          M569 P0 S1 ; Drive 0 goes forwards
                                          M569 P1 S1 ; Drive 1 goes forwards
                                          M569 P2 S1 ; Drive 2 goes forwards
                                          M569 P3 S1 ; Drive 3 goes forwards
                                          M569 P4 S1 ; Drive 4 goes forwards
                                          M350 X128 Y128 Z128 E32:32 I0 ; Configure microstepping without interpolation
                                          M92 X640 Y640 Z3200 E1000:1000 ; Set steps per mm
                                          M566 X900 Y900 Z12 E120:120 ; Set maximum instantaneous speed changes (mm/min)
                                          M203 X12000 Y12000 Z1200 E12000:12000 ; Set maximum speeds (mm/min)
                                          M201 X1000 Y1000 Z100 E200:200 ; Set accelerations (mm/s^2)
                                          M906 X855 Y855 Z855 E1200:1200 I30 ; Set motor currents (mA) and motor idle factor in per cent
                                          M84 S30 ; Set idle timeout

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

                                            This is a very common issue and usually means that your homing files are set up to use a Z probe to do Z homing when you are expecting an endstop switch to be used. See https://duet3d.com/wiki/Configuring_RepRapFirmware_for_a_Cartesian_printer#Homing_Z_using_a_Z_probe and the following section on the same page.

                                            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