With new M600 behavior in 2.7.2, is this still the correct custom color change gcode for MK3 AND MK4?
 
Notifications
Clear all

With new M600 behavior in 2.7.2, is this still the correct custom color change gcode for MK3 AND MK4?  

  RSS
TeeBell
(@teebell)
Trusted Member
With new M600 behavior in 2.7.2, is this still the correct custom color change gcode for MK3 AND MK4?

PrusaSlicer 2.7.2 announced a change in the behavior of M600 where by it will wait to start the color change process until after moving to the new location, helping to prevent the filament blob being left behind on a clearly visible part of the model. The blob is much bigger and worse on the MK4 than the MK3. There are plenty of threads with pics demonstrating it. The new behavior helps but in my case is not a perfect fix because if the next layer bring printed starts with a thin outline or corner/point the blob is still visible under the extruded filament.

It got me to thinking that I believe this gcode (screenshot attached) entered for color change was not a part of the original profile for the MK3, I believe.

1) What exactly is it doing?

2) Do we think it is still needed with this new behavior in place?

 

Posted : 15/03/2024 3:42 pm
Share: