What the 6212 *can* do is generate a finite pulse train with an exact # of pulses at a constant frequency. You would need a stepper drive that accepts step and direction input (maybe also enable) and uses them to drive power to the motor windings in the right sequence. (Direction and enable can be simple software-timed DO lines.)
What you pretty much *can't* do is generate nice motion trajectories that allow for smoother motion and higher speeds. You'll be limited to the speed range that the your system can reliably follow, like maybe low single digits of revs/sec, and the motion may not be terribly smooth. A microstepping drive can help with smoothness but won't appreciably change the top speed.
Sorry, I don't know any of the Matlab-based syntax, only LabVIEW.
-Kevin P
CAUTION! New LabVIEW adopters -- it's too late for me, but you *can* save yourself. The new subscription policy for LabVIEW puts NI's hand in your wallet for the rest of your working life. Are you sure you're *that* dedicated to LabVIEW? (Summary of my reasons in this post, part of a voluminous thread of mostly complaints starting here).
