02-26-2004 04:39 PM
03-01-2004 02:44 PM
03-02-2004 10:52 AM
07-16-2015 11:07 AM
This bug is alive and well, 11 years later, in NI Motion 14.0.0.3000.
Reproduction frequency is, as Chucker mentions, arbitrary. Maybe it'll take 10k's of discrete moves before crapping out; maybe failure mode can repro reliably after just a couple moves. Putting 10-50msec delays in the "obvious" places (including, between the `Blend Motion` command and the first `Read per Axis Status` to check the `Blend Complete` bit) does not help the problem.
It's arbitrary which of the axes in a 3-axis vector will "wander" toward their position setpoint at roughly 1 step per second sometimes X and Y, sometimes Y and Z, sometimes just one axis....
The only known fix is to remove all Blend Motion and stick with Move.