RepRapFirmware 3.2beta3.2 released
-
Please test that file again with beta 4 when it comes out (probably tomorrow). If the problem persists, post the file where I can retrieve it.
-
OK, will do.
This morning I did reslice with my usual settings (relative extrusions, usage of G10, cap on resolution), print is currently at 12.5% and progressing fine, hiccups counter stays at 0.
My gut feeling says that the huge amount of short segments in the original code is what causes the issues.In advance; the G-code file can be found here: https://www.icecoldcomputing.com/directlink/stackable_OD5.5_ID3.2_H3_bush.zip
-
@DaBit, 3.2beta4 for Duet WiFi is released now.
-
from the changelog.
Efficiency improvements to TMC2208/2209 drivers for both main and tool boards
Which board uses the TMC2208? did you mean TMC2224?
-
@Veti said in RepRapFirmware 3.2beta3.2 released:
from the changelog.
Efficiency improvements to TMC2208/2209 drivers for both main and tool boards
Which board uses the TMC2208? did you mean TMC2224?
Yes, I did. I think of the TMC2224 as a 2208 (it's the same with a different pinout).
-
@dc42 said in RepRapFirmware 3.2beta3.2 released:
@DaBit, 3.2beta4 for Duet WiFi is released now.
Makes no difference. Skirt goes well, once the printing of the circles starts the Duet hangs (cancel print does not work, emergency stop does, changing temperatures in DWC does too)
-
You've posted the print file, but I need your config.g file too.
-
@dc42 : Here is the entire bundle, directly downloaded from the printer:
https://www.icecoldcomputing.com/directlink/DaBit3D_config_26nov2020.zip
-
Thanks, that's on my list to look into.
-
It is not an issue for me. I suspect the large amount of short segments simply choking the Duet. When using gcode with sane segment length the Duet hums along fine.
But still, it should slow down to a crawl, but not hang. -
Absolutely right, it should not hang.
-
I believe this is now fixed in the new RRF 3.2bete4+3 binaries at https://www.dropbox.com/sh/tehhdvunh0pgr7q/AADgJ4Qj7W18MYaRRNNDdhpwa?dl=0.
-
not fixed or 'now fixed'?
I will give it a try, will report back...
-
The issue seems resolved.
I did not let the print finish since that's only a waste of plastic and I don't think it proves anything, but after 63000 moves it was still printing fine.
-
Thanks for confirming.