view the rest of the comments
3DPrinting
3DPrinting is a place where makers of all skill levels and walks of life can learn about and discuss 3D printing and development of 3D printed parts and devices.
The r/functionalprint community is now located at: !functionalprint@kbin.social or !functionalprint@fedia.io
There are CAD communities available at: !cad@lemmy.world or !freecad@lemmy.ml
Rules
-
No bigotry - including racism, sexism, ableism, homophobia, transphobia, or xenophobia. Code of Conduct.
-
Be respectful, especially when disagreeing. Everyone should feel welcome here.
-
No porn (NSFW prints are acceptable but must be marked NSFW)
-
No Ads / Spamming / Guerrilla Marketing
-
Do not create links to reddit
-
If you see an issue please flag it
-
No guns
-
No injury gore posts
If you need an easy way to host pictures, https://catbox.moe may be an option. Be ethical about what you post and donate if you are able or use this a lot. It is just an individual hosting content, not a company. The image embedding syntax for Lemmy is ![](URL)
Moderation policy: Light, mostly invisible
What printer do you have? https://youtu.be/Hvw3DrVAeTA?si=Pfy8z7OdlsybvbMN It could be this issue but that wouldn't be material dependent but might show up more with petg since it's more runny than pla.
It's an anycubic Kobra 2.
It's not small blobs like here, it's huge blobs because the printhead doesn't move for 10-20 seconds, so filament from the chamber keeps oozing while it just sits there.
If its stopping 10 to 20 seconds there's definitely something in the gcode making the printer hang. I'd try slicing the file again with a different slicer to be sure.
Thinking about this again, could it be you have something like "wait for layer time" on and a very high minimum layer time set for your petg profile?
I was overloading the controller with gcode commands due to high gcode resolution. I dug a little in to the terminal and could see that locked it up due to a checksum mismatch of commands when using octoprint. I'm guessing a reading speed/buffer issue is the cause when using the SD card.
I decreased resolution from the profile default 0.0125mm to 0.5mm and it went away. I'm going to see how fine I can set the resolution without introducing the stutter, but at 0.5mm it still looks good.
I was potentially trying to execute 24,000 gcode commands per second with that resolution when moving at max speed, now it's down to a more manageable 600 commands per second.
Here is an alternative Piped link(s):
https://piped.video/Hvw3DrVAeTA?si=Pfy8z7OdlsybvbMN
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I'm open-source; check me out at GitHub.