Z Probe trying to go past the the plate

Hi,

I’m trying to run my first job on my LR4 and when it gets to the Z Probe step it completely ignores the plate and tries to keep going :flushed_face:

When I run the Z Probe from the FluidNC WebUI, it works as expected; touches the plate and backs off the desired amount. I basically copied pasted the gcode from the Milling Basics page in the docs and added it to the CNC Program settings in EstlCam, as suggested. I can see in the terminal that the gcode used when I manually probe from the web ui is different, but I can’t figure out which part needs to change.

Here’s what I see in the terminal after manually probing from the webui:


G91
G38.2 Z-120 F20
ok
G90
G10 L20 P1 Z0.5
$J=G91 G21 F1000 Z10

Gcode produced by EstlCam attached

cut_test.gcode (2.4 KB)

here’s my start code:

G21
G90
G94
G92 X0 Y0
M0 (MSG Attach probe)
G38.2 Z-85 F200 (probe down set thickness )
G92 Z0.5
G1 Z10 F900
M0 (MSG Remove probe)

maybe it’s the G92 Z0.5 line that you’re missing?

It appears that the P0.5 at the end of G38.2 Z-110 F200 P0.5 is what was causing the probe to actually fail. Removing that caused the probe to succeed.

I also needed the G92 Z0.5 to properly zero it. Without out that, it was cutting in mid-air :grin:

So this is the start code that worked for me in case anyone else runs into a similar issue:

G21
G90
G94
G10 L20 P0 X0 Y0 Z0 (set current location to zero, survives reboot)
G0 X10 Y10 F2000 (move to probing location)
M0 (MSG Attach probe)
G38.2 Z-110 F200 (probe down)
G92 Z0.5 (set thickness/Z0)
G1 Z10 F900
M0 (MSG Remove probe)
M62 P1 (If used start spindle pin27 )
G00 X0.0000 Y0.0000 Z0.0000 F2400
G00 Z5.0000 F900
2 Likes

Hello fellow Jason. If you’re using FluidNC, that doesn’t make any sense. Using the P parameter is the correct way to do it so I’m confused. Technically, with the way you have it now will be slightly off because after the probe triggers, it still has to decelerate so it moves a bit past where the probe initially touches.

1 Like

I am using FluidNC. Not sure why it was misbehaving. Is it possible the value of P is the cause?

The value should be fine. I use that gcode without issue.

What version of FluidNC do you have?

I’ll go try your gcode file a bit later.

That would be awesome!

I’m on FluidNC v3.9.9 and WebUl version: 3.0.0.6

G21
G90
G94
G10 L20 P0 X0 Y0 Z0
G0 X100 Y100 F2400
M0 (MSG Attach probe)
G38.2 Z-110 F200 P0.5 (probe down set thickness )
G0 Z15 F900
G38.2 Z-110 F100 P0.5 (probe down set thickness )
G0 Z20 F900
M0 (MSG Remove probe)
M62 P1 (If used start spindle pin27 )

I just used this yesterday.

The newest version is 3.0.10.

Your original gcode worked fine.

3 Likes

Weird. I’ll try updating FluidNC and try again. Thanks for testing for me @jeyeager !

2 Likes

I just tried replacing my start code with this and it did the same thing; ignored the touchplate and just kept going.

I haven’t yet updated the WebUI because I checked the change list and there was nothing listed that sounded relevant. If anyone with more context thinks this update will make a difference I’m happy to try.

Otherwise, any ideas? It’s super weird that it works for others, but not me. There must be a setting somewhere that is different/wrong/missing/etc on my end. Any ideas where to start looking?

Use the $limits command in the webui to test your probe.

From there make sure the negative wire goes to the spindle, and the signal is to the plate itself.

That should let us know if there are any actual issues with the circuits.

I just ran $limits and confirmed that P, y, Y, x, z and Z all log as expected.

I also checked the wiring of my touchplate. The paddle is connected to the red wire, the clip to the black. I confirmed continuity with my volt meter. And I checked that the P showed in the logs regardless of which direction it is connected to the pins on the board; it did. Then I made sure it was connected in the same direction as the other limits: black toward the outside of the box red towards the inside.

In short, it appears (to this noob at least) that the touchplate is wired correctly and working as expected. (a little part of me wishes it wasn’t because that would be a straightforward, if tedious, fix)

Yea, I’m grasping at straws here a bit.

Do you have dust collection and if so is it grounded?

If I were in that situation, I might be inclined to re-flash FluidNC even if it was the same version.

Can you share your config.yaml file? Weird things can happen sometimes if there are things like extra spaces.

You could also try running it with debug enabled. I’d probably try that first.
$Message/Level=Debug

Restore to normal when done
$Message/Level=Info

1 Like

What kind of spindle are you using?

The Makita router y’all recommended and I currently have an 1/8” flat end mill in it.

The signal wire (paddle) is market with an “S” next to it, and the black should go to the clamps and the “G”.

I assume you mean the “S” and “G” are printed on the PCB, correct?

1 Like

Re-flashing is not a bad idea. It does test good though. Jason tested your gcode. I am pretty stumped.