When using the attached configurations from my previous post, the last current position is displayed.

What position is displayed when you turn the servo off and on again? 0 or the last current position?

I don’t think it can be the Z-axis clutch, as I have a glass scale on Z.
So a slipping clutch should either be corrected or, more likely, end in a stop due to following error.

You can't use uppercase letters in oword names

Could the coupling between the Z axis motor and ball screw be slipping? 

 This is one of the macros that isn't working for me. I've tried running them with Axis and it won't run either. They work with others, but I don't understand the exact reason.
 

Thank you. This brings up yet another issue, I have been trying to update but I don't believe I have a good repository. I keep getting an error saying the address doesn't have a release. I have attempted several different locations And I entered them into synapse. But I must be doing something wrong.

You can also just add ~220 ohm series resistors in the PWM lines

The main hazard is ground differences/HF noise causing negative
input voltages with unlimited current. a series resistor will protect against
this.

Yes I'll take care to put a BOB betwen P3 and the hardware until I grab a specific card from mesa store

Thanks a lot, have a good day

Can't see an oword problem, but have added some oword path checks to help to see if it's just a path problem. qtdragon will complain if the oword path is not found.

Someone loaned me a Probotix-based CNC Router. I need to make up some very simple wood frames, but I cant seem to the the controller to recognize the router table. I realize that I know very very little about LinuxCNC, and would rather contract and pay someone to help me. This could be local, in Novato, CA near San Francisco, or by remote desktop (Teamviewer, Anydesk, etc.). Could someone make some time to look at the setup and get me started?
Thanks!!
Anthony (415) 883-1476

You probably run Gmoccapy 3.4.6.
I suggest to update LinuxCNC to the latest version, then you will find a new setting called "G-code theme" where you can select another theme for the G-code.

Ok I pushed work to master to allow selecting auto switch to MDI for macro buttons and HAL pin macros on Qtdragon's setting page.

I didn't get a change to push it to the other Qtdragon variations.
I have not looked into the O word problem yet.

I was at it again today.
Threading does not work again, absolutely the same behavior as before.This time I could try G33 with the problem present. Running the exact same code multiple times, every subsequent run cut slightly to the right of the last by very even amounts.Now I am really confused. It worked a few days ago. That day it worked over and over, and now it does not work at all.
RPM does not seem to make a noticeable difference, or at least it does not work no matter how low I go.I don’t even have an idea what that tells me. The hardware is obviously capable of working. Is it some intermittent contact somewhere?The encoder being the problem is really the only thing that makes sense to me, but all tests I did point to it being OK.If anyone has an idea what I should test to find this, I would highly appreciate it.