Hi RegenS,
A common problem is to command the motion faster than what your machine is capable of moving. The Trajectory Planner creates a trajectory based on what you told the Trajectory Planner your system is capable of. If you were to display the trajectory (green DROs) you should see that the GCode lines match the trajectory and the GCode doesn't advance to the next line until after the trajectory is Done. However your actual machine position (blue DROs) may be lagging behind with a large error.
If you configure a small Max Following Error KFLOP will immediately detect this error, disable, and Stop. I'm guessing you have a large Max Following Error configured which tells KFLOP to allow any following errors and to just continue on and ignore the problem.
The solution is to configure all your axes properly so they have settings that they can actually do. A common mistake is to set high velocities then test only small moves that only accelerate to slower speeds. Then when GCode commands a big move it will be discovered that the high velocity is not possible.
So in summary the solution if this is the case is to either:
- Make changes to allow your system to move faster and/or accelerate faster
- Specify Settings your system can actually do in all case
Also set a small
Max Following Error so if there is a problem KFLOP will tell you.
Please read
this and
this.
HTH
