Weird offset / missteps on Z axis or extrusion problems ?
Hello,
A new printing problem recently appeared on my MK3S, with weird offsets appearing on walls, but in every axes...
It's like if multiple layers were done without going up on Z ?
Has anyone experienced this before ?
Here is the slicer project : cube-40-40-40
Thanks for your help!
Nicolas.
RE: Weird offset / missteps on Z axis or extrusion problems ?
Look like a mechanical problem. Is it reproducable the same or random? What does the cube look like when printed in vase mode?
Are you pinting in normal mode with collision detection?
If at first you don't succeed, skydiving is not for you.
Find out why this is pinned in the general section!
RE: Weird offset / missteps on Z axis or extrusion problems ?
PS: What's this custom g-code before layer change in ypur project doing? (Nothing I'd guess):
M220 S{if layer_num < 1}50{else}100{endif} ; M220 adjusts feed rates to 100% for first layer
If at first you don't succeed, skydiving is not for you.
Find out why this is pinned in the general section!
RE: Weird offset / missteps on Z axis or extrusion problems ?
I thought it was a mechanical issue, but when sliced with Cura instead of PrusaSlicer, the print was coming fine...
I then flashed the latest firmware, cleaned-reinstalled Prusaslicer and its settings, did a factory reset and a full calibration.
Now the print is fine again.
Thanks!
RE: Weird offset / missteps on Z axis or extrusion problems ?
Yes, it's just some GCode to slow down the print only for the first layer.
PS: What's this custom g-code before layer change in ypur project doing? (Nothing I'd guess):
M220 S{if layer_num < 1}50{else}100{endif} ; M220 adjusts feed rates to 100% for first layer
RE:
Yes, it's just some GCode to slow down the print only for the first layer.
PS: What's this custom g-code before layer change in ypur project doing? (Nothing I'd guess):
M220 S{if layer_num < 1}50{else}100{endif} ; M220 adjusts feed rates to 100% for first layer
Yes, but it's not...
The "if layer_num < 1" condition is never met since the first layer is layer 1 so no layer is <1 and even if you'd change that condition to <2 (or =1) it would not work as intended since the first time this will be evaluated is literally "before layer change" which is after the first layer has been printed...
If at first you don't succeed, skydiving is not for you.
Find out why this is pinned in the general section!
RE: Weird offset / missteps on Z axis or extrusion problems ?
FYI layer_num is zero based, so the first layer will have layer_num==0.
You can easily test it.
RE:
FYI layer_num is zero based, so the first layer will have layer_num==0.
You can easily test it.
No, it's not, and yes you can easily test it:
Slice your own project from above, save and open the gcode-file, find the first occurrence of "; M220 adjusts feed rates to 100% for first layer", notice the fact that the line begins with "M220 S100" as do all the other occurrences of this line... Note that this is still the first layer, since the "G1 Z.4 F720" command for moving to the second layer is still a few lines down.
If at first you don't succeed, skydiving is not for you.
Find out why this is pinned in the general section!
RE: Weird offset / missteps on Z axis or extrusion problems ?
You're right, thanks, I'll fix that too!