index debounce at 0 with no luck. Anything after 375 and my rpm reads wrong
The index debounce determines how manny times Mach will look at the index signal to confirm the signal. High values and you will see that
triggering will take longer, some will work at 0, I use a value of 10.
I also use a magnetic sensor, namely a Halls affect and it is fast sensing, some mag sensors like a reed are not fast enough at higher rpm's
and thus won't work right. That's why I asked what type so look at the specs of your sensor and see if it is limited.
Signal quality at higher rates may be different than low rates so you may want to look at the signal with an o'scope. If the signal is not clean
it can influence triggering timing and output. Sorry i can't be more specific.
locked rpm in the diagnostic information plugin
Disable that plugin / don't use it or any others from the thread testing thread, it is not functional and most of them required a specific related driver.
Spindle speed averaging, if on, will influence the threading accuracy since Mach reads the rpm to four decimal places ( if i recall correctly).....more accurately than you can measure it. Depending on your lathe system you may not even notice the affect on the finished thread lead.
I would still recommend users use it.
One reason threading will not work is if you don't have a licensed Mach.
Since you have an index signal per the testing, rpm is read accurately ( to some rpm range ) , i think the problem is the sensor signal.
Lower the rpm for a selected thread and see if it triggers for the lower range.
RICH