Hi all, When setting up an new project (simple X-Z axis, without probe), I was able to set all options and have the table running to my liking. As far as I know, the only open topic is the "Home all" process. The process starts with homing the Z-axis, which functions as it should (move until limit, back up, move till limit). When homing the X-axis, the axis moves until the limit switch and stops the movement without showing the alarm. After a certain amount of time an alert is triggered: " ALARM: 9 - Homing fail. Could not find limit switch within search distance. Defined as 1.5 * max_travel on search and 5 * pulloff on locate phases. [ $H ] ". So far I found no indications why the limit for the X-axis doesn't trigger the standard homing. The limit for both the X-axis and Z-axis functions during the troubleshoot check. Switching the cabling and/ or the limit switches didn't change anything to the process. The following Grbl settings are used: [17:18:53] [ $$ ] $0=10 ;Step pulse time, microseconds [17:18:53] [ $$ ] $1=255 ;Step idle delay, milliseconds [17:18:53] [ $$ ] $2=0 ;Step pulse invert, mask [17:18:53] [ $$ ] $3=7 ;Step direction invert, mask [17:18:53] [ $$ ] $4=1 ;Invert step enable pin, boolean [17:18:53] [ $$ ] $5=0 ;Invert limit pins, boolean/mask [17:18:53] [ $$ ] $6=0 ;Invert probe pin, boolean [17:18:53] [ $$ ] $10=1 ;Status report options, mask [17:18:53] [ $$ ] $11=0.010 ;Junction deviation, millimeters [17:18:53] [ $$ ] $12=0.002 ;Arc tolerance, millimeters [17:18:53] [ $$ ] $13=0 ;Report in inches, boolean [17:18:53] [ $$ ] $20=0 ;Soft limits enable, boolean [17:18:53] [ $$ ] $21=1 ;Hard limits enable, boolean [17:18:53] [ $$ ] $22=1 ;Homing cycle enable, boolean (Grbl) / mask (GrblHAL) [17:18:53] [ $$ ] $23=7 ;Homing direction invert, mask [17:18:53] [ $$ ] $24=150.000 ;Homing locate feed rate, mm/min [17:18:53] [ $$ ] $25=500.000 ;Homing search seek rate, mm/min [17:18:53] [ $$ ] $26=232 ;Homing switch debounce delay, milliseconds [17:18:53] [ $$ ] $27=2.000 ;Homing switch pull-off distance, millimeters [17:18:53] [ $$ ] $30=1000 ;Maximum spindle speed, RPM [17:18:53] [ $$ ] $31=0 ;Minimum spindle speed, RPM [17:18:53] [ $$ ] $32=0 ;Laser-mode enable, boolean [17:18:53] [ $$ ] $100=57.292 ;X-axis steps per millimeter [17:18:53] [ $$ ] $101=57.292 ;Y-axis steps per millimeter [17:18:53] [ $$ ] $102=57.292 ;Z-axis steps per millimeter [17:18:53] [ $$ ] $110=1000.000 ;X-axis maximum rate, mm/min [17:18:53] [ $$ ] $111=1000.000 ;Y-axis maximum rate, mm/min [17:18:53] [ $$ ] $112=1000.000 ;Z-axis maximum rate, mm/min [17:18:53] [ $$ ] $120=2.000 ;X-axis acceleration, mm/sec^2 [17:18:53] [ $$ ] $121=2.000 ;Y-axis acceleration, mm/sec^2 [17:18:53] [ $$ ] $122=2.000 ;Z-axis acceleration, mm/sec^2 [17:18:53] [ $$ ] $130=200.000 ;X-axis maximum travel, millimeters [17:18:53] [ $$ ] $131=200.000 ;Y-axis maximum travel, millimeters [17:18:53] [ $$ ] $132=200.000 ;Z-axis maximum travel, millimeters Does anybody have an idea? Thank you in advance! Best, Kay
Grbl by default is homing XY together. Not having a Y-axis is the reason for the alarm (it really didnt see Y triggering) Per your Grbl Settings backup, you unfortunately have an older Grbl 1.1 based controller (This is super easy to fix with just changing 2x Grbl Settings on a newer X32 running grblHAL) For the older grbl firmware you will need to do a custom compile telling it to only home X and Z (not Y) This is done in config.h grbl/grbl/config.h at master · gnea/grbl - compile instructions are in the Grbl Wiki If you don't have success with that, consider a BlackBox X32 docs:blackbox-x32:start [OpenBuilds Documentation] where its a lot easier (Simply set homing sequence in $44=4 and $45=1 to do Z first, then X)
