For anyone thinking about upgrading to MachPro there are still issues being worked on. I have problems with reading Registers from m-code scripts. For me, and the RC ATC this is a problem I need to solve as I need a removable dust boot. As far as the program, it's nice... There are definitely QOL improvements over Mach4 and way beyond Mach3. ESS support appears to be working extremely well. Definitely some niggling little bits that need work at this time though. It is unforunate that Mach4 is being EOL'd at this time though. Maybe a discount given to those that already own Mach4 might be an option. I've spoken to Carl Eldridge on the phone and he seems like a great guy. I wish them ALL the success the in world on this endevour.

As far as the hardware I can't speak to it, but with all the ESS and cnc4pc parts I have kicking around, there was no way I could justify moving to the M-31.. Ethercat would be really nice, but it's also out of my budget as a hobbyist. Right now I'm working on my fourth CNC build in 15 years. I will be moving it over to MachPro once a few features are working. RC ATC, maybe script debug, IPC would be nice so that remote control is possible (almost working).

I would like to see them finish Mach4 so it's more usable. IPC on my win10 and win11 computers fail. This affects wxprobe screen which does not work at all for me. They have this great probing screen that's useless as it won't detect probes at all. :shrug: 

anyways, if anyone has ideas on why mcGetRegister() fails in a m-code script, I'm all ears. return code can be -17 or -27(??) occasionally, and sometimes 0 for rc. always 0 for value.

Hi,

Would you be able to send me your Mcode script?

In MachPro, Mcodes are handled a bit differently than what you may be used to. We use a file called UserMCodeModule for custom or modified MCodes. We are working on getting documentation on how this is done and what available API's can be used as there are a lot more than just what is available on the Mach core API list now.

First thing on that list before we get that information out is having the new APIs documented. We are working on that process now.

When it comes to Mach4, I will be working on doing some bug fixes to try and provide a stable and solid product. There will just be no new planned features for the product.  This will take some time however.

Here is my lua script which is causing me problems. mc.mcRegGetHandle() mc.mcRegValue() never returns values that are definitely in the registry. I had a couple of Mach engineers logged into that system to see what the issue was. handle return code is -17. and a 0. Value returns and error because a handle of 0 doesn't exist.

anyways, it's just a method of dropping a dust shoe and picking it up again from a RapidChange ATC. I know RapidChange is working on there wizard/scripts and MachPro as well.

Would you be able to send a profile or just an .ini as well?

Sure. Here is a profile I've been using for testing. It's not right for a machine, but it does allow testing such as lua scripts etc.

Thanks,

I'll take a look when I get the chance!