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

    firmware retraction

    Scheduled Pinned Locked Moved Solved
    Using Duet Controllers
    5
    10
    799
    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.
    • bastienundefined
      bastien
      last edited by bastien

      hello, I wanted to test the firmware retraction but I have a problem, with the same settings as my slicer, my filament moves back with each retraction to the point where it no longer feeds the tool, M207 S5 F3000 Z0.1

      Circuit: Duet 2 WiFi (2WiFi)
      Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.0beta7+7 (2022-01-14)
      Duet WiFi Server Version: 1.23

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

        Are you still using wipe or coast in the slicer?

        Can you post your config.g?

        Are you sure you have firmware retraction enabled in the slicer?

        @bastien said in firmware retraction:

        3.4.0beta7+7

        You may want to update to 3.4 RC2

        Z-Bot CoreXY Build | Thingiverse Profile

        1 Reply Last reply Reply Quote 0
        • bastienundefined
          bastien
          last edited by

          I enabled firmware retraction in cura
          after M207
          Tool 0 retract/reprime: length 5.00/5.00mm, speed 50.0/50.0mm/sec, Z hop 0.10mm

          1 Reply Last reply Reply Quote 0
          • droftartsundefined
            droftarts administrators
            last edited by

            @bastien sounds like you might be using absolute rather than relative extrusion in the slicer.

            Ian

            Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

            bastienundefined 1 Reply Last reply Reply Quote 0
            • bastienundefined
              bastien @droftarts
              last edited by

              @droftarts I had thought about it, but I am in relative extrusion, and I have M83 at the beginning of my config.g, when the retraction is managed by the slicer, everything is fine, but not the firmware

              deckingmanundefined 1 Reply Last reply Reply Quote 0
              • deckingmanundefined
                deckingman @bastien
                last edited by

                @bastien Can you make the gcode file that you are trying to print available. Or at least a section of it which shows a few retract/unretract cycles. It might also help if you post your complete config.g file as well as your slicer start code.

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

                bastienundefined 1 Reply Last reply Reply Quote 0
                • bastienundefined
                  bastien @deckingman
                  last edited by

                  @deckingman
                  my config.g

                  G90                                            ; send absolute coordinates...
M83                                            ; ...but relative extruder moves
M550 P"Predator"                               ; set printer name
M665 L440.000 R221 B185.0 H456                       ; Set delta radius, diagonal rod length, printable radius and homed height M665 L415.000 R222.5 B185.0 H486  ; rod alu
M666 X0 Y0 Z0 A0.00 B0.00                                  ; put your endstop adjustments here, or let auto calibration find them

; Network
M552 S1                                        ; enable network
M586 P0 S1                                     ; enable HTTP
M586 P1 S1                                     ; disable FTP
M586 P2 S0                                     ; disable Telnet

; Drives
M569 P0 S0                                     ; physical drive 0 goes forwards
M569 P1 S0                                     ; physical drive 1 goes forwards
M569 P2 S1                                     ; physical drive 2 goes forwards
M569 P3 S1                                     ; physical drive 3 goes forwards
M584 X0 Y1 Z2 E3                               ; set drive mapping
M350 X16 Y16 Z16 E16 I1                        ; configure microstepping with interpolation
M92 X160 Y160 Z160 E392.5 ; set steps per mm
M566 X1000 Y1000 Z1000 E1000       ; set maximum instantaneous speed changes (mm/min)
M203 X12000 Y12000 Z12000 E1200    ; set maximum speeds (mm/min)
M201 X3000 Y3000 Z3000 E3000       ; set accelerations (mm/s^2)
M906 X1000 Y1000 Z1000 E1000 I30                ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                        ; Set idle timeout



; Axis Limits
M208 Z0 S1                                     ; set minimum Z

; Endstops
M574 X2 S1 P"xstop"                            ; configure active-high endstop for high end on X via pin xstop
M574 Y2 S1 P"ystop"                            ; configure active-high endstop for high end on Y via pin ystop
M574 Z2 S1 P"zstop"                            ; configure active-high endstop for high end on Z via pin zstop

; Z-Probe
M558 P5 C"e0stop" H8 F120 T6000            ; set Z probe type to switch and the dive height + speeds
M558 H10                                       ;*** Remove this line after delta calibration has been done and new delta parameters have been saved
G31 P500 X0 Y0 Z14.95                        ; set Z probe trigger value, offset and trigger height
M557 R175 S20                               				; Define mesh grid
G29 S1                                  

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4300 ; 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 B1 S1.00                               ; enable bang-bang mode for the bed heater and set PWM limit
M140 H0                                        ; map heated bed to heater 0
M143 H0 S80                                    ; set temperature limit for heater 0 to 80C
M308 S1 P"e0temp" Y"thermistor" T100000 B4300  ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1                           ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.00                               ; disable bang-bang mode for heater  and set PWM limit

; Fans
M950 F0 C"fan0" Q500                           ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1                                 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500                           ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H1 T45                              ; set fan 1 value. Thermostatic control is turned on
 

; Tools
M563 P0 D0 H1 F0                               ; define tool 0
G10 P0 X0 Y0 Z0                                ; set tool 0 axis offsets
G10 P0 R0 S0                                   ; set initial tool 0 active and standby temperatures to 0C

; Retraction
;M207 S4.0 F5000 R-0.025 T2500 Z0.5
M207 S6.5 F3700 Z0.1


; Custom settings are not defined
; Custom settings are not configured
;M572 D0 S0.1												; Pressure Advance
;M591 D0 P2 C"e1stop" S0											; Activate filament sensor
M404 N1.75 													; Set for print monitor
;M592 D0 A0.07772 B-0.00029 		; Nonlinear extrusion. Set parameters for extruder drive 0
; Miscellaneous
M575 P1 S1 B57600                              ; enable support for PanelDue

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

                    Could you show photo examples of what results you get with both?

                    Z-Bot CoreXY Build | Thingiverse Profile

                    1 Reply Last reply Reply Quote 0
                    • bbergerundefined
                      bberger
                      last edited by

                      @phaedrux said in firmware retraction:

                      @bastien said in firmware retraction:

                      3.4.0beta7+7

                      You may want to update to 3.4 RC2

                      this. the 3.4 betas are known (and confirmed) to have a retraction issue..

                      bastienundefined 1 Reply Last reply Reply Quote 0
                      • bastienundefined
                        bastien @bberger
                        last edited by

                        @bberger said in firmware retraction:

                        this. the 3.4 betas are known (and confirmed) to have a retraction issue..

                        it's ok after update thanks

                        1 Reply Last reply Reply Quote 0
                        • Phaedruxundefined Phaedrux marked this topic as a question
                        • Phaedruxundefined Phaedrux has marked this topic as solved
                        • First post
                          Last post
                        Unless otherwise noted, all forum content is licensed under CC-BY-SA