I've never tried to use an arduino to read quadrature signals. I get the impression that reading them can use a fair bit of cpu cycles. In addition, you need to calculate the pulses and send them to the stepper. The precision required can also require a lot of cycles. And stepping signals need to be somewhat long. That can be handled with interrupts or hardware timers though.
All that can add up to the processor being stressed. The one I mentioned from the ELS project has hardware quadrature decode, so you don't need to use cpu cycles for it. It also means that you will be less likely to miss signals, though you would probably never move the table fast enough for that to be an issue. It also has a floating point unit, so you get high precision calculations for low cycle counts. It's also much faster.
It's hard to say how much that will all matter. I haven't tried it, so it might be a non issue. If you already have the micro, might as well try it. You can write some test code to see how much time things take so you can see if the chip can keep up.
All that can add up to the processor being stressed. The one I mentioned from the ELS project has hardware quadrature decode, so you don't need to use cpu cycles for it. It also means that you will be less likely to miss signals, though you would probably never move the table fast enough for that to be an issue. It also has a floating point unit, so you get high precision calculations for low cycle counts. It's also much faster.
It's hard to say how much that will all matter. I haven't tried it, so it might be a non issue. If you already have the micro, might as well try it. You can write some test code to see how much time things take so you can see if the chip can keep up.