Hi craig.

Thank you for the long sentence.
I found "Motion plugin probing procedure."
I want to be able to understand.


I also didn't get good results when I tried to simulate "TOUCH" using a manual switch.
I've had success from time to time, so I got the point.
It was successful by pressing and holding the switch.

However,
I don't think this issue is due to a manual switch.
Because, if you look at the behavior of video.
https://www.youtube.com/watch?v=9LvV6iC3zmY
1, plobe descends.
2, plobe does not come into contact and stops temporarily at a certain position. (Video 3: 50 ~)
3, Next, it automatically contacts the front, back, left and right.

My situation
1, plobe descends.
2. It automatically descends to "Z measurement position" and mach4 stops. "ERROR: No contact with probe" is displayed.


In other words, I haven't turned on the manual switch, so I don't think the manual switch is the cause.


We would like to thank Mr. Craig for the MPG program.
I reduced the program for the X Y Z axis and attached an LED for the X Y Z axis so that I could see On Off.

Hi,

In other words, I haven't turned on the manual switch, so I don't think the manual switch is the cause.

I think you may have found the problem.

As I posted earlier:
g31 z-5 f200      gets interpreted as:
g1 z-5 f200,       but would stop at a point where the probe makes contact, lets say z=-2.5mm. But what happens if the
probe DOES NOT make contact, then the machine will drive to z=-5mm WITHOUT a probe detection event and Mach will know
that the probe is faulty or for some other reason the surface was not detected and post a "ERROR: No contact with probe"
statement.

So the fault you are describing COULD be caused by a manual probe button NOT being activated (to simulate a natural probe event)
BEFORE Mach reaches it g31 endpoint.

Craig

Thank you, Craig.

＞ So the fault you are describing COULD be caused by a manual probe button NOT being activated (to simulate a natural probe event)
BEFORE Mach reaches it g31 endpoint.


that's right.
If the manual switch is turned on before the Probe reaches the "Z measurement position", the probe will contact the front, back, left and right four times each.

But I can't find a solution.

Hi,
if the controller does NOT detect a probe event BEFORE it gets to the g31 endpoint, its a fault.....end of story.
I'm not quite sure what you would expect.

Essentially what you are saying when you execute a g31 block like g31 z-5 f200 is 'advance to z=-5mm but expect to stop
before you get there', if you don't get the signal to stop, ie a probe event what do you want Mach to do? It did not detect the surface
it expected to find......thats a fault isn't it?

Craig

Looking at the video, the probe goes down and pauses at "Z measurement position",
Next, it looks like the probe is moving back and forth and left and right.

However, in my case, it is stopped at "Z measurement position".
I just don't know the cause. I am troubled.
If you know any solution, please let me know.

Isn't the cause that the real XY axis motor is connected to the BOB?

Hi,
you are using the Probing module, the fault could be in the code, or it could be your probe simulation set-up, or it could
be a machine fault.

Why don't you try writing some MDI code to test the g31 cycle, your machine and simulation procedure?
Once you have proven all those to your satisfaction THEN try running the module code. Note tat the Lua source code is
freely published for you to inspect, read, edit as you wish.

Mach4Hobby/Modules/mcProbing.mcs

Craig

I used MDI.
g31 z-5 f200

Then
ESS: failure! Probe0 never hit or the allowed distance was traveled. Swiiiitching from

It looks like this, is the motor tab setting wrong?
I attached a photo.
I set the motor with Stepping Motor Cont Per uint400 pulse / rev.

excuse me.
Below is the History.

ESS: failure! Probe0 never hit or the allowed distance was traveled.
Switching from probing to normal state.

Hi,
No, the problem is that the probe event is not happening before the g31 block hits its end point.

There is (probably) no fault of the motor, no fault (probably) of the mcProbing module code, it's operator error,
you are not activating the probe button before the g31 finishes.

As an experiment try:
g31 z-5 f10
If the probe starts a z=0 it will take 30 seconds before the Z axis descends to z=-5mm and should give you plenty of time to hit the button
before the window of opportunity finishes.

Craig