Strange retraction behavior on Ender 3 v2

CRCinAU · 9 August 2022 11:00

Interesting. I’m not sure if this is you, but there seems to be an issue logged about something possibly similar:

[BUG] Duplicated retraction moves

opened 09:14PM - 08 Aug 22 UTC

### Did you test the latest `bugfix-2.1.x` code? Yes, and the problem still e…xists. ### Bug Description When I try to use slicer retraction (CUra) and a lot of duplicated moves appear. I try too compile v2.1.1 version with firmware-retraction enable, put zero in all firmware-retraction codes M208 and M207 and disable firmware-retraction in slicer, but not work. With firmware-retraction enable, works fine, but I want to use slicer retraction. ### Bug Timeline new bug ### Expected behavior Use slicer retraction without duplicated moviments. ### Actual behavior _No response_ ### Steps to Reproduce 1. Disable firmware-retraction in slicer (Cura). 2. Try to use slicer retraction. 3. Print anyone model. ### Version of Marlin Firmware 2.1.1 ### Printer model Creality Ender 3 v2 4.2.2 ### Electronics Not ### Add-ons Not ### Bed Leveling _No response_ ### Your Slicer Cura ### Host Software OctoPrint ### Don't forget to include - [X] A ZIP file containing your `Configuration.h` and `Configuration_adv.h`. ### Additional information & file uploads Video with bug: https://www.youtube.com/watch?v=4oyjgjOf9HE&t My gcode: https://drive.google.com/file/d/1Y9qObb9zp69XtNMwor9w32rBhZzDM-O2 My firmware codes: https://drive.google.com/drive/folders/1PIqez62yKWW60lRmoG_nDRWTuX4JqjuB?usp=sharing My start script: ``` ; Script based on an original created by tjjfvi (https://github.com/tjjfvi) ; An up-to-date version of the tjjfvi's original script can be found ; here: https://csi.t6.fyi/ ; Note - This script will only work in Cura V4.2 and above! ; --- Global Settings ; layer_height = {layer_height} ; smooth_spiralized_contours = {smooth_spiralized_contours} ; magic_mesh_surface_mode = {magic_mesh_surface_mode} ; machine_extruder_count = {machine_extruder_count} ; --- Single Extruder Settings ; speed_z_hop = {speed_z_hop} ; retraction_amount = {retraction_amount} ; retraction_hop = {retraction_hop} ; retraction_hop_enabled = {retraction_hop_enabled} ; retraction_enable = {retraction_enable} ; retraction_speed = {retraction_speed} ; retraction_retract_speed = {retraction_retract_speed} ; retraction_prime_speed = {retraction_prime_speed} ; speed_travel = {speed_travel} ; Ender 3 Custom Start G-code M117 Bed up to temp M140 S{material_bed_temperature_layer_0} ; Set Heat Bed temperature M190 S{material_bed_temperature_layer_0} ; Wait for Heat Bed temperature M117 Pre-heating extruder M104 S{material_print_temperature_layer_0} ; Set Extruder temperature G28 ; Home all axes M117 Auto bed-level ; G29 0; Auto bed-level (BL-Touch) G92 E0 ; Reset Extruder M117 Wating extruder temp M109 S{material_print_temperature_layer_0} ; Wait for Extruder temperature M900 K0 M209 S0 G1 Z1.0 F3000 ; move z up little to prevent scratching of surface G1 X0.1 Y20 Z0.3 F5000.0 ; move to start-line position M117 Prime hotend started G1 X0.1 Y200.0 Z0.3 F1500.0 E15 ; draw 1st line G1 X0.4 Y200.0 Z0.3 F5000.0 ; move to side a little G1 X0.4 Y20 Z0.3 F1500.0 E30 ; draw 2nd line G92 E0 ; reset extruder G1 Z1.0 F3000 ; move z up little to prevent scratching of surface M117 Print started ; End of custom start GCode ```

EDIT: Scratch that - I just noticed that you’re the same person - as the google drive links are the same

Interestingly, in the G-Code you generated, there are no retractions at all the from the slicer.

It is doing wipes, as such:

G1 X106.1 Y106.1 E13.78001
G1 X118.9 Y106.1 E14.24831
G1 X118.9 Y118.9 E14.71661

I wonder if you could re-slice with the extruder set to relative instead of absolute so it’d be a bit clearer in what its generating?