Jagged lines
-
I was just stating a new print and noticed super jagged edges on the 1st layer infill. Furthermore, the filament was not sticking to the bed like I am used to.
Earlier today, I configured pressure advance for the first time, so I first thought that was what was causing the issue. Disabling PA did not solve it however. Long story short I still some positive Z-babystepping offset (+0.30mm) from a previous print that had some issues.
It is obvious that due to the lack of squish, bed adhesion was lacking. The jagged-ness of the extruded lines are harder to explain for me. My guess would be that since the nozzle was that high, and thus not squished, the filament was kind of 'drizzled' on the bed before being very lightly pressed to the bed. When extruding in mid air the extruded filament does not come out of the nozzle perfectly straight either due to imperfections and nozzle wear.
One takeaway from this post could be that it seems weird to me that babystepping is persistent between prints. If you need a permanent offset, you do that in calibration right.
EDIT: The main reason shared this is as reference for other people who might be struggling with similar symptoms.
-
@Nxt-1 said in Jagged lines:
it seems weird to me that babystepping is persistent between prints.
People also complained that baby stepping wasn't persistent between homing, and even now people want it to be persistent between power cycles! Can't please everyone, but thankfully you can use gcode to clear baby stepping in homeall, or the slicer end gcode or cancel.g, or even in start.g before the print starts. I use that to reset a lot of values that may have been changed during a print.
-
@Phaedrux said in Jagged lines:
@Nxt-1 said in Jagged lines:
it seems weird to me that babystepping is persistent between prints.
People also complained that baby stepping wasn't persistent between homing, and even now people want it to be persistent between power cycles! Can't please everyone, but thankfully you can use gcode to clear baby stepping in homeall, or the slicer end gcode or cancel.g, or even in start.g before the print starts. I use that to reset a lot of values that may have been changed during a print.
Yeah, I have seen the recent discussions about it's persistence. Lets not continue that here
However, I do absolutely love your idea about always resetting it automatically. Thanks for sharing that.
