My problem is that with eleksmaker I am getting alarm from Z-switch even thought I have tried to configure the software to use only a X and Y limit switches. Below more detailed information and questions.
I am running the latest own build and configured 1.1h from gnea/grbl with eleksmaker A3 on manase v3.2 board with following settings
I have both the home and end limit switches for X and Y configured in Normally Closed (NC) mode. Both X and Y are working ok and triggering event only when switches are pressed
X is connected to D9
Y is connected to D10
Z on D12 pin is not connected as laser position is fixed on my device
(#define VARIABLE_SPINDLE enabled on config.h) which means that Z is expected to be on D12 and laser PWM on D11
I have tried to disable Z-switches by defining in config.h
(Not sure whether there is some more exact way of saying that do not check z-switches states as they are not used/needed)
define HOMING_CYCLE_0 (1<<X_AXIS) // COREXY COMPATIBLE: First home X
define HOMING_CYCLE_1 (1<<Y_AXIS) // COREXY COMPATIBLE: Then home Y
1) When I start the eleksmaker/grbl with any of the x or y switches pushed down and check the voltages on D9, D10 and D12 I see
D9 = 0V
D10=0V
D12=4.7V
and if I check the status on grbl serial port by using command "?" I see report that Z is triggered
?<Alarm|MPos:0.000,0.000,0.000|Bf:15,128|FS:0,0|Pn:Z|WCO:-43.000,-89.000,0.000>
2) If I press X-switch down, I see report that X and Z are triggered
?<Alarm|MPos:0.000,0.000,0.000|Bf:15,128|FS:0,0|Pn:XZ>
3) If I press X-switch down, I see report that X and Z are triggered
?<Alarm|MPos:0.000,0.000,0.000|Bf:15,128|FS:0,0|Pn:YZ|Ov:100,100,100>
So this means that X and Y switches are working but Z is always reported even though I tried to disable it in config.h
I have tested that I can disable the Z limit switch reporting with HW mod by wiring the D12 pin to ground but I would prefer a possibility to disable the reporting of certain limit switches via software settings without need for any hw changes.
Is this already possible in some way that I have missed in documentation or are there some non-upstream patches that can achieve this?
lamikr
commented
3 years ago
My problem is that with eleksmaker I am getting alarm from Z-switch even thought I have tried to configure the software to use only a X and Y limit switches. Below more detailed information and questions.
I am running the latest own build and configured 1.1h from gnea/grbl with eleksmaker A3 on manase v3.2 board with following settings
define HOMING_CYCLE_0 (1<<X_AXIS) // COREXY COMPATIBLE: First home X
define HOMING_CYCLE_1 (1<<Y_AXIS) // COREXY COMPATIBLE: Then home Y
$1=25
$2=0
$3=3
$4=0 $5=1 $6=0 $10=19 $11=0.010 $12=0.002 $13=0 $20=0 $21=0 $22=1 $23=3 $24=25.000 $25=500.000 $26=250 $27=1.000 $30=1000 $31=0 $32=0 $100=80.000 $101=80.000 $102=80.000 $110=800.000 $111=800.000 $112=800.000 $120=100.000 $121=100.000 $122=100.000 $130=150.000 $131=150.000 $132=150.000
1) When I start the eleksmaker/grbl with any of the x or y switches pushed down and check the voltages on D9, D10 and D12 I see
So this means that X and Y switches are working but Z is always reported even though I tried to disable it in config.h I have tested that I can disable the Z limit switch reporting with HW mod by wiring the D12 pin to ground but I would prefer a possibility to disable the reporting of certain limit switches via software settings without need for any hw changes.
Is this already possible in some way that I have missed in documentation or are there some non-upstream patches that can achieve this?