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

    Switch Z-probe not inverting

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    5
    46
    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.
    • resamundefined
      resam
      last edited by

      And does it change with M558 P4 I1 H5 F120 T3000?

      madmattcoundefined 1 Reply Last reply Reply Quote 0
      • madmattcoundefined
        madmattco @resam
        last edited by

        @resam No. Thats my dilemma. Its driving me nuts lol

        1 Reply Last reply Reply Quote 0
        • resamundefined
          resam
          last edited by

          Did you try:
          M574 X2 Y2 Z0 S0 and M558 P4 I1 H5 F120 T3000 (or I0)

          1 Reply Last reply Reply Quote 0
          • madmattcoundefined
            madmattco
            last edited by

            Will having Z set to 0 work properly when on a delta?

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

              @madmattco so if you send:

              M558 I1 does the probe setting change;
              0_1530457869993_b531902b-be8e-4e97-9072-15863069a2ea-image.png

              Ignore my other settings in the screen shot
              As you can see you can send M558 with no parameters to get a read out of the current settings
              Try M119 after both M558 I0 and M558 I1

              www.duet3d.com

              madmattcoundefined 1 Reply Last reply Reply Quote 0
              • madmattcoundefined
                madmattco @T3P3Tony
                last edited by

                @t3p3tony I owe you a pint. https://puu.sh/AP6NT/d101e9887d.png
                My question is, Why would it suddenly work when only issuing the M558 I1 command by its self?

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

                  @madmattco said in Switch Z-probe not inverting:

                  @t3p3tony I owe you a pint. https://puu.sh/AP6NT/d101e9887d.png
                  My question is, Why would it suddenly work when only issuing the M558 I1 command by its self?

                  When you were changing it in config.g, were you actually saving the changes and re-booting the Duet? If you were and if sending it through the console works but having it in config.g doesn't (and Duet is being restarted to read config.g again), then the only logical explanation that I can think of is that it's being reset elsewhere, like in config overide for example.

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

                  madmattcoundefined 1 Reply Last reply Reply Quote 0
                  • madmattcoundefined
                    madmattco @deckingman
                    last edited by

                    @deckingman I do not have a config override on my system. When I was issueing that command the first dozen times, I was including it in the primary M558 line under my Z-probe comment in config.g I have no idea where else it could have been getting reset at.

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

                      @madmattco glad it works. Changes to config.g only come into effect when the board is reset - that's why it prompts you for a reset after changing it there.

                      www.duet3d.com

                      madmattcoundefined 1 Reply Last reply Reply Quote 0
                      • madmattcoundefined
                        madmattco @T3P3Tony
                        last edited by

                        @t3p3tony That is what was driving me crazy. Because I clicked reboot every time I changed a setting. Now if only my autocal would work correctly

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

                          @madmattco

                          Maybe there is/was a hidden character in that M558 line which was causing the firmware to ignore it? Dunno - clutching at straws myself.....

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

                          1 Reply Last reply Reply Quote 0
                          • resamundefined
                            resam
                            last edited by

                            @chrishamm coming back to one of the earlier issues here, something for the DWC wishlist:

                            Would it be possible to make the Z-Probe box reflect the actual probe type?
                            Currently DWC always displays the 0-1000 analog reading, which might be confusing for people with digital/switch-type probes.

                            So, if its an analog type P1, P2, and P3 (?), then show the value 0-1000, as currently implemented.
                            But if it is a switch-type / digital, P4 through P9, then just show "triggered" and "untriggered" - accounting for the invert-flag.
                            Motor-stall detection P10 could be considered as P4-P9, or with "not stalled" and "stalled" strings.

                            0_1530517222443_Screen Shot 2018-07-02 at 09.40.02.png

                            One caveat: some people (including myself), reconfigure the probe type with multiple M558 commands in config.g and homez.g and various macros. To simplify things, I would suggest to only retrieve the probe type after booting (DWC connecting). Unless you think continuously querying M558 is reasonable (in non-printing states)?

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