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

    Need to lower the nozzle

    Scheduled Pinned Locked Moved
    General Discussion
    6
    72
    4.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.
    • OwenDundefined
      OwenD
      last edited by

      The math (or logic) in my original posted macro was incorrect.
      The baby-stepping value should be subtracted from the trigger height, not added.
      Macro shown above is correct.
      I should have stated that I had not tested it as I personally see no value in working this way.
      It was hastily done just to show the OP that it could be done.
      I have corrected the original post.

      1 Reply Last reply Reply Quote 0
      • jens55undefined
        jens55
        last edited by

        I am really glad to know that confusion about these measurements is not a rare phenomenon 🙂

        1 Reply Last reply Reply Quote 0
        • Baenwortundefined
          Baenwort
          last edited by

          I found the blog post at https://www.sublimelayers.com/2017/05/fdffsd.html?m=1 helpful when I was learning what trigger height means and how it changes.

          He posts still in some of the Delta communities and the visuals really help one understand. With the FSR and Smart Effector style probes the understanding is key and confusing with all the negative values.

          1 Reply Last reply Reply Quote 0
          • jens55undefined
            jens55
            last edited by

            BIG issue with the macro.
            Not sure what happened but somehow or other my z offset got set to z 395.xx with the obvious " Let's see if we can run the nozzle to China".
            Thankfully nothing broke.
            I haven't figured out as everything seems to run just fine if you run the macro just once. I did run into another issue though:
            If you run the macro multiple times without changing the babysteps, it will merely add onto the previous saved value of the z offset. The macro needs to reset the babysteps to zero before it exits.

            1 Reply Last reply Reply Quote 0
            • jens55undefined
              jens55
              last edited by

              OwenD, in another thread, mentioned to use

              M290 R0 S0 ; clear babystepping

              But there seems some concern about this working..... I will try it out.

              1 Reply Last reply Reply Quote 0
              • jens55undefined
                jens55
                last edited by jens55

                This is the new and improved macro:

                savez.txt

                Note that there are two changes - the line that clears the babysteps but also line 9 which introduced an error in the echoed text for Z offset.

                How can I get a nice text box like the previous posters ?

                fcwiltundefined 1 Reply Last reply Reply Quote 0
                • fcwiltundefined
                  fcwilt @jens55
                  last edited by fcwilt

                  @jens55

                  Hi,

                  You use the </> tag.

                  Frederick

                  ; 0:/macros/Save-Z
                  ; This macro adds the current babystep offset to the Z trigger height and saves it to config-overide.g
                  ; ! M501 needs to be in config.g to automatically be recalled on reset. If using multiple filament settings,
                  ; and this is for a specific filament type, recommend placing this yielded information in the filament's config.g.
                  
                  if move.axes[2].babystep !=0                                ; If no babysteps are currently adjusted - exit routine
                     echo {"OLD: " ^ sensors.probes[0].triggerHeight ^ " NEW: " ^ sensors.probes[0].triggerHeight + (move.axes[2].babystep * -1)}
                     G31 Z{sensors.probes[0].triggerHeight - move.axes[2].babystep}
                     echo {"Place either M501 -or- G31 Z" ^ sensors.probes[0].triggerHeight^ " in your config.g"}
                     M500 P10:31                                              ; save settings to config-overide.g - G31 P31 saves trigger height, 
                                                                              ; trigger value, and X and Y offsets for each possible Z probe type 
                                                                              ; P10 parameter saves the G10 tool offsets.
                     M290 R0 S0 												; clear babystepping 
                  
                  else
                     echo "Baby stepping is not currently employed, exiting."
                  
                  
                  

                  Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

                  jens55undefined 1 Reply Last reply Reply Quote 0
                  • jens55undefined
                    jens55
                    last edited by

                    ; 0:/macros/Save-Z
                    ; This macro adds the current babystep offset to the Z trigger height and saves it to config-overide.g
                    ; ! M501 needs to be in config.g to automatically be recalled on reset. If using multiple filament settings,
                    ; and this is for a specific filament type, recommend placing this yielded information in the filament's config.g.
                    
                    if move.axes[2].babystep !=0                                ; If no babysteps are currently adjusted - exit routine
                       echo {"OLD: " ^ sensors.probes[0].triggerHeight ^ " NEW: " ^ sensors.probes[0].triggerHeight + (move.axes[2].babystep * -1)}
                       G31 Z{sensors.probes[0].triggerHeight - move.axes[2].babystep}
                       echo {"Place either M501 -or- G31 Z" ^ sensors.probes[0].triggerHeight^ " in your config.g"}
                       M500 P10:31                                              ; save settings to config-overide.g - G31 P31 saves trigger height, 
                                                                                ; trigger value, and X and Y offsets for each possible Z probe type 
                                                                                ; P10 parameter saves the G10 tool offsets.
                       M290 R0 S0 												; clear babystepping 
                    
                    else
                       echo "Baby stepping is not currently employed, exiting."
                    
                    
                    
                    1 Reply Last reply Reply Quote 1
                    • jens55undefined
                      jens55 @fcwilt
                      last edited by

                      @fcwilt said in Need to lower the nozzle:

                      @jens55

                      Hi,

                      You use the </> tag.

                      Frederick

                      Thank You !

                      1 Reply Last reply Reply Quote 0
                      • jens55undefined
                        jens55
                        last edited by

                        One last comment .... the previous huge error in the Z offset was probably caused by the interaction of the macro with internal Z values of the Duet. See the post from yufanyufan here https://forum.duet3d.com/topic/16328/baby-stepping-can-it-or-can-it-not-be-permanent/55
                        One needs to be careful about using this macro as there is some strange interaction happening that I don't quite follow yet.
                        I recommend rebooting the Duet after running the macro so that everything is in sync. If you don't reboot but then home z, weird stuff happens.

                        1 Reply Last reply Reply Quote 0
                        • Kolbiundefined
                          Kolbi
                          last edited by Kolbi

                          @jens55, So one run of the macro is ok, but multiple runs are not ok?

                          Did you happen to home between runs?

                          I never ran it multiple times. Good call on M290 R0 S0 .

                          1 Reply Last reply Reply Quote 0
                          • jens55undefined
                            jens55
                            last edited by

                            With the updated macro, multiple runs seem to be ok but there is still an issue as reported in this thread :
                            https://forum.duet3d.com/topic/16328/baby-stepping-can-it-or-can-it-not-be-permanent/55?_=1596951896532
                            I now believe that an incorrect Z offset value is stored if the macro is run while the printer is doing a regular print job.
                            I have run out of time for the day and tomorrow to go any further on the diagnosis.

                            1 Reply Last reply Reply Quote 0
                            • jens55undefined
                              jens55
                              last edited by

                              The M290 R0 Z0 is courtesy of owenD and wasn't my call.

                              Kolbiundefined 1 Reply Last reply Reply Quote 0
                              • Kolbiundefined
                                Kolbi @jens55
                                last edited by

                                @jens55 Ok, so the only change was the M290 R0 Z0?

                                1 Reply Last reply Reply Quote 0
                                • jens55undefined
                                  jens55
                                  last edited by

                                  No, I also changed line 9 as it resulted in an incorrect echo output for setting the Z offset in config.g.

                                  Kolbiundefined 1 Reply Last reply Reply Quote 0
                                  • Kolbiundefined
                                    Kolbi @jens55
                                    last edited by

                                    @jens55 Ah yes, since it got changed in the line above....
                                    Good catch!

                                    1 Reply Last reply Reply Quote 0
                                    • jens55undefined
                                      jens55
                                      last edited by

                                      Exactly ... and thank you 🙂

                                      1 Reply Last reply Reply Quote 0
                                      • Kolbiundefined
                                        Kolbi
                                        last edited by Kolbi

                                        @jens55, Maybe until it is sorted - the macro should just state what to change in the config.g to be safe:

                                        ; 0:/macros/Save-Z
                                        ; This macro adds the current babystep offset to the Z trigger height and saves it to config-overide.g
                                        ; ! M501 needs to be in config.g to automatically be recalled on reset. If using multiple filament settings,
                                        ; and this is for a specific filament type, recommend placing this yielded information in the filament's config.g.
                                         
                                        if move.axes[2].babystep !=0                                ; If no babysteps are currently adjusted - exit routine
                                        	echo {"OLD: " ^ sensors.probes[0].triggerHeight ^ " NEW: " ^ sensors.probes[0].triggerHeight + (move.axes[2].babystep * -1)}
                                        	;G31 Z{sensors.probes[0].triggerHeight - move.axes[2].babystep}
                                        	echo {"Place either M501 -or- G31 Z" ^ sensors.probes[0].triggerHeight^ " in your config.g"}
                                        	;M500 P10:31                                         ; save settings to config-overide.g - G31 P31 saves trigger height, 
                                                                                                     ; trigger value, and X and Y offsets for each possible Z probe type 
                                                                                                     ; P10 parameter saves the G10 tool offsets.
                                        	;M290 R0 S0                                          ; clear babystepping 
                                         
                                        else
                                        	echo "Baby stepping is not currently employed, exiting."
                                        

                                        This way it just tells the person what it should be changed to, without inadvertently going to China - but I'm in Japan so maybe it would work for me 🙂
                                        Sorry about that btw - never thought of running it twice.

                                        jens55undefined 1 Reply Last reply Reply Quote 0
                                        • jens55undefined
                                          jens55
                                          last edited by

                                          Hopefully it will be sorted out quickly but I did indicate that the Duet should be reset after saving Z offset and saving should not happen while the printer is busy printing until things are sorted.
                                          I love the concept of saving the corrected offset value though!
                                          The rest is up to the user. Instead of 'buyer beware' it's 'user beware' 🙂

                                          1 Reply Last reply Reply Quote 0
                                          • jens55undefined
                                            jens55 @Kolbi
                                            last edited by

                                            @Kolbi said in Need to lower the nozzle:

                                            without inadvertently going to China - but I'm in Japan so maybe it would work for me 🙂

                                            No, you guys are hanging upside down on the world so your nozzle would end up going to North America (Hopefully missing the USA) 🙂

                                            .... end just like that I managed to politicize the thread 🙂

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