Homing not working. Soft limits issue

Community Discussion 🌎 Community
1

Installed NEMA 23 motor upgrade and 4080 extension kit on my Fox Alien. Surfaced the spoilboard and carved a grid. Just fine. No issues. Now I want to cut a test hole in a piece of scrap to check the fit with a pin I want to insert into the hole. Throws a “Soft limit alarm. G-code motion target exceeds machine travel.” What? I just machined a grid, and the scrap piece is anchored to the middle of the grid. I am in excess of the soft limit pullout distance ($27) in all directions. If I disable soft limits ($20), I can not jog the machine in any direction. Re-enabling soft limits was a struggle; everytime I enabled it and hit “apply settings,” it would jump back to disable. After several tries, it finally took, and I was able to jog again. Also, now when I home the machine, it does not set X and Y to zero. Comes up with negative numbers. Worked fine when I surfaced and cut the grid. I didn’t change anything since. This all happened the same afternoon.

Below are my firmware settings. Hopefully, someone can help. Perhaps gSender changed something on it’s own, but I don’t see a culprit.
client $$
$0=10 (Step pulse time, ÎŒs)
$1=255 (Step idle delay, ms)
$2=0 (Step pulse invert, mask)
$3=3 (Step direction invert, mask)
$4=0 (Invert step enable pin, boolean)
$5=0 (Invert limit pins, boolean)
$6=0 (Invert probe pin, boolean)
$10=3 (Status report options, mask)
$11=0.010 (Junction deviation, mm)
$12=0.002 (Arc tolerance, mm)
$13=1 (Report in inches, boolean)
$20=1 (Soft limits enable, boolean)
$21=1 (Hard limits enable, boolean)
$22=1 (Homing cycle enable, boolean)
$23=3 (Homing direction invert, mask)
$24=200.000 (Homing locate feed rate, mm/min)
$25=1000.000 (Homing search seek rate, mm/min)
$26=250 (Homing switch debounce delay, ms)
$27=3.000 (Homing switch pull-off distance, mm)
$30=30000 (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=800.000 (Z-axis travel resolution, step/mm)
$110=3810.000 (X-axis maximum rate, mm/min)
$111=3810.000 (Y-axis maximum rate, mm/min)
$112=500.000 (Z-axis maximum rate, mm/min)
$120=300.000 (X-axis acceleration, mm/sec^2)
$121=300.000 (Y-axis acceleration, mm/sec^2)
$122=30.000 (Z-axis acceleration, mm/sec^2)
$130=400.000 (X-axis maximum travel, mm)
$131=800.000 (Y-axis maximum travel, mm)
$132=90.000 (Z-axis maximum travel, mm)
ok
Thanks.

2

I would try $10=1, that’s the default for Sienci machines and I think it might mess with were gSender ‘thinks’ it is if it’s not 1.

I also think that $13 should be 0 even if you work in inches. You just need to select inches in gSender settings (cogwheel).

3

Thanks. Changing $10 did not make a difference. I rebooted the computer, then when I homed, X and Y are zeroed
once. Homed again, and it gave me -1.7 and -2.4 for x and y. I’m still getting the error that I’m exceeding the machine limits. This never happened prior to the NEMA 23 and 4080 upgrade. Yes, I did change the maximum Y travel in firmware settings. I’m pretty sure it may have something to do with the soft limits, but don’t know what.

4

Remember, I was able to surface the spoilboard (using gSender surfacing) and add a grid (designed with Vcarve) with no problems. That’s why this is baffling.