Printer Model: Custom Single Arm Cartesian
MCU / Printerboard: MKS Gen L V1.0 klippy.log klippy.log (63.4 KB)
Fill out above information andin all cases attach yourklippy.logfile (use zip to compress it, if too big). Pasting yourprinter.cfgis not needed Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there
Describe your issue:
I keep getting these strange verticle lines in my print. I have 2 identicle printers and one prints fine and the other has this issue. I do have some ghosting overall but I can live with that.
In the photo with the two parts those are printed from two different machines.
Ive tried changing infill percentages without any resolve. Ive also oriented the part in different ways on the print bed and have the same results.
Thanks for the suggestion. I have watched the print a couple of times now. I cant see any changes during printing. Im printing at 200mm/s and dont notice it slowing down or stopping at the verticle lines. I have tried to turn down my printer to 50mm/s and the errors became more pronounced.
If it’s a physical artifact on the print, it must have a physical cause. You need to determine what is happening before you can figure out why it’s happening. Maybe a general 3d printing forum would be more helpful in troubleshooting.
I dont beleive that there is an issue in the physical print itself. I can print the same sliced file in a cloned printer and I dont get these errors. I uploaded an image of a the same print from 2 different machines. Each machine is built the same as the other.
I have a feeling that there is something to do with Klipper. The only difference between the printers is one has a rapsberry pi 2 and the other a raspberry pi 3. The rasberry pi 2 set up is producing the issue.
To start my prints I simply upload a sliced file from simplify3d to octoprint. I have some commands in my start in end gcode that are specific to each printer. Ie Z offset. Nothing special beyond that.
If the slicer preview does not show such issues could you directly print it from the printer via SD card or something like that to exclude OctoPrint?
Though it would be strange that a software issue properly stacks up like this.
Does your printer always print such “defects” or are there models it prints fine?
Maybe you can print a cylinder or cube in vase/spiralized mode to check for some mechanical issues.
If yes, it might happen that Octoprint is actually bypassing the virtual_sdcard feature.
You can check by starting a print and cancelling it again with M112. In the klippy.log you should find commands M23 and M24 if it is used.
If not then you might be printing over the regular serial interface which might suffer from degraded performance.