Duet3D Logo

    Duet3D

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

    Z Height

    IR Height Sensor
    5
    10
    491
    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.
    • Dqtreats
      Dqtreats last edited by Dqtreats

      I've went through multiple forums and went over the procedure time after time. I'm getting a reading of 0.98 when it comes to my Z Height. so I changed my Z on my G31 code and I cant get the printer to print on the bed. The only way I was able to, was by editing the Z offset in my slicer and it worked. However after a restart, it doesn't work anymore and lost its parameters. I don't have a config-override file, and my Bed.g doesn't have G31 in it. What else could be going on?

      *Z offset on slicer wont work anymore. Only thing that works is finding the difference of my current bed height and adding or subtracting if from my M665 command at the top of my config.g file. I've had 3 people helping me with this and we've also changed config files but nothing changes.

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

        We could use some more information. https://forum.duet3d.com/topic/5909/guide-for-posting-requests-for-help

        Z-Bot CoreXY Build | Thingiverse Profile

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

          Idk what version I'm using. 2.0.2??

          Im using a Duet 2 Wifi on a Delta, Tevo LlM

          I figured out that the ONLY Z Height adjustments that I can find is by editing the MAX Height of the printer drive. Is there no possible way to offset this???? I cant do it by the config.g or even in the slicer.

          I cant upload my config from my android.

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

            Have you looked in config-override.g?
            You'll probably need to change it in there instead.
            You could send the change as gcode first to make sure its correct before saving it with M500

            Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

            deckingman Dqtreats 2 Replies Last reply Reply Quote 0
            • deckingman
              deckingman @jay_s_uk last edited by

              @jay_s_uk said in Z Height:

              Have you looked in config-override.g?
              You'll probably need to change it in there instead.
              You could send the change as gcode first to make sure its correct before saving it with M500

              He said in his OP that he doesn't have a config-override file.

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

              1 Reply Last reply Reply Quote 1
              • Dqtreats
                Dqtreats @jay_s_uk last edited by

                @jay_s_uk I dont have a config-override

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

                  Have you read through this:

                  https://duet3d.dozuki.com/Wiki/Gcode#Section_G31_Set_or_Report_Current_Probe_status

                  Generally you reduce z height (move nozzle closer to bed, or move elevator up to nozzle) until the probe triggers with the probe dead centre. Record the z height. Reduce z height until the nozzle just touches the bed. Record that z height. Use the difference as the probe trigger height.

                  Alive: 1 Ormerodish machines. 1 Custom Cantilever. 3 P3Steel. 1 Ciclopish scanner. In build: 1 P3Steel. Controllers: 2 Duet 2 , 2 D0.6, 1 D0.8.5, 1 D3 v0.5, 1 RAMPS/DRV8825, 1 Uno/Scan Card.

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

                    You may also need to look at the repeat measures and tollerances for probing.

                    Without being able to see the config file or know what sort of values you are having to adjust by we can't be much help.

                    Alive: 1 Ormerodish machines. 1 Custom Cantilever. 3 P3Steel. 1 Ciclopish scanner. In build: 1 P3Steel. Controllers: 2 Duet 2 , 2 D0.6, 1 D0.8.5, 1 D3 v0.5, 1 RAMPS/DRV8825, 1 Uno/Scan Card.

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

                      Minimum z is often set at below 0, but there are actions when the firmware ignores the minimum and maximum and goes where it likes! I'm not sure if probing is one of them, but it maybe worth adding for a check.

                      That said if your trigger height is 0.98 above the bed then your bed has to be very uneven for that to be needed.

                      Alive: 1 Ormerodish machines. 1 Custom Cantilever. 3 P3Steel. 1 Ciclopish scanner. In build: 1 P3Steel. Controllers: 2 Duet 2 , 2 D0.6, 1 D0.8.5, 1 D3 v0.5, 1 RAMPS/DRV8825, 1 Uno/Scan Card.

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

                        You've not said what IR sensor you are using. Some are strongly influenced by ambient IR light, be that clouds moving and soaking your machine in sunlight or turning on and off a halohen/filament desk light.

                        Edit: Just seen M665 relates to delta machines. Want one, but don't have one so I'll leave you lot in peace now! 😄

                        Alive: 1 Ormerodish machines. 1 Custom Cantilever. 3 P3Steel. 1 Ciclopish scanner. In build: 1 P3Steel. Controllers: 2 Duet 2 , 2 D0.6, 1 D0.8.5, 1 D3 v0.5, 1 RAMPS/DRV8825, 1 Uno/Scan Card.

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