Quote Originally Posted by Desertboy View Post
The CNCshield is designed for grbl which is cnc router firmware not 3d printing! It can pass up to 36v to steppers (It's designed for a hobby machine after all) but if you need 60v to the drivers you can do that easily as well. Most people use cheap ass Polou steppers which are not suitable for 36v but you can get a lsightly more expensive driver than will push 36v fine or wire a real driver to replace the cheap chip drivers the cncshield is designed to take on board.
That CNC shield is just a glorified header board, with pinouts optimised for grbl. You could just as easily use it for 3D printing.
Regardless, what I was highlighting was the more stringent requirements for CNC.

Of course it's not as good as much more expensive solutions but it's very powerful for the price (£25 including 4 stepper drivers!) and not as useless as you might think but I will move to a breakout board solution relatively soon I consider it the least essential purchase right now in getting the thing built and cutting.

Ardunio and cncshield are also very good for testing nema's so when I do upgrade I will have a simple test bed for the recovered motor's I collect.
Just for clarity, I never said an Arduino is not a useable option, it's just not an ideal one.
grbl is very stable these days, maybe not the quickest of course but they are rock solid stable.

"The controller is written in highly optimized C utilizing every clever feature of the AVR-chips to achieve precise timing and asynchronous operation. It is able to maintain up to 30kHz of stable, jitter free control pulses."
And if you have a look at the grbl source, you'll see it's using a similar smoothing algorithm to Repetier (which incidentally has a nice explanation on how it works). It may be jitter free, but in order to achieve the jitter free, you have to compromise accuracy. And then to achieve the higher pulse rates, it starts scaling steps, so you loose even more accuracy, and introduce a certain amount of jitter.

If I didn't have as much work to do just now, I'd try connecting an arduino to a datalogger, and see just how jitter free the output really is.

P.S. the technobabble may impress your average arduino coder, but all they're ultimately doing is handling pulse generation in native AVR C, and relying on ISRs for timing. The only thing optimised other than good coding technique, is avoiding using C++ and the arduino compiler, which is inherently bloated.