search

Klipper3d / klipper

Klipper is a 3d-printer firmware
GNU General Public License v3.0
9.47k stars 5.31k forks source link

Blobs / zits on round models #2792

Closed Maxiba closed 4 years ago

Maxiba commented 4 years ago

Hello!

I have a problem with getting blobs / zits [20200427_173909] on my round model [Model.zip]. I tried several times. It seems like it has always the same pattern.

Some unsorted informations:

20200427_173909 20200427_173939 loadgraph3 klippy3.log Model.zip

Best Regards! Max

jalanjarosz commented 4 years ago

Do you have the “Display Layer Progress” plug-in installed and enabled?

I only mention this because there is a known issue with this popular plug-in that causes stuttering, pauses, and this blobs.

Maxiba commented 4 years ago

No, there is only OctoKlipper, BedVisualizer ans Action Command Prompt in my Plugins Settings. I didnt installed any other plugins yet. Or do you mean GCodeViewer?

Coffee0297 commented 4 years ago

what slicer? the new cura 4.6 are know in create issues.

kind regards Tonny

Maxiba commented 4 years ago

Yes, actually use Cura 4.6... I just printed a new test cylinder. I will post the result later... What free slicer can you recommend?

Coffee0297 commented 4 years ago

slic3r++

Hywelmartin commented 4 years ago

my host buffer is normally way lower than yours.... are you certain that you are printing from vSD

Maxiba commented 4 years ago

slic3r++

I tried slicing and printing with slic3r. And it really turned out much better. There arent any blobs or zits! Just a few different printing problems i didnt had with cura, but i think i just need to tune my settings in slic3r. I would have never thought that the problem is my slicer!

my host buffer is normally way lower than yours.... are you certain that you are printing from vSD

In the graph i have posted i wasnt printing with vSD. But i had the same printing result with and without vSD.

jalanjarosz commented 4 years ago

There is some good slicer settings here:

https://github.com/KevinOConnor/klipper/blob/master/docs/Slicers.md

And here too:

https://github.com/KevinOConnor/klipper/issues/1869

Thanks! James

On Apr 28, 2020, at 3:11 PM, Maxiba notifications@github.com wrote:



slic3r++

I tried slicing and printing with slic3r. And it really turned out much better. There arent any blobs or zits! Just a few different printing problems i didnt had with cura, but i think i just need to tune my settings in slic3r. I would have never thought that the problem is my slicer!

my host buffer is normally way lower than yours.... are you certain that you are printing from vSD

In the graph i have posted i wasnt printing with vSD. But i had the same printing result with and without vSD.

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/KevinOConnor/klipper/issues/2792#issuecomment-620800815, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJYADFZJYU3QR277ZS2TKEDRO4S63ANCNFSM4MSBIAHA.

jakep82 commented 4 years ago

Are you sure you were printing from the vSD file? Just enabling vSD in the printer.cfg is not enough, you also need to make sure you configure Octoprint to only show SD files so you're selecting the correct file to print. This issue is a very common with Octoprint, and I've always been able to solve it with vSD.

Maxiba commented 4 years ago

Are you sure you were printing from the vSD file? Just enabling vSD in the printer.cfg is not enough, you also need to make sure you configure Octoprint to only show SD files so you're selecting the correct file to print. This issue is a very common with Octoprint, and I've always been able to solve it with vSD.

Yes, I am sure. The message in terminal said "starting printing from SD" or something like that. And the gcode commands were not showing, it just said, that the commands from SD card are still running. The problem was really cura 4.6. The issue is known and will be fixed this week with release of cura 4.6.1.

See here: https://www.reddit.com/r/klippers/comments/g8z3st/stuttering_with_virtual_sd_too/