Yeah, I suggest you use the group move time feature of the ssc-32 and use a timer in VB to send the position commands out appropriately . . . . of course depending on how frequently you want the position commands to update you might run in to the problems I had!
Incidentally, the VB timer is no worse than querying the system clock for use as a timer. I measured the output of both using a daq setup and labview (SSC-32 out of the loop) and the results were the same. At certain update rates, 30ms, 60ms, etc, the output was reliable. Otherwise, not so much. The same sawtooth plot I posted before developed using the daq setup. It is best to move to a microprocessor to handle the timing if you want better control over the update rates, for me I simply selected an update rate that worked well with VB.