Muss mit 75 Prozent Extrusion drucken

Wolfgang.Klein

@resam drucke dann auch mit 80 mm pro s

Wolfgang.Klein

@resam der befehl m404 N1.75 D0.4 verursacht die Probleme mit der überextrussion. Wenn dieser Befehl aktiv ist dann stoppt er bei der 2. Schicht weil,die Düse vom filament dicht gedrückt wird. Danke für deine Unterstützung. Da hätte ich nie drauf getippt. Wurde so von der Firma RatRig als Befehl in der config.g vorgeschlagen....Danke

Wolfgang.Klein

@resam vielleicht habe ander das gleiche Problem. Dann kann die Info ja nützlich sein.

resam

@dc42 it seems that M404 is causing massive over-extrusion. @Wolfgang-Klein is using it based on his printer's manufacturer's config advice from https://v-core.ratrig.com/firmware/#configg

I'm not familiar with this command, but https://duet3d.dozuki.com/Wiki/M404 reads like it should not affect anything apart from progress reporting (maybe?). What is it supposed to do - and what is it really doing?

The only references in the code I could find point to src/Storage/FileInfoParser.cpp which seems inconspicuous...

oliof

Bitte nochmal prüfen ob im Slicer Volumetric Extrusion eingeschaltet ist oder nicht.

oliof

@resam if you enter M404 on a machine where it's not set in config.g, you will see that it defaults to 1.75mm. So it would be the nozzle diameter that would affect extrusion? Either way sounds like a bug. It's worth noting that with 3.4b4 the nozzle diameter parameter is gone.

I will talk to ratrig to get the M404 line removed.

Wolfgang.Klein

@oliof vielen Dank, dass ist eine gute Idee, so findet ein Feedback und eine Fehlerbehebung statt. Tolle Comunity. Liebe Grüße Wolfgang

oliof

M404 line removed from reference configuration on the ratrig site.

Wolfgang.Klein

@oliof danke, so solls laufen. Noch eine guten Start in Neue Jahr und vielen Dank an alle die mitgeholfen haben dieses Problem zu lösen. LG Wolfgang

dc42

@resam I have checked the code and verified that the M404 command doesn't use the D parameter, and the N parameter is used only by the print monitor in converting filament volume to filament length, for those slicers that report filament volume used instead of filament length used. Furthermore, the default filament width is 1.75mm, the same as in the command that @Wolfgang-Klein was using.

@Wolfgang-Klein said that he also removed the M200 command. M200 activates volumetric extrusion, which requires the slicer to specify the E coordinate in mm^3 of filament instead of mm. However, RRF defaults to non-volumetric extrusion when starting a print (so that a GCode file that was sliced using volumetric extrusion must use the M200 command in its preamble), so this doesn't really explain it either.

bberger

@dc42 for what it's worth I toyed around with volumetric extrusion in SuperSlicer a few years back and I had the exact same behavior. That was still RFF 2.x I think (or maybe even RRF 3.0). Since then I figured it's just a buggy hell and I won't ever need it anyways - never looked back or tried to find the root cause..