The problem is that the printer moves faster than we can get those strings back into the buffer and parsed. These buffers are not very large, so if I have 30 individual line segments that make up an arc, then the printer might spend a lot of time dealing with the commands it has in the buffer. Generally, this means parsing out the mm’s from the input into how many steps it would take, then deciding based on if it’s in relative mode or not, what to put in the internal buffer. In the case of individual segments, the firmware has to store every single command inside a buffer, until it has processed it into something it can use in its internal buffer. Also, just as a note, neither the arc or the line segments need to know about nozzle diameter in the firmware. Ignoring CAM completely (Don’t bring routers into a 3D printing fight? shrug), let’s do a comparison between what the controller has to do with multiple line segments vs an arc as well as look at what it can do. You have to understand exactly what’s going on under the hood and the tradeoffs involved.
But you can’t look at this with just simple factors like clock speed and memory. That means 14,400 characters / second assuming you’re using that baud rate.
0 kommentar(er)
