MPG causing axis oscillations.

That really makes no sense, what is the ilowpass scale? (I would not reccomend less than 1000)

There does seem to be something wrong with the stepgen but its not obvious what
as this is not a common problem.
Can you plot the following error and velocity during a jog with halscope and post it here?
That would help at lot to understand whats happening here

I will run the test tonight and post the results. The issue only occurs when jogging with the mpg in .100 per click mode. I have not cut any parts on the machine yet but have run several g-code files without issue. The machine jogs fine with the keyboard as well. I am not an expert programmer so there may be an error in my hal files. I have attached my latest one with ilowpass . Thanks for the help with this.

Here is the hal scope log file.

Hmm... a halscope screenshot would be a bit easier to interpret

Looks like something basic is broken maybe servo thread rate is not as expected or PCI clock is wrong
I would try setting the maxerror to 0 and seeing if that helps

The other option is to tune FF1 (assuming a clock issue)
Is this a 5I25 card? (you can easily break the stepgen on a 6I25 by getting the clocks wrong)

It is a 5i25, What does FF1 do? The odd thing is running gcode max error following error is around .00007in. This only happens when using the MPG.

Strange, you might try reducing the P gain

Also your example file has

setp ilowpass.0.scale 1

This means that smoothing cannot work (as I said 1000 is a reasonable minimum for ilowpass scale)

Make sure you reduce the jog increments to match the scale change

So I set ilowpass scale to 1000, ilowpass to .01 per the exampl and adjusted my jog incremants by 1000 offset the ilowpass scale. This looks to have completely fixed my issue. I just jogeed the machine around for about 1/2 hour with the mpg on all axis and not a single following error or oscillation. Thanks for the help, I can now say for sure that my future cnc builds will be running Mesa cards.

I'm glad the low pass filter fixed the following error during jogging problem.

I have been thinking about how this can happen and after looking at the plot, I suspect its a combination of
MPG jogging slight exceeding the stepgens accel limits, your quite low machine acceleration settings
and the fact that once the stepgens acceleration limits are exceeded, the PID loop is no longer running
in proportional mode so can become unstable. I will see what can be done about this so it does not bite anyone else