


The value in LightBurn is called "S-Value Max", in the Device Settings.

Once this is done, if the problem still persists, starting the cut in lightburn in absolute coordinates mode, an error 2 will appear in the console and the command will be ignored, then, check if any offsets have been stored with the $# command. To activate the software movement limits, $20 must be set to 1 (therefore the command to be given in the console is: $20 =1) The limits are stored in the variables $130 and $131 and in the case of my atomstack x 20 pro both must be set to 400. the check that when a movement to the laser axes is requested, this movement is within the physical limits of the machine ( x +400 y +400) otherwise it crashes. If you give the controller the command $$ you will see a list of settings which are stored in eeprom and in my case were:įirst of all I have activated the software limits, i.e. If you can homing the laser correctly (left side down) but when in a cut you try to start with absolute coordinates and your laser goes right banging, then, like me, you have some wrong settings stored in the GRBL parameters. If you too, as happened to me, have problems in the start from settings of lightburn with your laser atomstack x20 pro, I can give you my indications (completely personal and referring to my setup) to solve the problem in a short time. My experience : lightburn and atomstack x20 pro
