Please follow these steps for tuning:
1. Set C00.04=0 to switch to manual mode.
2. Confirm the inertia ratio (using the drive's automatic inertia identification function).
3. Fine-tune the speed loop (C01.01, C01.02):
Gradually increase C01.01 until slight noise or vibration occurs, then back it off by 15–20%;
Gradually decrease C01.02 to eliminate steady-state speed error, but do not set it too low, or low-speed creeping/oscillation may occur.
4. Fine-tune the position loop (C01.00):
Gradually increase the value to shorten positioning time and reduce tracking error; if overshoot occurs, back it off by 10–15%.
5. Acceleration feedforward + velocity feedforward.
6. Adjust friction compensation:
Measure the friction torque in both the forward and reverse directions separately, then input the values.
However, at the 0.001mm (1μm) level, mechanical factors often limit precision more than electrical parameters—such as leadscrew backlash, thermal expansion, structural rigidity, and uneven guideway friction. If the steady-state accuracy remains stuck at a certain value after manual fine-tuning, it is likely a mechanical bottleneck that cannot be resolved by gain adjustments.

PCW wrote:

Does sound like an EMI issue.

Have you tried debouncing the limit switch signals?
 ( This can be done with the hal debounce component or with some
hardware, a hal parameter )

This seems the most likely problem and a simple solution. I did go through your Hal and ini files shared earlier and could not see anything obvious wrong.

I probably wouldn't add a max limit signal if I was sharing a single home/limit switch but I don't think that will make any difference. Are you using proximity sensors or switches? normally open or closed? if prox sensors, are they pnp or npn?

See if you can install a wifi dongle on your garage pc and get it on your network. Then you should be able to create a network share of your home folder you can reach from your main PC to configure and share Gcode files

Does sound like an EMI issue.

Have you tried debouncing the limit switch signals?
 ( This can be done with the hal debounce component or with some
hardware, a hal parameter )

I am currently having the same problem. After it telling me what my key was everything else I did much the same as michaeln I kept getting conflict messages, could not examine sources, etc. I am new to this so where and how would I remedy my key issue.and I don't have the Synaptic option that I can find.

It’s been a little over 10 years since I last used LinuxCNC; back then it was for a one‑off prototyping project at work. Now that I’m retired, I’m thinking about getting back into it for some hobby projects.While going through some old boxes, I found some MESA cards I had kept as spares: 5I22, 7I33TA, and 3 × 7I42TA. They were stored properly and should be in good condition. I’m not sure how current this generation of hardware is anymore, and I’m reluctant to start a new build around something that is obsolete. Before I decide what to do with them, I wanted to ask: do these boards still have practical value for anyone running older systems? If so, I’d likely sell them rather than let them sit unused.As for new projects, I’m considering a few possibilities:

• 3‑axis router, for wood and softer materials. Likely steppers, though I may look at servos depending on what I decide for requirements.
• I have a CO₂ Iradion laser + PSU, new in the box. Could be a candidate for a laser cutter/engraver build, or I may just try to sell it if there’s still a market, as my primary interest is the router.
• Guitar pickup winder, something I’ve always wanted to build, and a simple way to get back into LinuxCNC.

Before I dive into researching current LinuxCNC‑based routers, laser systems, or pickup winders (does anyone know of one), I figured I’d ask here first. Any pointers on modern hardware choices, project examples, or insight into whether the MESA boards I have are still useful would be appreciated.

I am.

However, my lathe is not completely finished and I'm finding that I will need to heavily modify PB or switch to another GUI (likely Flex) as my configuration and GUI preferences are pretty specific.

Hello all, I was hoping to get an idea of who all out there is using probe basic lathe currently?  please drop a line and let me know if you are using it!  

thanks all!!

Chris