25 minutes ago, DrDOHC said:weaked setting are: Model resolution, max. deviation, max. Resolution, none of which caused it to get better.
Seems like the right track to me. Seems like we are thinking it's the same or similar thing. It could be the prusa slicer does this better (reduces gcodes).
Recommended Posts
gr5 2,268
Look at the gcode for a known stuttering circle (a known layer where it does it - I predict it won't do it every layer). How many gcodes for a circle and how big is the circle? You wan't the buffer length of the printer (really? Only 8?) to be long enough that the printer can go from full speed (e.g. 70mm/sec) to stopped in that distance. It depends on the acceleration. Say it's really slow - 1000mm/sec/sec. You can get 0 to 70mm (or back) in 2.45mm. So you don't want more than 8 gcodes in a distance of 2.45mm.
This is almost surely the problem. If the acceleration is 2000mm/sec/sec you can get from 70 to 0 in just 1.22mm (wow - I didn't expect it to be linear).
If you want to go 35mm to 0mm with acceleration at 1000mm/sec/sec you only need 0.61mm. Wow - again it appears to be linear. Not what I expected. Anyway you get the idea - having half the buffer length and possibly lower acceleration can make a big difference and cause stuttering.
So in your cad you could just output fewer triangles to the STL. I've seen some crappy STLs where hundreds of triangles converge on one point (on a cylinder part). Most cad won't do that. But you can have 100 short gcodes just above and below that point all within 1mm. Makes the printer almost completely stop.
Link to post
Share on other sites