T-Rex wrote: ↑
Mon Aug 13, 2018 3:07 pm
Yet to receive a reply, not too sure if this means no one has a clue.
if you uploaded the G-Code file it would be much easier for us to help you.
are you using 4.0.1? if you are using 3.x this was because you have a STL that's too detailed so S3D produces a GCODE that's toooooooooo detailed and you have many small moves that
- your firmware ignores but slows you down in the path and you get accumulation of filament
- your electronics can't handle the speed of g-code (can't pass enough g-code trough serial port / can't parse enough g-code in time) so you have stops and slowdowns and you develop blobs
4.x mostly solves this problem as it ignores "too precise" stl's and creates less moves but it's not ideal so it can still have this issue on some STL's. If you are not on 4.x move to 4.x, if you still have a problem, use some STL editing/modifying software to "optimize" your STL and reduce triangle count. For e.g. you can safely optimize the STL to 0.1mm "error" it will significantly reduce triangle number and will create STL that will slice faster and not produce this blobs.
Do a simple test to prove that's a problem; create a curved object and export it into STL with low poly count and super high poly count, then print them both and compare results
integrates with Simplify3D and allow you to
Calculate print time accurately (acceleration, max speed, junction deviation all taken into consideration)
Embed M117 codes into G-Code
Upload your G-Code directly to Octoprint
open source and unlicence