X Coordinate Lags MPG Encoder

Very strange, I would expect a lot of complaints if this problem was widespread
so the question becomes: what is unique about your configuration

Have you widened the X following error limits so you never get a following error?

Do you have a hal/ini file set that exhibits this issue? (with backlash = 0)

I can try to duplicate with 2.7.14

EDIT

Ok, tried your hal/ini files with 2.7.14 here and I cant test everything since I dont have a MPG, but there is some odd behavior just
with the axis jog + and - buttons. On X axis as long as you press the +, or - jog button, the graphic window is frozen until
the button is released (completely frozen, the tool tip doesn't move either). Once the button is released, the display is updated
This does not happen with Y or Z.

However, this seems to be specific to your hal/ini file set, I cannot duplicate this behaviour with my hal/ini files. With my hal/ini files
X,Y,Z behave normally (display is updated continuously on X,Y,Z jogs)

"following error limits"
I have tried both narrow (FERROR = 0.5 MIN_FERROR = 0.05) and wide (FERROR = 0.5 MIN_FERROR = 0.05) error limits, but this did not affect the X commanded position coordinate behaviour.

"Do you have a hal/ini file set that exhibits this issue? (with backlash = 0)"
I have provided the .ini and .hal files in the original post (#128700) and later in post #128844. The first set has the MPG in it and the second set (#128844) is a fairly generic output from Pncconf without the MPG. This demonstrated that the problem was present even in simplified .ini & .hal files.

I've just seen your edit to your post. You are experiencing something different from what I have seen, but they do share an anomalous behaviour on the X axis. Can you send me your .ini & .hal files so I can do a line by line comparison?

EDIT
"wide (FERROR = 0.5 MIN_FERROR = 0.05)" should be wide "(FERROR = 5 MIN_FERROR = 1)"

tommylight,
Thank you for your opinion on 2.8. Not sure I want to go there yet, as I have my hands full with other things right now and learning how to install 2.8 might take up too much time. But if things don't go well with 2.7.14, I may have to go to 2.8. On the other hand, the problem might just follow me into 2.8 and I'd be no further ahead.

I'll look into "setp pid.y.maxerror .0005". I didn't know that was required/recommended. I tried it, and it didn't fix the X coordinate problem, but I assume you didn't intend it as fix anyways.

Here is your initial hal/ini file modified so it will run on my test hardware (jogtest.ini and jogtest.hal)
plus a generic ini/hal file set

jogtest exhibits the X jogs not updating issue but my generic file (7i96.ini & hm2-pidstepper.hal) set does not

Thank you. I'll have a look at the files you sent tomorrow and I'll let you know what I find.

I understand that, with your files, you did not experience any lag in the commanded X coordinate. I compared your .ini & .hal files to mine and noted all the differences. Then I updated your files to match the Mesa card I have (my 5i24_16 vs your 7i96) and changed the gpio pins to match my configuration. Unfortunately, I am still seeing the delayed updates.

A few posts ago you said "I would expect a lot of complaints if this problem was widespread". It might be under reported because few people look at the commanded X coordinate. After all, the system is keeping track of the jog clicks, its just not displaying them consistently so maybe most people view the actual instead of commanded position.

The value of looking at the commanded position is that I can verify that the MPG or jog +/- input via the Axis user interface is working. Through this investigation, I have learned that halshow can display variables (mpg-out, hm2_5i24.0.encoder.04.count and hm2_5i24.0.encoder.04.rawcounts) that demonstrate that the system is keeping track of the MPG input correctly. That means I can proceed with my original plan: 1) get the MPG working (done) and 2) tune the servo motor.

As you suggested, there is probably something unique about my configuration or system. Until I find a solution, I can always click in the Preview Window to make sure X is displaying the correct commanded position or I can use halshow to display relevant variables.

Thanks for your help!!