Random filament changes added
 
Benachrichtigungen
Alles löschen

Random filament changes added  

  RSS
Akentut
(@akentut)
Active Member
Random filament changes added

Printing a small item, single color, no filament change with a small support block. The gcode is putting in filament changes at random locations which isn't necessary. I'm using a MK3S with MMU2S. I bypassed the MMU (having issues with it). But I've looked at the code and see where it would stop the print for filament change. Not sure why this is happening.

Here is a snip of the code where I think it's stopping for filament change.

G1 X124.502 Y112.684 E0.01356
G1 X124.052 Y112.234 E0.02001
M204 S1000
; stop printing object Cpap Clip4.stl id:0 copy 0
M106 S84.15
;LAYER_CHANGE
;Z:0.3;HEIGHT:0.1
;BEFORE_LAYER_CHANGE
G92 E0.0;0.3
;WIPE_START
G1 F8640.000
G1 X124.502 Y112.684 E-0.14690
G1 X124.915 Y112.563 E-0.09956
G1 X124.221 Y111.869 E-0.22661
G1 X124.221 Y111.334 E-0.12351
G1 X124.722 Y111.834 E-0.16342
;WIPE_END
G1 E-0.04000 F2100.000
G1 Z0.600 F10800.000
;AFTER_LAYER_CHANGE
;0.3; printing object Cpap Clip4.stl id:0 copy 0
G1 X123.857 Y113.025G1 Z0.300
G1 E0.80000 F2100.000
M204 S600
;TYPE:Perimeter
;WIDTH:0.45
G1 F2700.000
G1 X123.857 Y91.863 E0.37704
G1 X122.602 Y91.863 E0.02236
G1 X122.602 Y91.024 E0.01494
G1 X134.826 Y94.593 E0.22689

Veröffentlicht : 03/11/2021 4:11 pm
Neophyl
(@neophyl)
Illustrious Member

There are no filament change gcodes in that snippet.  Those would be M600 for a prusa printer.  That looks like just normal gcode.  Movements, extrusions, speed changes etc.  You aren't thinking the stop printing xxxx means a filament change are you ?  As it doesn't.  It just means its stopping printing the object, as its about to do a wipe, then a layer change and then it carries on printing the next layer.  The comments are there to indicate the process its doing at that point as well as the object its printing.

Veröffentlicht : 03/11/2021 5:18 pm
FoxRun3D
(@foxrun3d)
Famed Member

So are you actually experiencing filament changes? In which case I don't think they're triggered by actual GCODE commands but rather a misaligned filament sensor.

Formerly known on this forum as @fuchsr -- until all hell broke loose with the forum software...

Veröffentlicht : 03/11/2021 5:39 pm
Akentut
(@akentut)
Active Member
Themenstarter answered:
Filament change fixed.

Ok Problem solved. What was happening was when I choose to add the block to add support for an overhang, it asked for bridging which I accepted. When I removed that option the filament change stopped.

Not sure if that was thinking I had to change filament to place the support material.

Tnx for the replies.

 

Veröffentlicht : 03/11/2021 10:15 pm
FoxRun3D
(@foxrun3d)
Famed Member

Glad you're back in business even though that explanation makes little sense to me. I have no idea why supports/bridging could possibly trigger filament swaps. 

Should the problem creep up again, the best way to get help here is to export the project from PrusaSlicer as a 3mf file, then zip it (important! Or the forum software will not accept it) and upload it here. This way, we can look at all your settings to see what's going on. 

Formerly known on this forum as @fuchsr -- until all hell broke loose with the forum software...

Veröffentlicht : 03/11/2021 10:29 pm
Neophyl
(@neophyl)
Illustrious Member

Without the saved project we cant know, but as the user stated they had a mmu they have bypassed its quite possible that support is configured to use a different extruder. 

Veröffentlicht : 03/11/2021 10:42 pm
FoxRun3D
(@foxrun3d)
Famed Member

@neophyl — Good catch!

Formerly known on this forum as @fuchsr -- until all hell broke loose with the forum software...

Veröffentlicht : 03/11/2021 11:55 pm
Teilen: