Try to deactivate hard limits ($22) and homing cycle ($23). If the Laser Test button works after that, then you should update Grbl again. There was an issue with the limits and homing which has been solved the last days.
with $22=0 and $23=0 Laser Test Button won´t work.
current settings:
Grbl 1.1e [’$’ for help]
$0=10
$1=25
$2=0
$3=0
$4=0
$5=1
$6=0
$10=0
$11=0.010
$12=0.002
$13=0
$20=0
$21=0
$22=0
$23=3
$24=500.000
$25=1000.000
$26=250
$27=3.000
$30=100
$31=0
$32=1
$100=106.670
$101=106.670
$102=250.000
$110=17500.000
$111=17500.000
$112=500.000
$120=2500.000
$121=2500.000
$122=10.000
$130=1160.000
$131=440.000
$132=200.000
Soft and Hardlimit deactivated didn´t solve the Laser Test Button issue.
Test if you can switch the laser on/off manually. Send “G1F20” then “M3S10” to switch the laser on and “M3S0” or “M5” to switch it off.
In Grbl 1.1e you must be in G1, G2 or G3 mode to switch the laser on (security reason).
G1F20 nothing happens
M3S10 Laser is on
M5 Laser is off
The G1F20 does nothing you can see, but it switches the controller to G1 mode, which is needed to get the laser on.
If the commands work manually, but not the laser test button, then you either have a too short laser test duration configured (in milliseconds) or you don’t have the actual LW version.
Output:
Recv: <Idle|WPos:70.001,70.001,0.000|FS:0,0>
laserTest: Power 10, Duration 2500
Sent: M3S10 Q: 2
Sent: G4P2.5 Q: 1
Sent: M5S0 Q: 0
Recv: <Idle|WPos:70.001,70.001,0.000|FS:0,0>
Your version of LaserWeb is Up To Date!
Content of version.txt: 30476
Do a git pull anyways, as we don’t increase the version on each push.
I did a new git clone and npm install. Now it works, thanks a lot!