341
General Mach Discussion / Re: Mach 3 Threading Hangs
« on: March 31, 2019, 10:05:31 PM »Sorry, I wasn't clear in my description of the signal I have. At 500 rpm, it's a pulse that's about 5% duty signal. By "square wave," I just meant that the signal is clean with square edges as if it had been shaped with a Schmitt trigger rather than the somewhat sinusoidal raw signal off an opto-sensor. It's a roughly 6ms pulse out of about 120 ms that it takes the spindle to make a revolution at 500 rpm.
--
On a related topic, I don't understand why application of a UC300ETH with Mach 3 requires the use of a full A/B+Index input. From Mach's viewpoint, what has changed? Does the UC plugin actually change the Mach 3 trigger code/behavior? If I understand the default Mach 3 setup instructions, the threading trigger normally functions with a single index input of 200us or longer. As a related data point, Mach is happily taking the single input pulse and giving me the correct actual spindle speed.
OK
Thanks for your explanation.
Engineering-wise people don't refer a pulse to a "square-wave".
"Square Wave Waveform (by definition) is symmetrical in shape and has a positive pulse width equal to its negative pulse width resulting in a 50% duty cycle".
UCCNC - not good enough for lathe - turning. Does not support G32 only G76 in threading
MACH4 - Does not support G32 only G76. BUT UC300ETH does not support MACH4 THREADING using G76.
So the threading in MACH3 supporting both G32 and G76 are all MACH3 features and has not much to do with UC300ETH.
If it is me,
I would try to satisfy MACH3's necessary conditions even though an external motion controller is used
The people in Europe do not do threads based on TPI (which is a superior Imperial design) That may be why CNCDRIVE people maybe trying harder because metric threads have very different inferior design. Rotate a 1.6mm metric thread 16 times - you get 25.6mm which is NOT = 1 inch. Rotate a 16tpi thread 16 times and you get exactly 1 inch.