Duet3D Logo

    Duet3D

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

    Problem with negative Z-probe trigger values

    Firmware installation
    2
    4
    835
    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.
    • Laurman
      Laurman last edited by

      Hi,

      After upgrading to the v1.19 I encountered two bugs:

      1. My CoreXY X and Y axes were flipped - had a easy fix by changing the motor directions
      2. Homez.g and homeall.g files do not recognize negative G92 Z- values. If the trigger height is set negative, Duet completely ignores it and sets the value to zero. Everything works correctly when I use positive values, Duet recognizes it and uses it as it should. Unfortunately I need negative values to get my nozzle probe working again. Deployprobe.g and retractprobe.g files are deleted.

      Thanks for your time.

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

        #1 is documented in the upgrade notes.

        Regarding #2, if you are using a Z probe for Z homing, you should not be using a G92 command. A G92 command is only needed when a Z endstop switch is being used, and the switch trigger position is not the same as the axis limit.

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

          Thanks for the quick reply. I replaced the second G1 commands for Z-homing with G30 and stated the necessary trigger values in config.g. Now everything works as intended.

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

            I'm glad you got it working. If anyone does need to use G92 with an axis position outside the M208 limits, I suspect it can be done by sending M564 S0 before the G92 command to suspend axis limits, and M564 S1 afterwards to restore them; but I haven't tested this.

            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