XYZ Probe with AZTP setting wrong Z zero

I understand. If I click the zero button the position changes to 0 without moving. If I click the “GO TO” button the position changes to 0 with the bit moving 1mm down. It is still 1-2mm above the workpiece after this move.

Well, I don’t know. Mine works fine on XY zero, but I haven’t even used the XYZ function.

All my projects are designed with the Z being referenced to the spoilboard rather than the surface of the material, so my Z-zero is done off the material.

I’ll have to do a setup on my machine before I can see if mine is working like yours.

I appreciate the attempt. It seems like an obvious bug but I don’t know where to go from here without doing an extra step to redo the Z zero each time.

I’m just busy with life right this moment, but will investigate more this evening. I want to know, too.

@SuperDodge I don’t have the auto touch plate, but in the interest of trying to figure this out, I have a question. What kind of end mill are you using and do you have the probe set to auto or tip?

Using an 1/8" end mill with the probe set to auto.

@SuperDodge I knew that it wouldn’t be that easy. :grinning:

I would advise to open a support ticket with Sienci.

@SuperDodge I did get a chance to test the XYZ probe on my Shapeoko 3XXL and did not have any problem setting XYZ zero with the AutoZero probe using a ¼" Dia. gage pin.

I remembered that I did have a problem with a tapered ball nose bit when I first got the probe block, but that went away after the first trial. The process “skipped” the last move to the XY zero location before it drove the bit into the bottom of my block creating a permanent indentation. It only did that once, though.

So weird that you don’t get the same results.

I’m sure I should be smart enough to find this on my own, but I can’t. How do I open a support ticket?

@SuperDodge I would have thought that between you, me and Tex, we would figure this out. Wrong! :grinning:

To open a support ticket, to here and complete the form

What version of gSender are you running?

Or of curiosity, shot in the dark, what’s your $13 value?

Don’t know about @SuperDodge yet, but my $13 = 0.

1 Like

I’m wondering if his is set to $13=1. I remember this causing issues in cncjs, but I’m pretty sure this was resolved with gSender early on.

Sorry for the delay. Just got home from work. $13=0

client $$
$0=10 (Step pulse time, μs)
$1=255 (Step idle delay, ms)
$2=0 (Step pulse invert, mask)
$3=5 (Step direction invert, mask)
$4=0 (Invert step enable pin, boolean)
$5=0 (Invert limit pins, boolean)
$6=0 (Invert probe pin, boolean)
$10=255 (Status report options, mask)
$11=0.020 (Junction deviation, mm)
$12=0.010 (Arc tolerance, mm)
$13=0 (Report in inches, boolean)
$20=0 (Soft limits enable, boolean)
$21=0 (Hard limits enable, boolean)
$22=1 (Homing cycle enable, boolean)
$23=0 (Homing direction invert, mask)
$24=100.000 (Homing locate feed rate, mm/min)
$25=2000.000 (Homing search seek rate, mm/min)
$26=25 (Homing switch debounce delay, ms)
$27=3.000 (Homing switch pull-off distance, mm)
$30=24000 (Maximum spindle speed, rpm)
$31=0 (Minimum spindle speed, rpm)
$32=0 (Laser-mode enabled as spindle, boolean)
$100=40.000 (X-axis travel resolution, step/mm)
$101=40.000 (Y-axis travel resolution, step/mm)
$102=200.000 (Z-axis travel resolution, step/mm)
$110=10000.000 (X-axis maximum rate, mm/min)
$111=10000.000 (Y-axis maximum rate, mm/min)
$112=1000.000 (Z-axis maximum rate, mm/min)
$120=500.000 (X-axis acceleration, mm/sec^2)
$121=500.000 (Y-axis acceleration, mm/sec^2)
$122=270.000 (Z-axis acceleration, mm/sec^2)
$130=845.000 (X-axis maximum travel, mm)
$131=850.000 (Y-axis maximum travel, mm)
$132=95.000 (Z-axis maximum travel, mm)
ok
1 Like

I am using v1.2.2 armv7| on a Raspberry Pi 5

If you just set Z-zero with the probe, is it better?
Do you have calipers to measure the thickness of the probe?

The z zero did work correctly.

However, after that test…

I have reflashed the pi and reinstalled gSender and do not have the same issue with the XYZ on the new setup.

I wish I had figured out the root cause but I’m back to work, regardless.

1 Like

@SuperDodge I’m glad that you are fixed up, RL. There was simply too much about your setup that I didn’t understand for me to be of any help. I’ll close this thread now as resolved.

1 Like