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

    Z-Probe trigger inverted after update to RRF3.0

    Scheduled Pinned Locked Moved Solved
    Firmware installation
    5
    16
    745
    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.
    • SIamundefined
      SIam
      last edited by

      @wcj97 said in Z-Probe trigger inverted after update to RRF3.0:

      M574 Z1 S2

      and if you remove this line

      M574 Z1 S2
      

      Hypercube-Evolution-Hybrid, Piezo Orion, Orbiter
      Duet WiFi 1.02 or later + DueX5
      RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.0beta4 (2021-09-27 11:30:36)
      Duet WiFi Server: 1.26
      Duet Web Control 3.4.0beta4 (2021-09-27)

      wcj97undefined 2 Replies Last reply Reply Quote 1
      • wcj97undefined
        wcj97 @SIam
        last edited by

        @SIam Nope, still inverting the input.

        Is the "I" parameter still needed in RRF3.0 to invert the input? I know the M558 in my config.g from RRF1.19 had that included

        Original Prusa i3 MK2
        Hephaestus (Custom Duet based large format FFF)
        Aeon (Custom belt printer)
        Elegoo Mars

        1 Reply Last reply Reply Quote 0
        • wcj97undefined
          wcj97 @SIam
          last edited by

          @SIam Wait! I take that back. I changed the sensor type to "P5" in addition to what you said and that seems to have worked. Thank you for the help! Now on to my next struggle

          Original Prusa i3 MK2
          Hephaestus (Custom Duet based large format FFF)
          Aeon (Custom belt printer)
          Elegoo Mars

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

            @SIam said in Z-Probe trigger inverted after update to RRF3.0:

            @wcj97 said in Z-Probe trigger inverted after update to RRF3.0:

            M558 P1 C"zprobe.in" H5 F120 T6000

            try this

            M558 P1 C"!zprobe.in" H5 F120 T6000
            

            If it's an NPN-output probe then you also need to enable the pullup resistor:

            M558 P1 C"!^zprobe.in" H5 F120 T6000
            

            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

            wcj97undefined 1 Reply Last reply Reply Quote 1
            • wcj97undefined
              wcj97 @dc42
              last edited by

              @dc42 Just curious, what exactly is the pullup resistor doing? Currently I don't have that on, but I'm assuming you have a good reason for enabling the pullup resistor. Is it just an over-current protection for the sensor/board?

              Original Prusa i3 MK2
              Hephaestus (Custom Duet based large format FFF)
              Aeon (Custom belt printer)
              Elegoo Mars

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

                @wcj97 said in Z-Probe trigger inverted after update to RRF3.0:

                @dc42 Just curious, what exactly is the pullup resistor doing? Currently I don't have that on, but I'm assuming you have a good reason for enabling the pullup resistor. Is it just an over-current protection for the sensor/board?

                An NPN-output sensor can only pull its output to ground. When it isn't doing that, you need something else to pull the Z probe input high. The pullup resistor does that. Without it, you would be relying on the leakage of the over-voltage protection diode.

                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

                damaged_goodsundefined 1 Reply Last reply Reply Quote 1
                • damaged_goodsundefined
                  damaged_goods @dc42
                  last edited by

                  @dc42 what would the code line look like on a duet 3 mainboard ,for a Z probe NPN sensor, running RRF 3.4? I am having trouble.

                  damaged_goodsundefined 1 Reply Last reply Reply Quote 0
                  • damaged_goodsundefined
                    damaged_goods @damaged_goods
                    last edited by

                    @damaged_goods said in Z-Probe trigger inverted after update to RRF3.0:

                    @dc42 what would the code line look like on a duet 3 mainboard ,for a Z probe NPN sensor, running RRF 3.4? I am having trouble.

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

                      @damaged_goods It's literally 4 posts up

                      If it's an NPN-output probe then you also need to enable the pullup resistor:

                      M558 P1 C"!^zprobe.in" H5 F120 T6000

                      Z-Bot CoreXY Build | Thingiverse Profile

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

                        @phaedrux said in Z-Probe trigger inverted after update to RRF3.0:

                        @damaged_goods It's literally 4 posts up

                        If it's an NPN-output probe then you also need to enable the pullup resistor:

                        M558 P1 C"!^zprobe.in" H5 F120 T6000

                        Or as above but preferanly with probe type P5 or P8.

                        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

                        damaged_goodsundefined 1 Reply Last reply Reply Quote 0
                        • damaged_goodsundefined
                          damaged_goods @dc42
                          last edited by

                          @dc42 @Phaedrux
                          Thanks guys. The Duet 3 board I have does not have a dedicated "Zprobe" pin. I wasn't sure what to call it in the code. I had thought "io_0.in". Not that I'm not trying 🙂

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

                            @damaged_goods which IO port on the Duet 3 have you connected the Z probe to? If you connected it to IO0 then you should use:

                            M558 P8 C"!io0.in"

                            plus whatever extra parameters you need in the M558 command.

                            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

                            damaged_goodsundefined 1 Reply Last reply Reply Quote 0
                            • damaged_goodsundefined
                              damaged_goods @dc42
                              last edited by

                              @dc42 that's better and the probe is working. Thank you

                              1 Reply Last reply Reply Quote 0
                              • dc42undefined dc42 marked this topic as a question
                              • dc42undefined dc42 has marked this topic as solved
                              • First post
                                Last post
                              Unless otherwise noted, all forum content is licensed under CC-BY-SA