I assembled my laser engraver using CNC Shield and GRBL, I have already tested cutting and engraving, everything works. But as soon as I connected the limit switches, it stopped driving. When idle, I click on the limit switches and the program writes “ALARM: 1
A hard limit has been triggered. The machine’s position is likely lost due to the sudden and immediate stop. Re-targeting is strongly recommended.” Both limit switches work, but after $H it doesnt move and the console displays “ALARM:9
Pointing error. The limit switch could not be found within the search distance. Defined as 1.5 * max_travel during search and 5 * offset during search stages.
ok”
Looks like the switches are recognized to be activated all the time. Try to invert them ($5=1). You can test by sending a question mark “?” in the console window and check the output. There is a section Pn: which shows the activated limit switches.
When i set $5=1, then i have another error
“ALARM:8
Pointing error. During the cycle, it was not possible to reset the limit switch when moving. Try increasing the tap setting or check the wiring.
ok”
I just read your post again and I got it wrong. Your setting was correct and the output shows that all switches work. So $5=0 is correct. If you hit the switches and get the hard stop message, that’s fine and should be like this. Be aware, that after a hard limit trigger event, you probably need to power cycle the board to make it work again.
Regarding homing:
You set a workspace size of 500x500, is that correct? Your speeds are extremely slow compared to that size. Which driving mechanism do you use? If it is a standard mechanics, set
$24=50
$25=1000
$110=5000
$111=5000
$120=500
$121=500
Since you are driving such slow, you might run in a timeout.
Yep, i already cut and engrave some plywood, they works normal (with turned off hard limits), problem only with homing + hard/soft limits (G28, $H doesnt matter it always says the same)
Ah, another idea. Which firmware version did you use? Standard grbl from the GitHub repository? Or something else? Maybe it tries to home Z first. Check if you can home a single axis via $HX or $HY (but the single commands also need to be enabled in firmware).