Basically, we're talking about 8-bit processors here without the processing or memory to look ahead like a motion planner like Mach3 might do. (See this post discussing the lengths that some motion planners go to) Hence, its up to the slicer to "dumb it down" for the machine, which has a very limited motion planner.This is often discussed: small tight circles need to be printed slower.
Use a slicer which can slow them down (e.g,, RepG + Altshell plugin with
slowing down for all loops enabled). The issue is that the firmwares
control for linear acceleration but not centripedal. That's because
the firmware has no clue that a small, tight circle is being drawn.
And for centripedal acceleration, it's square(velocity) / radius. Since
you cannot do much about the radius, you're left with reducing the velocity
and that's the job of your slicer.
Code: Select all
python3 smallFeatures.py Primus_Pi_Body.gcode 360 30