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

    Cant get my nozzle close to bed at all when trying to print

    Scheduled Pinned Locked Moved
    Tuning and tweaking
    5
    78
    7.0k
    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.
    • Puppet172undefined
      Puppet172 @Puppet172
      last edited by

      @dc42 @Phaedrux
      Fixed that but now it says insufficient axis's homed How can i stop this from happening becuase it say i need to home x and y first before homing z but i can home x because it says
      G28 X
      Error: G0/G1: insufficient axes homed

      1 Reply Last reply Reply Quote 0
      • whosrdaddyundefined
        whosrdaddy
        last edited by whosrdaddy

        Reading the firmware upgrade notes would have prevented this question 🙂
        In recent firmwares you cannot move axes before they are homed, so you must add S2 to G1 moves for non homed axes...
        Anyway, you can add M564 H0 to your config.g file to have the old behavior back...

        Puppet172undefined 1 Reply Last reply Reply Quote 0
        • Puppet172undefined
          Puppet172 @whosrdaddy
          last edited by

          @dc42
          How can i control my fans in the new server version because i only see control for Fan 0 and i have mine on 1&2

          Puppet172undefined 1 Reply Last reply Reply Quote 0
          • Puppet172undefined
            Puppet172 @Puppet172
            last edited by

            @puppet172
            Nvm

            1 Reply Last reply Reply Quote 0
            • Puppet172undefined
              Puppet172
              last edited by

              @dc42
              Still not using the mesh bed compensation during print. Even after i updated. Any idea why?

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

                @puppet172 Did you add the M375 or G29 S1 command to load the height map to your config.g?

                Z-Bot CoreXY Build | Thingiverse Profile

                Puppet172undefined 1 Reply Last reply Reply Quote 0
                • Puppet172undefined
                  Puppet172 @Phaedrux
                  last edited by

                  @phaedrux
                  no where would i add that
                  0_1530485751276_config (3).g

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

                    Just add M375 anywhere in config.g.

                    I put mine in the section where I configure the mesh size and z probe.

                    Z-Bot CoreXY Build | Thingiverse Profile

                    Puppet172undefined 1 Reply Last reply Reply Quote 0
                    • Puppet172undefined
                      Puppet172 @Phaedrux
                      last edited by

                      @phaedrux
                      That should fix it then?

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

                        That will load the height map if you've run a successful compensation probing. That will adjust the nozzle height based on the probe data to keep it at the specified height from the bed at all times.

                        Hopefully that will resolve your issue.

                        Z-Bot CoreXY Build | Thingiverse Profile

                        Puppet172undefined 1 Reply Last reply Reply Quote 0
                        • Puppet172undefined
                          Puppet172 @Phaedrux
                          last edited by

                          @phaedrux
                          if i change me trigger height should i run another mesh bed compensation( G29)

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

                            I'm not sure about that. As long as the probe is triggering consistently when you make the map the new trigger height should be applied after homing z and it should follow the height map correctly, but I could be wrong in my thinking there.

                            Regardless, I like to follow this order for bed leveling just to make sure.

                            Mechanically level your bed as well as you can first.

                            Measure your trigger height at least 10 times and take the average (or mode if it looks like a single value repeats most often).

                            Then run a compensation probing routine knowing that the results should be as accurate as possible.

                            Then you can varify that the height compensation is applied by moving to z=0.5 and jogging the head over the bed and see if the z axis is engaging to keep the distance the same as it moves.

                            Z-Bot CoreXY Build | Thingiverse Profile

                            Puppet172undefined 1 Reply Last reply Reply Quote 0
                            • Puppet172undefined
                              Puppet172 @Phaedrux
                              last edited by

                              @phaedrux @dc42

                              When im doing a mesh bed compensation It keeps getting to a point where the bed is a little higher there and it triggers the probe before it probes there. so i get this
                              Error: Z probe already triggered before probing move started
                              Is there anyway to get around this because all my axis's are level the bed just isnt
                              Thanks

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

                                You can try increasing your dive height a millimeter or two.

                                Z-Bot CoreXY Build | Thingiverse Profile

                                Puppet172undefined 1 Reply Last reply Reply Quote 0
                                • Puppet172undefined
                                  Puppet172 @Phaedrux
                                  last edited by

                                  @phaedrux
                                  Where is that?

                                  Puppet172undefined 1 Reply Last reply Reply Quote 0
                                  • Puppet172undefined
                                    Puppet172 @Puppet172
                                    last edited by

                                    @puppet172 @Phaedrux
                                    Nvm found it

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

                                      The H value in the M558 command in config.g

                                      Z-Bot CoreXY Build | Thingiverse Profile

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

                                        @puppet172 did it work?

                                        Z-Bot CoreXY Build | Thingiverse Profile

                                        Puppet172undefined 1 Reply Last reply Reply Quote 0
                                        • Puppet172undefined
                                          Puppet172 @Phaedrux
                                          last edited by

                                          @phaedrux @dc42
                                          Yeah it worked.
                                          And another question. When i re did my G29 to have more points to be more accurate, now when ever i print it is much higher off the print bed like a couple millimeters. Why would this be happening?
                                          Thanks

                                          Puppet172undefined 1 Reply Last reply Reply Quote 0
                                          • Puppet172undefined
                                            Puppet172 @Puppet172
                                            last edited by

                                            @Phaedrux @dc42
                                            0_1530550571985_IMG_3183[1].JPG

                                            I don't think the bed level is working to well

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