![]() ![]() The location and name of these settings vary slicer to slicer. Reduce the resolution of the final GCODE. That's something I'll just have to figure out. M400 is supposed to help, but it doesn't seem to. This issue is now exacerbated to 32 movements, which has significant side effects when the last 32 moves are very long lines. I was having trouble with the heaters turning off before the last 16 movements are completed. With these changes, the slowdown lasted for a shorter duration of the curve. I haven't bothered revisiting it - the increase to 32 was enough to reduce the effect while I wait for a new Ender 3 motherboard. This may have been low memory causing corruption, or user error. I tried increasing BLOCK_BUFFER_SIZE to 64 but had some issues connecting over serial. I tried increasing the BUFSIZE significantly while leaving BLOCK_BUFFER_SIZE at 16, but performance was same/worse. I increased the BAUDRATE to 2500000 but I'm not certain if this improves or degrades print quality.īLOCK_BUFFER_SIZE is the movement planner buffer. You can reduce the effect of the first item on an Ender 3 by increasing BLOCK_BUFFER_SIZE from 16 to 32. If you've got cause number two, and/or serial errors, double check that another computer doesn't have the same issues before trying to solve 1.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |