I searched the forums but couldn't find a solution.
Please let me know if there is a solution.

Not a good idea, but I changed some things and it worked.
My solution is not the best.
I think there is actually a better solution.

good evening everyone.
The Mach4 probe was even more defective.
It's a photo feature.
After the inspection rod comes into contact, the detection rod does not move away from the surface and rises upward.
It's a terrible problem.
Do you guys care?

Hello everyone.

There were other bugs as well.
It is a function to measure the inner diameter.

phenomenon
After the measurement, the center shifts by the amount of X offset.

Look at the program.
It was caused by the inside of the green frame.
I corrected it like the red arrow.

The probe of Mach4 has other problems.
How do you all fix the Mach4 probe bug?
Please tell me the solution.

Hi,

How do you all fix the Mach4 probe bug?
Please tell me the solution.

To my knowledge you can't....its not a Mach4 fault but is the way that the ESS interacts with Mach4.

NFS claim its an ESS problem, and Warp9 claim that its a Mach4 problem and until one or the other company see an appreciate
the fault and start talking to the other company about it I don't believe there is a solution.

I just write my own probing code if I need something specific.

You could try Andy at Warp9, he is usually pretty responsive to claimed bugs.

Craig

Hello Craig.
I use it with ESS and BOB (MB3).
I think ESS has many users.

It's been about half a year since I moved to Mach4.
I spent a lot of time and money.

I was finally able to use the milling machine, and when I used it immediately, Probing malfunctioned and I was disappointed.

So I thought that some of you might have already solved the problem like me.
Therefore, I am asking everyone in this forum.

It is important to solve the problem.
There is no point in saying bad things about the company.

＞ I just write my own probing code if I need something specific.

I feel the same way.

About the problem of probing of Mac4 Hobby
Hello everyone.
There were two things that I found out by investigating so far.
No. 1
When moving in a straight line, I think that using G1 is the correct answer, but in the program, G31 is used. For this reason, the detection rod will stop when it reaches the specified distance.
Originally, I think that G31 is used in combination with an instruction that returns a measured value when it comes into contact within the specified distance. Therefore, since I continue to use G31, I thought that the detection rod would stop.

No. 2
It is a function called "2 Surface Centering".
We have to pay attention to this feature.
The detection rod will rise after coming into contact with the measurement surface.
Originally, it should retreat after contacting the measurement surface, and then rise.
Looking at the program, there was still a problem.
So I added a command to retract the detector bar.
This fixed the problem.

My conclusion
I don't think there are any problems with ESS.
I thought that it would work correctly if I corrected the defective part of the Mach4 DEMO program "mcProbing.lua".

Hi Toshio.K,
there may be a solution after all. There was a post on the Warp9 forum about this exact issue and Andy has indicated that there is a setting that can be made such that
the Lua code doe NOT hang when an unscessful G31 is made:

https://warp9td.com/index.php/kunena/7-general-discussion/9092-about-g31-and-ess#28980

Craig

Hi Toshio.K,

See attached pic of the ESS Plugin Probing tab.

Craig

Hi Toshio.K,
the lower of the two highlighted parts is very promising.

It suggests that if you add just one line of Lua code to the module that Mach4 will not be disabled on the report of a G31 failure, and in this thread
a G31 event which does not return a positive probe event is considered a failure by the ESS, but the NFS programmers did not anticipate that
a non-contacting G31 move would be treated as a failure.

Craig

Hello joeaverage.
I learned the meaning of the checkbox yesterday.
Then I unchecked it and probed with the original mcProbing.lua and it worked fine.

And also
I found the following article.
"http://Https://warp9td.com/index.php/kunena/7-general-discussion/8746-probing-error-bad-behavior-when-probing-fails?start=6"

"Mr. Bx3mE" in this article seems to be driving Mach4 by making a button and pasting the code on that button.
They were discussing M2010.
But I didn't know the concrete solution.