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

    Help with retraction. Retraction not working

    Scheduled Pinned Locked Moved
    Tuning and tweaking
    5
    26
    1.1k
    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.
    • DIY-O-Sphereundefined
      DIY-O-Sphere @Paskal
      last edited by

      @Paskal said in Help with retraction. Retraction not working:

      Yes, retraction works in the printer web interface

      Have you checked the slicer G-code?
      Can you provide a sample?

      (UTC+1)

      1 Reply Last reply Reply Quote 0
      • Paskalundefined
        Paskal
        last edited by

        four_square_cons.gcode

        DIY-O-Sphereundefined 1 Reply Last reply Reply Quote 0
        • DIY-O-Sphereundefined
          DIY-O-Sphere @Paskal
          last edited by DIY-O-Sphere

          @Paskal
          Where do you set the retraction settings?
          I have base values in the config. And I overwrite them with the g-code of the filament settings.
          Have you set them manually in DWC before starting a print?

          (UTC+1)

          1 Reply Last reply Reply Quote 0
          • Paskalundefined
            Paskal
            last edited by

            I have retraction settings in the config.g

            DIY-O-Sphereundefined 1 Reply Last reply Reply Quote 0
            • DIY-O-Sphereundefined
              DIY-O-Sphere @Paskal
              last edited by

              @Paskal said in Help with retraction. Retraction not working:

              I have retraction settings in the config.g

              Not in the old one.....

              (UTC+1)

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

                you still need to enable retraction in the slicer and then tick the box for firmware retraction.
                The slicer then inserts G10 and G11 when retraction is required.
                Otherwise, how will the firmware know?

                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

                DIY-O-Sphereundefined 1 Reply Last reply Reply Quote 0
                • DIY-O-Sphereundefined
                  DIY-O-Sphere @jay_s_uk
                  last edited by

                  @jay_s_uk said in Help with retraction. Retraction not working:

                  The slicer then inserts G10 and G11

                  It's in the g-code
                  I have checked that...

                  (UTC+1)

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

                    Part of the problem is the extremely long retraction, extremely low speed values for Z, and using Z hop. Z hop will always lead to a lot of stringing.

                    Try this for your settings

                    M566 X700 Y700 Z60 E3000            	   ; set maximum instantaneous speed changes (mm/min)
                    M203 X6000 Y6000 Z600 E6000       	   ; set maximum speeds (mm/min)
                    M201 X900 Y900 Z200 E3000            	   ; set accelerations (mm/s^2)
                    M207 P0 S1.5 R0 F3600 T2600 Z0 ; retraction
                    M572 S0 S0.05 ; pressure advance
                    

                    Z-Bot CoreXY Build | Thingiverse Profile

                    1 Reply Last reply Reply Quote 0
                    • Paskalundefined
                      Paskal
                      last edited by

                      @Phaedrux said in Help with retraction. Retraction not working:

                      M207 P0 S1.5 R0 F3600 T2600 Z0 ; retraction M572 S0 S0.05 ; pressure advance

                      I changed the settings as recommended. I attach a photo, it seems better to me

                      IMG_20210118_211946.jpg

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

                        Ok, now try calibrating the extruder: https://duet3d.dozuki.com/Guide/Ender+3+Pro+and+Duet+Maestro+Guide+Part+4:+Calibration/40#s165

                        Z-Bot CoreXY Build | Thingiverse Profile

                        Paskalundefined 1 Reply Last reply Reply Quote 0
                        • Paskalundefined
                          Paskal
                          last edited by

                          Okay, I'll try. I calibrated it on PETG. But now I have PLA there, so I'll try again

                          1 Reply Last reply Reply Quote 0
                          • Paskalundefined
                            Paskal @Phaedrux
                            last edited by

                            @Phaedrux After calibration the result is the same. I tried to add length + speed and no change.

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

                              Photo of your extruder setup?
                              Is everything assembled correctly?
                              Do you have some fresh PLA to test with?

                              Z-Bot CoreXY Build | Thingiverse Profile

                              DIY-O-Sphereundefined 1 Reply Last reply Reply Quote 0
                              • DIY-O-Sphereundefined
                                DIY-O-Sphere @Phaedrux
                                last edited by

                                @Phaedrux
                                As I mentioned yesterday, there is an issue in the provided config. Look at the configuration of H1.

                                ; Heaters
                                M308 S0 P"bedtemp" Y"thermistor" T100000 B3950     ; configure sensor 0 as thermistor on pin bedtemp
                                M950 H0 C"bedheat" T0                              ; create bed heater output on bedheat and map it to sensor 0
                                M307 H0 A167.0 C982.2 D5.1 S1.00 V23.1 B0          ; enable bang-bang mode for the bed heater and set PWM limit
                                M140 H0                                            ; map heated bed to heater 0
                                M143 H0 S120										; set temperature limit for heater 0 to 120C
                                
                                M308 S1 P"spi.cs1" Y"rtd-max31865" ; define temperature sensor number 4 as a PT100
                                M950 H1 C"e0heat" T1                               ; create nozzle heater output on e0heat and map it to sensor 1
                                M307 H0 B1 S1.00  
                                M143 H1 S280                                       ; set temperature limit for heater 1 to 280C
                                
                                

                                I'm not sure if it is already corrected or not. Nor what RRF is interprets in such a case.
                                But I know that higher temperatures lead to ozzing.

                                (UTC+1)

                                1 Reply Last reply Reply Quote 0
                                • Paskalundefined
                                  Paskal
                                  last edited by

                                  Here is a photo of the hotend. Shouldn't the M143 have anything to do with it stringing or confusing?

                                  IMG_20210120_150621.jpg

                                  DIY-O-Sphereundefined 1 Reply Last reply Reply Quote 0
                                  • DIY-O-Sphereundefined
                                    DIY-O-Sphere @Paskal
                                    last edited by DIY-O-Sphere

                                    @Paskal
                                    Have a look on line 10, that should be H1. The line is overwriting the tunning of line 4.
                                    So there is no M307 set for H1. Maybe RRF sets standard values, but I don't know.
                                    You should also perform tunning for H1.

                                    (UTC+1)

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