Hi all again. Looking for help on improving print quality. 3 Weeks now that I try to get to print the Benchy perfect, but I can not get rid of the issues seen in the image. Where can I look further for this? Steps are calibrated, tried temperature from 180 to 220. And a lot of fiddling around. Printer is a Prusa i3 Hephestos, with solid aluminium frame.
What are you using as printer host? Maybe the communications hangs inbetween, so the hotend stops for a very short time and ozzes a bit? And do you use retraction?
Check your heat. May be a little too hot. Also, if the filament has water in it the water evaporates and can cause pressure forcing extra plastic out the nozzle.
@Volker_Klaffehn Using Octoprint. But yes, the hotend seems to be slow sometimes or stops. Yes. I will put the gcode on the sd card and give it a try again.
@Michael_Spano_Jr_Ama I trief from 180 to 220 degress. Make no difference on the “blobbing”, only on stringing, which is best at 200-210. Tried 3 different filaments, all stored with silicagel, as I had issues with water vapor in the past.
Give us all facts: PLA temperature,etc…
Download this 6 PDF’s and control all adjustments.
http://www.3d-printerstore.ch/3D-Drucker/bq-Witbox-Prusa-3D-Drucker/bq-PRUSA-i3-Hephestos-red::509.html?language=de
@Erich_HaHaOh Sorry for missing that. PLA (Colorfabb), 0.2 layer height, 210°C Hotend, 50°C Bed, at around 40mm/s. Retraction 4mm. Want me to upload the cura settings somewhere? Firmware is here https://github.com/lobermann/Marlin/tree/PrusaI3Hephestos_update.
Will have a read threw the PDF now. Thanks.
@Erich_HaHaOh Also, it’s only the frame and the printed parts (most of them) that are from the original one. Using an Infill 3D Geared Extruder and E3D Hotend. And, I went threw all of the 6 PDFs when assembling it.
Hier mal Cura Einstellungen:
@Volker_Klaffehn Perfekt hit on that! Printing directly from SD card resolves the blobbing. Also the print only takes 1:10 hours instead of 1:30 when printing from the Pi. Heres a picture https://photos.google.com/share/AF1QipNw42eEoY8tkODAfyYxLG9LXFT1yI9efIsfaZbaFtQrlj7KBCUqdcQ-zS6TKnK-rg?key=RHNxdXQtX0FETVUwSDhJQ0pNSmk3Z2JfYjYyWE5B . The left one is the new one.
Still not perfect.
@Ashley_Webster Thanks for the hints, going to give them a try. Slipping and temperature fluctuations are already ruled out. Currently modifying the retraction. Nozzle is clean, and I am cold pulling the filament on every change.
@Nathan_Walkner Ok. Maybe a general @OctoPrint or Octopi Problem? Only tried in on a new Raspberry Pi 2.
I can only reiterate what I’ve said in the past: if people who do run into problems with OctoPi/OctoPrint don’t report back and seek help in the G+ community or on the mailing list (with a willingness to provide data I might add) there’s absolutely nothing I can do to make stuff work for them. A lot of people print perfectly fine. Blobbing and stalling hints at communication errors, which can be caused by quite a lot of factors. That starts at people overtaxing the Pi (e.g. by also running the graphical Linux interface on it while printing or by using a webcam that cannot put out mjpg natively), continues with using inadequate power supplies for their pis (I’ve had users whose problems magically vanished once they started using a proper stable 5v/2a psu), further continues with bad USB cables or cables lain down right next to stepper motor wiring and ends with simply running old versions of OctoPrint that still have some specific bugs in the comm layer (1.2 is current, please use that…) or buggy firmware. So, no, sorry, it’s usually not a “general problem” with OctoPrint, most times it’s an environmental factor, and while I’d like to get to the ground of the cases where it isn’t I need collaboration for that because I can’t reproduce myself.
Octoprint (and OctoPi) work well in our farm. We use images from Guy for the new machines but previously built them from source for both Pi and BBB. We control all machines from a single workstation and share files using a NAS. Prior to Octoprint we managed individual SD cards in each machine. The Pis are up 24/7 with each machine logging 50-60 hours of print time a week.
To pile on, it sounds like the OP is having a communication issue between the Pi and the printer. Have the Pi boot into the command line, don’t start X. SSH into the Pi if you need to work on something. If you do need to use a GUI start it manually and reboot to the command line when you are done. The issues we’ve had with communication have been due to the USB wall wart PSUs failing over time. We’re going now to a stand alone PSUs for the Pi.
No worries on not getting an error report on this. But I first have to look a bit deeper into what could cause this in my setup. As a software developer myself I want to rule out as much as possible before reporting a bug or something … Have Octoprint running on my other printers without any issues myself, but not on a raspberry pi.