rc = mc.mcCntlGcodeExecuteWait(inst, string.format("G%.1f Z%.4f F%.1f", ProbeCode, ZMeasPos, FastFeed))
mm.ReturnCode(rc)
rc = Probing.CheckProbe(1, ProbeCode); if not rc then; do return end; end

if you replace the two instances of the above code in the mcProbing.lua with :


rc = mc.mcCntlGcodeExecuteWait(inst, string.format("G0 Z%.4f F%.1f", ZMeasPos, SlowFeed))
mm.ReturnCode(rc)

it seems to solve the issue. Double check before full use as I'm no lua expert but it seemed to work for me

I think I found a better solution in the Warp9 documentation. Hopefully it helps somebody because it certainly stumped me for the better part of a weekend.

Warp9 Documentation:
Probing in Mach4
http://documentation.warp9td.com/Shared/Mach4/Probing/Probing.htm#:~:text=ESS%20%3E%20Software%20Mach4%20%3E%20Probing%20in%20Mach4%20

About half-way down the document under "The Probing Config Tab" header is the solution that worked for me.

Here's the gist of it.

In the ESS configuration window under the "Probing" tab you just uncheck "Probe Failure Disables Mach". Then run the calibration sequences and be sure to turn "Probe Failure Disables Mach" back on when you're done.

I don't know if it's a particularly safe solution, but it worked.

I think I found a better solution in the Warp9 documentation...
I don't know if it's a particularly safe solution, but it worked.

I am pulling my hair out over this for the past couple of days. Never occured to me to take a peek at the Warp9 stuff.

In fact I was going to search again and post some questions. Thank you for saving me the effort!

I am crawling to the shop later today and I will run through this documentation and see if that fixes my problems.

Thanks, HeyNoSeriously

From the link posted...

Why don't I change how the ESS operates? If I did, I would be changing the operating behavior for tens of thousands of other customers, and they would be very surprised by this change in probing behavior.  Besides, if probing fails in GCode, Mach4 and the GCode should stop.

Ugh! Really?

I need a more modern and standards based controller. I just don't buy the whole "stability" argument anymore.

WARNING!

If you have an AvidCNC machine and they built your control box, disabling this feature WILL CAUSE YOUR MACHINE TO CRASH!

I do not understand why. My machine is "typical" as per AvidCNC specification. The homing sequence after this is disabled will go until it hits the limit and does not perform the back-off which means your machine is now "somewhere near home" but not homed. If you have an ATC you will be running into your posts or smashing your carousel.

I am going to ping AvidCNC about this. Wow! Talk about a mess.

HeyNoSeriously, nice to meet you.
Thank you for your feedback.

I am aware that this is a problem with ESS.
At that time, regarding this problem, on the Warp9 forum, I was told that there were two solutions.

I tried your method, but it didn't work for me.
That's too bad.

HeyNoSeriously, nice to meet you.
Thank you for your feedback.

I am aware that this is a problem with ESS.
At that time, regarding this problem, on the Warp9 forum, I was told that there were two solutions.

I tried your method, but it didn't work for me.
That's too bad.

Yep, seriously causes me troubles too. If you have an ESS you cannot use the Mach4 probe routines.

Thus you cannot use the stock probing, stock angle, surface mapping or any of those advanced features you paid all that money for. All for the low, low price of that sad little ESS with the slow clock, bare minimum I/O and limited channels.

I think there are two solutions to this problem.
So far I think my Mach4 is working fine.

I think there are two solutions to this problem.
So far I think my Mach4 is working fine.

Ok, do I have to pay or something to get these two solutions of yours? 

The solution is free.
1. Remove the check.
2. Look at the bottom of the next page.
http://documentation.warp9td.com/Shared/Mach4/Probing/Probing.htm#:~:text=ESS%20%3E%20Software%20Mach4%20%3E%20Probing%20in%20Mach4%20
"This method modifies the program."
"I stopped because the program was long."
I think it's easier and better to remove the check if you don't make a mistake in using probing.