I was out on a business trip this week and only just got to try this. I don't have a lib/python/gladevcp folder.

I did find those files in lib/python3/dist-packages/gladevcp. Would it help to edit them there, or should I leave those versions alone and look for them somewhere else?
Cheers,
Mark

To do a LinuxCNC retrofit (with existing servo drive and motors) you would need to know
the pinout of the 25 pin connector between the old controller and servo drive.

OK,das war bei mir aber nicht schwierig ,USB dran ,Com Port eingestellt und einmal gescannt - fertig ,klingt so als wären die Vorgängerversionen nicht so kommunikativ .
Nur bei dem Autotuning werd ich nicht schlau draus 

Just went to run dmesg again....after it finished...stretched terminal window...went blank...opened new terminal fullof read only errors??

These are the nameplates on the drive motors, plus a list of documentation for what came with the machine. Plus, that is the first page of the amplifier, I believe. It's a 3-channel drive/amplifier from what I have gathered. I can send all other pages if needed. 

So this am I switched to another pc optiplex 9020...used same SSD...Got same error...
Ran smartctl...disc passed....just did fsck -f -y....got 4% noncontiguous as result

dmesg gave nothing in red

going forward you would need to use the usertabs for that. i am releasing a conversational plugin that will utilize that conversational tab so it is now no longer populating with the old bad conversational unfinished screens and macros.

Seems to be getting worse...

Sounds like some hardware is failing,

Does dmesg show any hardware faults (disk errors etc?)

Looks like the servo drive is a Copley 800-468, and older 3 Axis drive.
I suspect it's an analog velocity mode drive but its old enough that is
hard to find data on the drive. Was any documentation included with the machine?

These are some of the photos I have so far. Working through getting the PC portion out of it, as I have a spare, more modern PC I want to use in it. 

At the risk of dating myself, MTConnect reminds me of an old project (ganglia) which was originally used in academic high-performance computing environments to monitor distributed compute nodes. These ideas led to the modern data-center and eventually bormon/prometheus for large-scale infrastructure monitoring. It's a similar problem. Lots of vendors with proprietary hardware all reporting data. Aggregating it is a PIA.

mesaus has one:

mesaus.com/product/7i76eu/

 and our EU dealers have more

We should have the next build lot done in about 4 weeks