Yes, I see what you mean about the speed differences.
I'd be inclined to state that is just the 'processing of the data' for the purpose of displaying the values and not a reflection on the 'real time' speed of data exchange between pulsecoder and controller, otherwise there would be a huge following error (difference between commanded value and actual value) within the motion processing which to me would result in error after error after error.
It could well be, both robots are actually processing a different amount of data at the time of displaying these values.
Motion instructions are always the priority as far as the controller is concerned, anything squirted out to the teach pendant for display purposes sit at the end of the priority list of processing as far as I'm aware.
But still, interesting when you see them side be side.
I wonder if you just set them both to single display for the positional data, you would see some improvements or not?
The error you are getting is a distinctive 'break' in communication from pulsecoder to controller according to the error listing though.