Machsupport Forum
Mach Discussion => General Mach Discussion => Topic started by: Toshio.K on December 29, 2021, 05:11:56 PM
-
I am using Mach4 Hobby DEMO.
There is a problem in "Probing Outside Corner".
The probe (G31.1) works as follows and does not measure.
I think it works like the Mach Support video "Probing Outside Corner Part 2 in probing".
URL:https://www.youtube.com/watch?v=ole5nCpsxlU
I think there is something wrong with the program.
Please tell me how to solve the problem.
・ Set all X, Y, and Z axes to "0".
・ Click Measure Corner
・ 20mm probe moves and stops.
・ "No contact with probe" is displayed.
* Probe does not move in the X direction.
-
Hi,
This post should be on the Mach4 General Discussion board, no doubt tweakie will shift it in due course.
The problem you describe is not a fault, its just the way some controllers handle a G31 error.
It is common practice when generating automatic Gcode to use G31 as a regular move rather than G1. This is because if the probe accidentally touches
something the machine will stop rather than carry on until the end of the normal G1 move and crunch the probe. It like a safe way to move somewhere
without damage.
What happens if however you code G31 X20? The machine will travel at the prevailing G1 rate to X=20, if it does not contact something along the way.
If it gets to X=20 WITHOUT touching something it will report an error, ie 'No contact with Probe'. Some controllers will just sit there and sulk, there is an error
that needs to be sorted, whereas other controllers carry on.
There are a number of posts on the Mach4 board that cover this.
Craig
-
Good morning, Craig.
There was a problem with the program even during "Probe calibration".
There should be something wrong with the program (mc.Probing.lua).
There should be a bug in that it doesn't behave like a video.
But I don't know.
-
Hi,
There should be something wrong with the program (mc.Probing.lua).
That is incorrect, there is no fault with the probing module, but rather some motion controllers handle it better than others.
Craig
-
I'm using ESS and MB3.
The probe is also turned on and off properly.
There are also operations that do not cause problems with probing.
Therefore, I think there is a problem with the program.
"Probe calibration" had a problem with the program, so I think it's the same problem this time.
I saw an article in the forum that caused a similar problem. I don't think I'm the only one.
-
Hi,
There are also operations that do not cause problems with probing.
Therefore, I think there is a problem with the program.
I'm sure you think there is a problem, so why don't you research the threads on the matter on the Mach4 board, you may come to a different conclusion.
Craig
-
Hello everyone.
There were some bugs.
I was able to make some corrections.
Anyone will be charged for a license, but will that fix the problem with the program?
Art Soft, if you want to take money, please eliminate the problem.
Thank you.
-
Hi,
I keep telling you its the way the ESS handles the exception, its not a Mach4 fault. You can complain as much as yu like but Artsoft
cannot fix it.....its just the way the ESS works.
You could try Andy at Warp9.
Craig
-
Happy new year everyone.
I look forward to working with you this year as well.
and,
Thank you for the information, Craig.
This is the program that is causing the problem. If this is left as it is, it will advance 20 mm and stop, and will not advance in the X-axis direction.
Can anyone please tell me the solution?
Thank you.
The program that is causing the problem
mcProbing.lua
Line 1137
rc = mc.mcCntlGcodeExecuteWait (inst, string.format ("G% .1f Y% .4f F% .1f", ProbeCode, YMeasurePos, FastFeed))
-
Hi,
I don't think there is any fault with that line.
What happens is that the machine advances but does not encounter a probe event. The ESS regards this as a fault and hangs up.
My ESS does a similar thing. If the machine encounters a probe event before the end of the 20mm move then it works fine.
Its just how the ESS handles the exception. Plenty of other people have had the same issue. Have a look on the Mach4 board and you will find
plenty.
-
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 (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.
"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.