1891
General Mach Discussion / Re: How do you resume after a flame-out?
« on: December 07, 2019, 01:17:28 AM »
Hi,
as I said the RFH feature is about the most confusing and frustrating feature of Mach3. If I'm not mistaken Mach will not traverse
a Gcode program which contains sub-routines and maybe even macros. Its been over four years since I last used Mach3....I don't
now recall all the details.
I've never had much difficulty with Mach4. Unless there is a specific reason not to I would recommend you look closely at Mach4.
Several months ago NFS released a script based THC feature for Mach4.
As you know script (software) THC solutions have never worked with Mach3 by virtue of communication delays and buffering delays
inherent in Mach3. THC requires real-time hardware or near real-time motion controller like Machs parallel port.
Thus for Mach4 to have a script solution for THC is a major advantage over Mach3. It must be said the best THC is still done
by a real-time motion controller but the script option is very welcome.
Craig
as I said the RFH feature is about the most confusing and frustrating feature of Mach3. If I'm not mistaken Mach will not traverse
a Gcode program which contains sub-routines and maybe even macros. Its been over four years since I last used Mach3....I don't
now recall all the details.
I've never had much difficulty with Mach4. Unless there is a specific reason not to I would recommend you look closely at Mach4.
Several months ago NFS released a script based THC feature for Mach4.
As you know script (software) THC solutions have never worked with Mach3 by virtue of communication delays and buffering delays
inherent in Mach3. THC requires real-time hardware or near real-time motion controller like Machs parallel port.
Thus for Mach4 to have a script solution for THC is a major advantage over Mach3. It must be said the best THC is still done
by a real-time motion controller but the script option is very welcome.
Craig