I’m attempting to sync the positions of two slaved motors before sending motion data from our CNC motion planner (which assumes identical positions) to avoid jumps on enable.
I’m attempting to accomplish this using
Under some circumstances (I haven’t discovered a pattern), what I observe is that the axis moves, but never quite gets there (and stays in the
MOVING state indefinitely—or until I run out of patience.
Here’s MotionScope data from the commanded move.
Here’s a closeup of the “end” of the move.
Here’s what RapidSetup shows during the never-ending move.
The axis is a part of a MultiAxis during this move (and, generally, always). Does that matter? None of the other axes are even enabled.
The command position is where I expect it to be. The motion parameters are sensible ( >> 0 ). Position error hovers around 1900 for as long as I want to wait (e.g. the entire time I spent composing this post).
Let’s assume I’m doing something to cause this behavior. What could it be? The axis has a state of
MOVING, but it’s not actually changing position (more than just the normal flicker I see with these drives). What would keep it from attaining the command position without causing a fault or other error?