Homing Cycle Issue - Z Axis doesn't home

Hi all,

Having trouble with the Z-axis when I run a homing cycle in CONTROL v1.0.149. The Z-axis doesn't even move when I hit Home All, though I can trip the limit alarm if I jog or manually toggle the switch.

Toubleshooting:

• Verified electrical continuity
• Validated that the switch works in the troubleshooting menu

Machine: LEAD 1010
Controller: BlackBox

[17:03:30] [ $$ ] $0=10 ;Step pulse time, microseconds

[17:03:30] [ $$ ] $1=255 ;Step idle delay, milliseconds

[17:03:30] [ $$ ] $2=0 ;Step pulse invert, mask

[17:03:30] [ $$ ] $3=4 ;Step direction invert, mask

[17:03:30] [ $$ ] $4=1 ;Invert step enable pin, boolean

[17:03:30] [ $$ ] $5=0 ;Invert limit pins, boolean

[17:03:30] [ $$ ] $6=0 ;Invert probe pin, boolean

[17:03:30] [ $$ ] $10=1 ;Status report options, mask

[17:03:30] [ $$ ] $11=0.020 ;Junction deviation, millimeters

[17:03:30] [ $$ ] $12=0.002 ;Arc tolerance, millimeters

[17:03:30] [ $$ ] $13=0 ;Report in inches, boolean

[17:03:30] [ $$ ] $20=0 ;Soft limits enable, boolean

[17:03:30] [ $$ ] $21=1 ;Hard limits enable, boolean

[17:03:30] [ $$ ] $22=1 ;Homing cycle enable, boolean

[17:03:30] [ $$ ] $23=3 ;Homing direction invert, mask

[17:03:30] [ $$ ] $24=100.000 ;Homing locate feed rate, mm/min

[17:03:30] [ $$ ] $25=1000.000 ;Homing search seek rate, mm/min

[17:03:30] [ $$ ] $26=250 ;Homing switch debounce delay, milliseconds

[17:03:30] [ $$ ] $27=5.000 ;Homing switch pull-off distance, millimeters

[17:03:30] [ $$ ] $30=16000 ;Maximum spindle speed, RPM

[17:03:30] [ $$ ] $31=0 ;Minimum spindle speed, RPM

[17:03:30] [ $$ ] $32=0 ;Laser-mode enable, boolean

[17:03:30] [ $$ ] $100=199.100 ;X-axis steps per millimeter

[17:03:30] [ $$ ] $101=199.100 ;Y-axis steps per millimeter

[17:03:30] [ $$ ] $102=199.100 ;Z-axis steps per millimeter

[17:03:30] [ $$ ] $110=2500.000 ;X-axis maximum rate, mm/min

[17:03:30] [ $$ ] $111=2500.000 ;Y-axis maximum rate, mm/min

[17:03:30] [ $$ ] $112=2500.000 ;Z-axis maximum rate, mm/min

[17:03:30] [ $$ ] $120=150.000 ;X-axis acceleration, mm/sec^2

[17:03:30] [ $$ ] $121=150.000 ;Y-axis acceleration, mm/sec^2

[17:03:30] [ $$ ] $122=150.000 ;Z-axis acceleration, mm/sec^2

[17:03:30] [ $$ ] $130=810.000 ;X-axis maximum travel, millimeters

[17:03:30] [ $$ ] $131=730.000 ;Y-axis maximum travel, millimeters

[17:03:30] [ $$ ] $132=90.000 ;Z-axis maximum travel, millimeters

[17:03:30] [ $$ ] ok

[17:03:30] [ $I ] [VER:1.1g.20181112:LEADMACHINE1010]

[17:03:30] [ $I ] [OPT:V,15,128]

[17:03:30] [ $I ] ok

 

Edited my post for clarity. I also just noticed that Hard Limits are enabled so I'm going to disable hard limits and try again.

The step enable setting has nothing to do with limit switches. That setting purely refers to stepper motors.

$4=1 should be right according to the LEAD 1010 docs:
OpenBuilds LEAD CNC

 

@Award,

This is a post from another person in another forum that explains the differences. Hope it's helpful to you.

Looking at things from the grbl perspective, the term "limit switch" only applies for the X-carve if you use hard limits ($21=1) .

Looking at things from the grbl perspective, all other cases for the machine the switches are "homing switches".

Homing switches allow soft limits ($20=1) to work. For this case the "limits" depend on having done the homing cycle and on the low end the limits are 0,0,0 and the limits on the high end are set by $130, $131, and $132. After the homing sequence the switches are ignored. Cannot get a false trigger after homing sequence is complete.

For soft limits the destination of your G-code commands are checked to see if they are out of bounds - if they are out of bounds, grbl alarms without moving the machine.

For hard limits the error is only detected if the machine actually does a move that trips a "limit switch".

You can have both soft limits and hard limits turned on at the same time. This configuration is susceptible to false triggers without either, shielded switch wiring or a low pass filter on the switch input.

Both soft limits and hard limits depend on the integrity of the electronics. In other words if your electronics don't function properly then neither will your soft or hard limits.

 

OK, so I think I figured out the issue with Hard Limits becoming enabled.

When I toggle "Limit Switches Installed" in CONTROL under Grbl Settings,the $21 value is being toggled to 1. I manually over rode the setting, so now I have:

[15:23:46] [ $$ ] $20=0 ;Soft limits enable, boolean
[15:23:46] [ $$ ] $21=0 ;Hard limits enable, boolean
[15:23:46] [ $$ ] $22=1 ;Homing cycle enable, boolean
[15:23:46] [ $$ ] $23=3 ;Homing direction invert, mask

In my understanding, this should be the proper configuration.

My Z-axis still doesn't try to find the limit switch, regardless of the settings for $20, $21, or $22. I've tried every iteration of 20/21. Instead, the machine immediately moves X, then Y to machine left/front. This tells me that homing is, in fact, enabled and set appropriately ($23=3). In my past experience, previous grbl-based machines I've owned moved z first, then X & Y simultaneously or moved all 3 axis at the same time when seeking the homing switches.

 

@Award

No problem. Happy to help.

 

So, the Console was reporting [VER:1.1f.20170801:LEADMACHINE1010].

Taking your suggestion as a queue, and because I kept getting "FLASH FAILED" when trying to flash the same version, I flashed to the ACRO firmware, and back to the firmware for the Lead Machine. Once I power cycled, all seems to be well, and all 3 axis now home properly