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

    Z axis wont home

    Scheduled Pinned Locked Moved
    General Discussion
    5
    25
    3.4k
    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.
    • brianundefined
      brian
      last edited by

      Strange. If it were just the probe…but i cant homez when only using endstops either, so much something else.

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

        If the probe is always reading in the 900s regardless of whether it is touching something, then either the probe is damaged or it is not wired properly. So regardless of .g files, probe homing will not work until the probe readings are correct.

        Please post the config.g and homez.g files that you attempted to use with endstop homing.

        Please also post the results from M119 in the following situations:

        Z-endstop engaged
        Z-endstop released
        Z-probe activated (bed close enough to trigger it)
        Z-probe released (bed far enough away to not trigger it)

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

          Configuration file for Duet WiFi (firmware version 1.19 beta6) Wifi working, z endstop not working
          ; executed by the firmware on start-up
          ; generated by RepRapFirmware Configuration Tool on Tue Jun 20 2017 17:30:36 GMT-0700 (Pacific Daylight Time)

          ; 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 X420 Y430 Z650 S0 ; Set axis maxima

          ; Endstops
          M574 Z0 S0 ; Define active low and unused microswitches no need for this so have changed Z1 to Z0 to indicate no endstop
          M574 X1 Y1 S1 ; Define active high microswitches
          M558 P1 X0 Y0 Z1 H3 F200 T5000 R0 ; smart IR Z probe, used for homing Z axis only, dive height 3mm, probe speed 200mm/min, travel speed 5000mm/min, no recovery time
          G31 P500 X11.0 Y0.5 Z1.0 ; set threshold and offsets
          ;M558 P1 X0 Y0 Z1 H5 F120 T6000 ; Set Z probe type to unmodulated, the axes for which it is used and the probe + travel speeds
          G31 P500 X0 Y0 Z0.1 ; Set Z probe trigger value, offset and trigger height
          M557 X25:175 Y25:175 S25 ; Define mesh grid

          ; homez.g

          ;wiki/Configuring_RepRapFirmware_for_a_Cartesian_printer#Homing_Z_using_a_Z_probe
          G91 ; relative mode
          G1 Z4 F200 ; raise head 4mm to ensure it is above the switch trigger height
          G90 ; back to absolute mode
          G1 X0 Y0 F2000 ; put head wherever you want it to be when you home Z (omit this line if it doesn't matter)
          G91 ; relative mode
          G1 Z-200 S1 F100 ; move Z down until the switch triggers
          G90 ; back to absolute mode
          G92 Z0.3 ; tell the firmware that we are at Z=0.3mm

          ;G91 ; relative mode
          ;G1 Z4 F200 ; raise head 4mm to ensure it is above the Z probe trigger height
          ;G90 ; back to absolute mode
          ;G1 X100 Y100 F2000 ; put head over the centre of the bed, or wherever you want to probe
          ;G30 ; lower head, stop when probe triggered and set Z to trigger height

          Z-endstop engaged = @ min stop
          Z-endstop released = @ min stop
          Z-probe activated (bed close enough to trigger it) = @ min stop
          Z-probe released (bed far enough away to not trigger it) = @ min stop

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

            Does the red LED on the sensor light up when the sensor is triggered i.e. close to the bed, and stay off otherwise? If yes and you are getting those readings around 900 then that suggests a faulty connection between the sensor output pin and the Duet.

            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
            • elmoretundefined
              elmoret
              last edited by

              Just FYI David, I think he's using an Aus3D sensor.

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

                Brian, you are not configuring properly for a Z-endstop:

                M574 Z0 S0 ; Define active low and unused microswitches no need for this so have changed Z1 to Z0 to indicate no endstop
                M574 X1 Y1 S1 ; Define active high microswitches

                That does not set up a Z-endstop in firmware. You'd need to get rid of the first line and change the second line to:

                M574 X1 Y1 Z1 S1 ; Define active high microswitches

                Assuming all three endstops are active high.

                Please do that and re-run the M119 tests.

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

                  @dc42:

                  Does the red LED on the sensor light up when the sensor is triggered i.e. close to the bed, and stay off otherwise? If yes and you are getting those readings around 900 then that suggests a faulty connection between the sensor output pin and the Duet.

                  No it doesnt. It flashes twice on start up only.

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

                    That's not right. If you have connected it correctly then it should flash 4 times at startup. Perhaps you have connected the sensor output wire to the MOD pin of the Z probe connector instead of to the IN pin?

                    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

                      Z-endstop engaged = @ not stopped * this changed
                      Z-endstop released = @ min stop
                      Z-probe activated (bed close enough to trigger it) = @ min stop
                      Z-probe released (bed far enough away to not trigger it) = @ min stop

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

                        @dc42:

                        That's not right. If you have connected it correctly then it should flash 4 times at startup. Perhaps you have connected the sensor output wire to the MOD pin of the Z probe connector instead of to the IN pin?

                        I've connected sensor duetwifi
                        power to 3.3v
                        grnd to mod
                        –-- grnd
                        analogue probe in

                        Looks like i've got Grnd on sensor going to Mod on duet.

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

                          @brian:

                          Z-endstop engaged = @ not stopped * this changed
                          Z-endstop released = @ min stop
                          Z-probe activated (bed close enough to trigger it) = @ min stop
                          Z-probe released (bed far enough away to not trigger it) = @ min stop

                          This is a step in the right direction, but it seems as though that switch is active low, not active high. I assumed all three endstop switches were the same but is seems that is not the case. Try changing this:

                          M574 X1 Y1 Z1 S1 ; Define active high microswitches

                          to:

                          M574 Z1 S0 ; Define active low microswitches
                          M574 X1 Y1 S1 ; Define active high microswitches

                          That should set the firmware up to expect an active low microswitch on Z. The above code also assumes your endstop is at the Z-minimum, if it is at the Z-maximum then change to Z2 instead of Z1.

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

                            Tim, thanks for that. Brian, you had better talk to aus3d if you are using their sensor. It's my sensor (also so!d by Duet3D and Filastruder) that should flash 4 times at startup when connected to a Duet.

                            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

                              @dc42:

                              Tim, thanks for that. Brian, you had better talk to aus3d if you are using their sensor. It's my sensor (also so!d by Duet3D and Filastruder) that should flash 4 times at startup when connected to a Duet.

                              I think i have found the error, as i've mount the duet upside down, and with small print its hard to see clearly. I'll check until i'm convinced i see it right.

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

                                I changed the ground on the sensor to the next position on the duet .

                                It still only flashes twice on start up, but when bed approches the sensor a red led lights up until bed is moved away.

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

                                  Now the home z only moves the bed down a bit, but the home all works!!!

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

                                    Finally got the z probe offset to work, it resisted a lot, but is good now.

                                    Just want to thank dc42, elmoret, and CaLviNx for getting me thru this.

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

                                      Just love a happy ending.

                                      Frederick

                                      Printers: a E3D MS/TC setup and a RatRig Hybrid. Using Duet 3 hardware running 3.4.6

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