I notice LaserWeb4 will fire the laser while checking size. Is there someway to turn this feature off?
That could be a bug. @cprezzi
Have you set up laser test?
If check size is executed as a G1 move instead of a G0 move the laser would fire
I did not set up laser test. I’ll look into it. Thanks.
@Ariel_Yahni_UniKpty No bug, that’s by design 
“Check Size” is using G1, so that you can switch on “Laser Test” before checking the size. This is very usefull for diode lasers.
If you left the laser on after the last job (no M5 in end-code), or activated it manually with M3, then it will fire on check size.
On a CO2 you should always switch the laser off (M5) at the end of a job, otherwise manual G1 would also fire!
I have added M5 to the default End-Gcode settings now.
@cprezzi I do understand the reason but just to be clear, even if I don’t have test button set up, check size will fire the laser anyway?
The reason i ask it because Theres some users with K40 upgrades that use laser pointers so they dont need to fire the laser or use the test button. Also im not sure how low you can go on power on a CO2 to not leave a mark
@Ariel_Yahni_UniKpty Are you using Smoothie or Grbl on that machine?
The default “Laser Test Power” is 0, so even with Laser Test on it should not fire.
@cprezzi Im on grbl. I am using test button but haven’t used check size yet.
My question is: check size depends on test button setup or not to? If it does that’s good as the user allready typed a value different from 0. But in any case I would prefer to press test button and then to a check size . This is based on what issue above about co2 user that allready have laser pointers.
In the end it’s less confusing even if you are doing it automatically that the user turn on the test and then check.
That’s how I see it.
@Ariel_Yahni_UniKpty “Check Size” does not change the laser state (M3/M4/M5), it just executes four G1 moves around the object.
If M3 or M4 is active, a G1 will fire the laser, if M5 is active (=laser off), the laser will not fire.
You should always make sure that your jobs end with M5, otherwise the laser is still activated after the job and will fire on a G1, G2 or G3.
I allways set my End-Gcode to:
M5 ; deactivate laser
G0X0Y0 ; goto XY zero
M2 ; End Job
Ok, is this the same for smoothie and GRBL? I just don’t want people having random laser on.
Yes, it’s the same for smoothie.
I’m thinking if I should insert a M5 after every job in lw.comm-server. It doesn’t make any sense to leave M3 or M4 on.