Centroid Community CNC Support Forum

No it is a WIN11 Problem if you connect a USB2 device to USB3.2

Uwe

We have a potential fix that lowers the CPU usage for the MPGclient.exe.

To test out the fix, rename your existing mpgclient.exe to mpgclient_original.exe (or anything else so you can change it back after testing) and name one of the fix exe's to mpgclient.exe from their current name. The difference in fixes is based on the sleep timer delay. I was unable to see any issues on the bench even with the 200 millisecond variant.

Thank you for the fix. I'll test it and report back shortly.

BTW, moving the adapter to the 2.0 port made no difference.

EDIT: new MPGClient.exe seems to be doing the trick.

Switched to MPGClient_100.exe and the CPU usage dropped from 60-75% to 10-35%. Overall CPU load dropped from 95-100% to 50-65%.

Thank you again.

EDIT - See below post for resolution. No issues with new file

UPDATE

The new MPGClient file has resulted in the MPG not functioning properly.

1. Incremental mode - only 1x setting on MPG works as expected. 1x results in 0.0001 movement for all axes, but 10x and 100x do not move DRO or axis.
2. Continuous mode - 10x moves at slow jog speed, but 100x only moves at slow jog, not fast jog. Check axes settings in Wizard and fast jog wasn't changed from before when it was working.

Batteries are brand new alkaline.
Restarted PC and CNC12 after installing new MPGClient file. Turning on/off the WMPG-6 didnt resolve the issue.

That sounds like the normal behavior when CNC12 thinks that a probing device (probe, tool setter, or touch plate) is tripped.

cncsnw wrote: ↑Fri Aug 08, 2025 4:13 pm That sounds like the normal behavior when CNC12 thinks that a probing device (probe, tool setter, or touch plate) is tripped.

That was it. TTS-4 appeared to be triggered and was throttling the MPG jogging.

Thanks a ton for the tip.

So the new MPGClient file is GTG.

That was it. TTS-4 appeared to be triggered and was throttling the MPG jogging.

Thanks a ton for the tip.

So the new MPGClient file is GTG.

Thank you for the the feedback. Which of the versions did you end up using (50,100, 200)?

Centroid_Liviu wrote: ↑Mon Aug 11, 2025 9:52 am Thank you for the the feedback. Which of the versions did you end up using (50,100, 200)?

I used 100. Have not tried 50 or 200 since 100 worked and I've got plenty of other things to work through on this installation.

Doing some testing myself with a Nuc with an N100 processor:
Base MpgClient.exe: ~30-35% CPU usage
MpgClient_50.exe: ~20-25% CPU usage
MpgClient_100.exe: ~15-20% CPU usage
MpgClient_200.exe: ~7-12% CPU usage
There seems to be little difference in terms of responsiveness, but I think the 200 version could be noticeable if you're paying close attention.
The 100 version is probably the best middle ground here for responsiveness and performance.
Anyone giving these a try, I'd try the 200 first and see how it feels.

Out of interest, what was 'fixed'?