My x and y axis are set to 20,000 pulses per inch. This is why I needed a faster computer that can handle a faster kernel.
1. Kernel=25khz, vel=135ipm, accel=1 the velocity slider is at 100%.
2. Kernel=45khz, vel=135ipm, accel=1 the velocity slider is at 100%.
3. Kernel=60khz, vel=135ipm, accel=1 the velocity slider is at 75%.
4. Kernel=65khz, vel=135ipm, accel=1 the velocity slider is at 66%
5. Kernel=75khz, vel=135ipm, accel=1 the velocity slider is at 55%.
6. Kernel=100khz, vel=135ipm, accel=1 the velocity slider is at 45%.
So I have to apologize for being wrong about my slider position earlier in this thread!!
Right now my accel is set around 1-2 as i recall. It's 3 stories down stairs. So I'm replicating my system settings on it's twin computer upstairs.
20,000 pulses per inch uses up a lot of cycles. So I was pretty lucky to get 135ipm out of the old pentium III 800mhz machine. But the machine won't go any faster at 2.4ghz. In fact, it actually skips slightly more steps if the kernel is set higher than 45khz, if I leave all of the motor settings the same. This is why I think the scope needs to be applied to the hardware to see if there is a mismatch in timing between the step and direction pulses. Or maybe my PS2501 opto board on the parallel port is the bottle neck.
Mike