Hi,
As far as I can see, there is no feedback to the controller or Mach at all.
That is correct, Mach is open loop. That is to say that mach issues a trajectory, which is a series of points in space in 1 millisecond time intervals. Mach issues
blocks of numeric data that describe the controlled point in 1ms time slices. The motion controller receives those pulses into the motion buffer. As those time slices are enacted
the motion controller returns to Mach where the controlled point is and that data is displayed by mach in its DROs. The fact that the DROs appear to 'move' tells us that
Mach is producing a trajectory and that the motion control is receiving the trajectory and that its issuing Step/Dir pulses to the motors and 'consuming' that trajectory.
In truth though the motion controller issues the Step/Dir pulses but really has no idea whether the motors actually got there, you might say its 'assuming' they got there.
With servos or closed loop steppers they can signal a Following Error fault if they do not get to the commanded location....so Mach has some justification in assuming that all is well.
When this fault occurs do the DROs reflect the actual movement or do they reflect the programmed movement? If the DROs reflect the actual movement then the programmed
movement is getting screwed up in Mach at the trajectory phase. If the DROs reflect the programmed or commanded movement then the motion controller is issuing way too many
Step pulse for a given distance.
Just as a matter of interest you don't have a G51 active do you? Just try canceling any scaling with a G50.
Craig