When you get an error message with a GCode laser like this one, it can be helpful to look at the original open-source error message list to see what the controller is trying to tell you.
Error messages: grbl/doc/csv/error_codes_en_US.csv at master · gnea/grbl · GitHub
Alarm codes:
grbl/doc/csv/alarm_codes_en_US.csv at master · gnea/grbl · GitHub
There are two types of Homing errors that are common here.
If the engraver is supposed to auto-home, it has switches or current detection to tell the controller to stop moving toward home because it’s arrived. If the switch or current detector has failed or is set up incorrectly it can’t tell the controller to stop so it will do what you’re describing here.
If the controller is not equipped with switches or current detection and if/when it is instructed to home, it will overshoot and also do what you’re describing.
When homing, If the engrave head runs away from the switches, this is a different problem. This is caused by an incorrect setting in the controller or a wiring problem. These are factors that LightBurn doesn’t control when auto-homing but this can usually be adjusted without rewiring.
The temporary fix for all of this in LightBurn is to click Edit, click Device Settings, and turn off the switch marked “Auto-home on startup” - Then carefully click OK in the bottom row. Lightburn won’t send the command to home. You physically move the engrave head to the home position before powering up the laser engraver.
It’s now set for an engraver that has no switches or current sensing (no auto-homing).
So, if Lightburn connects to the laser now, in the Console window type the following lines one at a time followed by Enter:
$$
$RST=$
$$
$i
Scroll back in the Console window, Select and copy all the output and paste it into a reply here.
We should see the factory settings which often tell us that your laser engraver has auto-homing or doesn’t have auto-homing.
We’re all right here. Best to avoid staircases when asking for this.
(grey-beard humor… sorry… )
I can’t stress this enough. This is almost always a step backward and almost always moves people further from the solution.
That said, the settings are probably still available in an lbprefs file. If you do a brute-force search of your hard drive for lbprefs files, you may find an early file is still entact. LightBurn saves the last 50 versions (which is the most amazing and useful thing I’ve ever seen). If you have lbprefs files from before and after it stopped working, please drag and drop them into your reply here. I’m happy to take a look.
The white-screen symptom is very important.
This may be a hardware problem.
If one of the changes is unintentionally leaving the SD card in the controller and attempting to connect with the USB cable this could be the reason.
With some controllers, the USB serial competes with the data lines used for loading the SD card info into the controller. Some of the controllers also show conflicted data lines with a screen and an SD card.
The symptom of a white screen when plugged in with a cable could also be pointing at a damaged board or a bad cable.
Finally…
Are you engraving on carpet? The chemistry of synthetic carpet is proprietary and rarely published, but you could safely assume it’s petroleum-based and likely flammable - unless it’s chemically treated with even more hazardous stuff.
You may want to consider a nice flat chunk of drywall or cement board as a safer surface for your engraver to rest on.