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

    Easier Z Offset control

    Scheduled Pinned Locked Moved
    Firmware wishlist
    4
    12
    836
    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.
    • Krohm Koalaundefined
      Krohm Koala
      last edited by

      Hi, i know it's set directly in config.g but do you think it is possible to add something to tune it easily directly on the DWC and PanelDue, and maybe separate the height map and the Z offset, so long to redo all the thing everytime a really little change is needed. Don't know if it's possible, but could be cool 🙂

      Have a nice day !

      Stephen6309undefined 1 Reply Last reply Reply Quote 0
      • Stephen6309undefined
        Stephen6309 @Krohm Koala
        last edited by

        @krohm-koala I use a macro to set the G31 stuff. It allows you to change it without resclicing or rebooting.

        1 Reply Last reply Reply Quote 0
        • Krohm Koalaundefined
          Krohm Koala
          last edited by

          Such a good idea ! Thanks for the reply !

          1 Reply Last reply Reply Quote 0
          • E1ixirundefined
            E1ixir
            last edited by

            I use this macro which is really cool:

            T0
            M291 P"Press ""OK"" if you would you like to calibrate the Z-offset for this Tool Cartridge." R"Calibrate Z-Offset" S3
            M291 P"Make sure your nozzle is free of debris. Press ""Cancel"" if you need to stop and clean the nozzle." R"Calibrate Z-Offset" S3
            M291 P"Homing, please wait..." R"Calibrate Z-Offset" S1
            M98 P/sys/homeall.g
            M208 S1 Z-2 ; allow movement below Z0
            G1 X100 Y10 Z8 F2000 ; move to center of bed
            M558 P0
            G30 S-2
            M500 ; save results
            M501 ; load new data
            M208 S1 Z0 ; disallow movement below Z0
            G1 Z25 ; drop build plate
            M291 P"Z-offset calibration complete! " R"Calibrate Z-Offset" S1 T3

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

              @e1ixir Wouldn't you need to use M500 P31 to save the trigger height?

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

              Z-Bot CoreXY Build | Thingiverse Profile

              1 Reply Last reply Reply Quote 0
              • E1ixirundefined
                E1ixir
                last edited by E1ixir

                No, the macro doesn't use G31

                1 Reply Last reply Reply Quote 0
                • Krohm Koalaundefined
                  Krohm Koala
                  last edited by

                  Thanks I'll try this macro but I'm on the @Phaedrux side, now it need the M500 P31 to save the trigger height (according to the dozuki)

                  1 Reply Last reply Reply Quote 0
                  • E1ixirundefined
                    E1ixir
                    last edited by E1ixir

                    See here: https://forum.duet3d.com/topic/8645/solved-calibrate-z-probe-macro/12

                    My english is not so good, but I think the explanation can be found in this message (thanks to its author):

                    "jckray 18 janv. 2019 à 08:30
                    ...this script measures and saves a G10 tool offset, which is separate from the z-probe trigger hight. I went this route, because, as I understand it, measuring the trigger height just reports the value and requires a manual G31 entry with the new trigger hight in order for M500 P31 to save the new trigger height. For an individual printer without any kind of tool changing it is probably better to just measure the trigger height and manually update the value in config. For my application which is for a consumer product and has to do with tool changing it actually makes more sense to use the tool offset to and have a static z-probe trigger height."

                    Krohm Koalaundefined 1 Reply Last reply Reply Quote 0
                    • Krohm Koalaundefined
                      Krohm Koala @E1ixir
                      last edited by

                      @e1ixir Bon je sais que beaucoup ne comprendront pas, mais, du coup, tu save comment ton offset ? Obligé de modifier dans le config.g ? Parce qu'il y a rien dans le macro qui à l'air de save ça ._.

                      1 Reply Last reply Reply Quote 0
                      • E1ixirundefined
                        E1ixir
                        last edited by

                        Mais si, tu as un M500! L'offset est sauvegardé dans config.overrides.g, sous la forme d'une commande G10. Bref, essaye, tu verras, ca marche très bien... Une autre solution aurait été d'utiliser un G31 S-3, je pense.

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

                          @e1ixir said in Easier Z Offset control:

                          L'offset est sauvegardé dans config.overrides.g, sous la forme d'une commande G10.

                          Mais bien sûr!

                          Z-Bot CoreXY Build | Thingiverse Profile

                          1 Reply Last reply Reply Quote 0
                          • Krohm Koalaundefined
                            Krohm Koala
                            last edited by

                            J'ai essayé, ça à l'air d'aller pas trop mal, même si j'ai essayé plusieurs fois (avec un print entre 2) et ma buse se crash dans le bed des fois, j'ai pas trop compris mais à voir, j'ai surement merdé quelque part x) D'un côté j'pense que je l'adapterais pour enregistrer un G31, j'préfère rester avec un G31 même si avec le G10 ça à l'air d'aller pas trop mal.

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