You should *definitely* use a counter output task for your pulse generation, not a digital output task.
X-series counters support buffered pulse train generation, allowing you to define a hardware-precise variable timing pattern for each individual pulse. This makes it possible to define full trajectory profiles (such as trapezoidal), which allow you to achieve higher top speeds and reduce motion time. It also allows you to control the total # steps precisely using only 1 of the 4 available counters.
M-series counters do not support this. Frequency changes *can* be done on-the-fly, but only via software timing. That'll make accel/decel less smooth, which will reduce the top speed you can achieve. Also, when in the mode that lets you change freq on-the-fly, you *cannot* also precisely control the # of steps. In a mode where you precisely control the # of steps, you can only run at a constant (and therefore relatively low) speed *and* you'll need to use both of the 2 available counters.
-Kevin P
ALERT! LabVIEW's subscription-only policy came to an end (finally!). Unfortunately, pricing favors the captured and committed over new adopters -- so tread carefully.
