You have a *lot* of ram on the ARM parts. They also are pretty good at things like DMA to / from RAM for serial i/o. I suspect that a fairly big serial buffer would take care of any possible serial port speed issue. It's not speed challenged on average (no where near). The only time you might hit something would be in bursts.
Ok, so prove it::)-D
250,000 baud is roughly 25,000 bytes/sec. In a minute you can run 1.5MB over the link (each way). If the link spends 1/3 of it's time waiting for / getting responses that's a very convenient 1 MB per minute. At least on the type of files I run, a gcode file in the 1MB range takes an 1 hour or more to print.I have a 1.8 MB file printing right now that should finish out in 2.5 hours. Could I pad it with a bunch of stuff to make that not be true - sure. On the files as the slicing program does them, the serial port speed is not an issue on average.
Ok, so prove it::)-D
250,000 baud is roughly 25,000 bytes/sec. In a minute you can run 1.5MB over the link (each way). If the link spends 1/3 of it's time waiting for / getting responses that's a very convenient 1 MB per minute. At least on the type of files I run, a gcode file in the 1MB range takes an 1 hour or more to print.I have a 1.8 MB file printing right now that should finish out in 2.5 hours. Could I pad it with a bunch of stuff to make that not be true - sure. On the files as the slicing program does them, the serial port speed is not an issue on average.