resume redundant extrusion
-
@Notepad okay, reading the word 'double' sent me to do more tests. Indeed - the overextruded amount seems to depend on what's written oin resume.g, but not exactly double - it seems like tripple to me. That is, changing "G1 E10 F300" to E1 (1mm) makes the additional extrusion something like 2mm. If this command is completely removed, there's no extrusion before or after the G4. Hope this could give some insight.
-
@bugpwr I'm looking at your debug trace again and now I can see the extra extrusion. Following the G1 E10 command there are 7830 microsteps of extrusion at a top speed of 3915 microsteps/sec (5mm/sec) with acceleration at the start and deceleration at the end. Then there are another 7830 microsteps of extrusion at a top speed of 15660 microsteps/sec (20mm/sec), again with acceleration at the start and deceleration at the end.
I will take a look at the 3.5.4 source code to identify the reason for this. Meanwhile, please can you try upgrading to 3.6.0-beta.3. There have been fairly substantial changes to the movement code in that version since beta 2.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 this is not 3.5.4, this was actually the latest beta2 (I will try with beta3 later today).
-
@bugpwr I think I found the problem. It only affects Duet 2 and Duet Maestro. Please try the 3.5.4+1 firmware binary at https://www.dropbox.com/scl/fo/xx7tpppxwbirz4zm9yr0o/AEb98egoCKGGVfCydwsFit8?rlkey=q1eg5g59zt1rbr9wqam80zygx&dl=0.
Edit: the same bug is present in the Duet 3 builds of 3.6.0-beta.3.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 looks like it is completely solved in this fix.
-
@bugpwr thanks for confirming. I will generate a new 3.6beta3+1 for Duet 2 when I have fixed another bug.
-
@bugpwr I've put a 3.6.0-beta.3+1 build that includes this fix at https://www.dropbox.com/scl/fo/bx70c7u0bshq79ez83mnn/AKMj4UCEimtQuGYxRj_d0ew?rlkey=7yiq3x5fcae3v2ogslfocx1op&dl=0.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
undefined dc42 has marked this topic as solved
-
@dc42 many thanks, the beta3+1 update works like a charm!!
(completely unrelated: speaking of 2.85mm systems, I don't want to bother you with a minor thing, but it would be awesome if M404 would upate move.extruders[].filamentDiameter. As of now, DWC always shows incorrect volumetric rate for 2.85 machines) -
by the way, I am having some (unrelated) motion troubles with the beta3+1. On a couple of incidents homing commands got stuck (e.g. G1 H1 Y480 F5000) I did not investigate further.
The screenshot attached popped up mid printing.
-
@bugpwr best to open a separate thread for the separate issue so this can be marked solved.
-
@bugpwr said in resume redundant extrusion:
@dc42 many thanks, the beta3+1 update works like a charm!!
(completely unrelated: speaking of 2.85mm systems, I don't want to bother you with a minor thing, but it would be awesome if M404 would upate move.extruders[].filamentDiameter. As of now, DWC always shows incorrect volumetric rate for 2.85 machines)You can use M200 S0 D### to set the filament diameter to ###. Unlike M404, M200 allows you to set per-extruder filament diameters.
-
@bugpwr said in resume redundant extrusion:
by the way, I am having some (unrelated) motion troubles with the beta3+1. On a couple of incidents homing commands got stuck (e.g. G1 H1 Y480 F5000) I did not investigate further.
That is the second line of a 2-line error message. The first line includes a single-digit error code, which I need to know to investigate this further.
