How jitter affects the no of steps or speed of the stepper motor

I am working with Mesa board with 3 stepper motor. I am trying to reduce the jitter and so want to understand if there is direct relationship between jitter and the speed of stepper motors especially when 3 motors are connected.

As I understand when we are not using parallel port, then base thread doesn't come into picture and so only servo thread jitter needs to be seen.

If so, then would like to understand how will I know what max steps can we have for stepper motor have per sec running based on jitter? Is there any direct calculation exists? I am sure it will differ when 3 motors are connected and when 1 motor is connected.. 

Please help understanding these calculations

vkhargwanshi wrote:

I am working with Mesa board with 3 stepper motor. I am trying to reduce the jitter and so want to understand if there is direct relationship between jitter and the speed of stepper motors especially when 3 motors are connected.

No, there is no relation between host jitter (or number of steppers) and step rates when you are using Mesa hardware. Therefore also no such calculations.

Thank you for the reply.. Ok so how should I decide upto what extend I have to optimize jitter to ensure smooth working of my 3 axis machine..

Thank you tommylight.

I am doing some trial and errors, I am using Mesa 7i96s. I observed with one motor if I keep the speed as 5000mm/min with 200 microsec jitter, 32 micro stepping and 200 steps, I keep getting errors from LinuxCNC within mins, but when make it 2000mm/min, don't get any error, even when running for an hr...

So you mean to say, I need to have such trial and errors to understand what will be the best speed I need and so keep lowering the jitter by removing services.. Right?

What's the exact error message? (Run linuxcnc from the terminal and copy and paste the error message(s) here.)

Large jitter amounts can cause following errors.
These following errors are velocity dependent.

This can typically be eliminated by adjusting the DPLL
timing.

Also if you get Ethernet timeouts you will get following
errors so depending on you host hardware, you may need to
increase the servo thread period.

There is a workaround for this also if you cannot completely eliminate
Ethernet timeouts

To check timing, run LinuxCNC for a while and then run
this command in a terminal:

halcmd show param *.tmax

These times are in CPU clocks (on x86 hosts)

Thanks PCW. I will try these.. By the way I am using Raspberry pi.. so hopefully will get something better....

I am getting following 2 errors

1) Unexpected realtime delay on task 0 with period 2000000
2) hm2/hm2_7i96s.0:stepgen.00.maxval is too big for current step timings and position-scale. clipping to max possible.