Duet3D Logo

    Duet3D

    • Register
    • Login
    • Search
    • Categories
    • Tags
    • Documentation
    • Order

    NPN Probe on Z axis

    General Discussion
    4
    10
    1782
    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.
    • richardmckenna
      richardmckenna last edited by

      Hi all,

      Firstly I have read and reread the wiki but cannot seem to find the solution to the issue I am having with using an NPN NO Probe for the the z axis endstop.

      I have it wired up with a diode and connected to the E0 STP pin. When triggering it manually (by placing a metal object under it), both the LED on top of the probe and the LED on the DuetWiFi lights up. Which to me indicated the hardware is working fine.

      However when I home the Z axis, when the probe is triggered it does not stop the motor so the z axis just keeps moving up.

      I must be missing something in the config. So if anyone can help, that would be great.

      Thanks,

      Richard

      config.g
      ; Endstops
      M574 X1 Y1 S0 ; Define active low and unused microswitches
      M574 Z0 E1 S1 ; Define active high microswitches
      M558 P4 I1 X0 Y0 Z1 H10 F120 T6000 ; Set Z probe type to switch, the axes for which it is used and the probe + travel speeds
      G31 P500 X28 Y12 Z1.20 ; Set Z probe trigger value, offset and trigger height

      homez.g
      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

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

        Your config looks ok to me. I suggest you use M119 or the web interface to check whether the firmware sees the sensor as triggered when the LEDs turn on.

        Some people seem to need to use a Schottky diode when connecting the probe output to the endstop input. For others, an ordinary silicon diode works. Perhaps it depends on the sensor.

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

          Thanks,

          Using M119 I get

          Endstops - X: not stopped, Y: not stopped, Z: not stopped, Z probe: not stopped

          X and Y work fine, neither z or z prode are activated when manually triigering the probe despite both lights being on.

          I guess I need to source some Schottky diodes.

          The 2 diodes I tried were:

          1N4148 150mA Switching Diode
          1N4007S 1A Silicon Rectifier

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

            Try a Schottky diode e.g. BAT43 or BAT85.

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

              Just an update. The BAT43 diode works perfectly.

              So I now have a fully working NPN Probe with the Duet WiFI.

              I will give the Mini differential IR height sensor a go when it arrives 🙂

              Thanks dc42

              1 Reply Last reply Reply Quote 0
              • MKGC
                MKGC last edited by

                richardmckenna, how is the BAT43 diode wired into the leads? On the signal lead between the sensor and the controller? Which direction? I am not particularly wise in this area. 🙂

                1 Reply Last reply Reply Quote 0
                • pao_wikhan
                  pao_wikhan last edited by

                  i have this sensor and i used a bat85 for it, the untriggered output is at 0.5-0.6V and triggered is showing 0.14-0.2V, im using 24V, i have not attached it yet to the duet. are those values reasonable for duet to be read?

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

                    The 0.5 to 0.6V is unusually low.

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

                      usually what should be the signal input voltage accepted by the board?

                      1 Reply Last reply Reply Quote 0
                      • pao_wikhan
                        pao_wikhan last edited by

                        interestingly, it seems the signal is being distinguished.

                        [[language]]
                        >>> M119
                        SENDING:M119
                        Endstops - X: not stopped, Y: not stopped, Z: at min stop, Z probe: at min stop
                        >>> M119
                        SENDING:M119
                        Endstops - X: not stopped, Y: not stopped, Z: not stopped, Z probe: not stopped
                        
                        
                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post
                        Unless otherwise noted, all forum content is licensed under CC-BY-SA