Tried a new file and get the same results. There is something I forgot to mention. My laser will frame both files like it’s supposed to if that helps.
Hmm different job does it too. I was going to ask if it is always line 52 in the error, but I assume not. Was the new job a very simple one? if yes, then it won’t be a memory error or such.
Is everything on the same layer?
Over travel isn’t set way too high or something silly?
I assume the preview is all ok and doesn’t show anything strange?
If you use an online previewer any issues there?
It’s starting to sound like an electricsl noise issue, but difficult to prove. Have you tried a different USB cable?
I did try an old printer cable and actually switched to my other laptop. It starts and burns about 10mm and quits. I then have to shut down the laser and restart. One single layer and preview is fine. I just created a 60mm x 60mm square. I’ve never did anything with over travel. I think I will open one of my files and see what it does. It will have to wait until later, have a few errands to run. Thanks.
I think I’ll just delete my laser from LightBurn and reinstall again and see what happens. I may try installing the latest firmware update from Ortur if you think that is an option to try now.
Always worth a try Ernie. I have run out of suggestions at the moment, but maybe one of the other members might be able to throw some light on it. Let us know how you get on.
you will find lots and lots of disconnection errors and many are either tied to Windows doing something or USB electrical issues. I don’t do Windows so as for USB:
- make sure your computer and laser are on the same electrical outlet to eliminate ground loops
- try a better USB cable, preferred are ones with noise filter chokes on each end
- try using a powered USB hub in between computer and laser.
- IIRC there are different versions of GRBL you can pick from when setting up your machine. My Ortur LM1 I use plain “GRBL” option.
David, Thank you for trying I appreciate you taking your time to help.
Doug, I’m going to get a better USB cable today. I’m running laptops on battery unless they are charging. I do have a powered USB hub but read somewhere to not use one. (Hold my beer 
) so I’ll give that a try. Thanks for the suggestions.
Hi Ernie - while I don’t have an exact resolution to this issue, I wanted to share that I’ve encountered the same/similar issue. While I consider myself a newbie, I do have many hours of burning with LB and my Ortur LM 2 under my belt. I often burn multiple objects of the same type and design for my business so I’ve created a number of templates to maximize my use of the available space. The only time I encounter this issue is when I’m burning near the edge of the frame, certain designs will trigger the issue in those locations and others do not. So for my setup, I believe the issue to be mechanical in nature, something about the laser head being close to the allowable border causes it to jump (I’ve noticed this behavior of jumping and losing its location when framing objects that go right up to the border as well). I should mention that my templates are within the acceptable burn area and not touching the edge but are very close.
Wanted to share that in case it gives you another clue to help resolve or perhaps prevent, the issue from occurring.
Good luck,
Doc
Doc,
Thank you for the info. I have a template for doing bottle opener boards that is kind of close to the edges and bottom of the ‘allowable’ burn area. I can’t wait to fire that one up and give it a try. I had my laser apart for adding some riser blocks and feet as well as belt tensioners and a Z axis adjustment. I also built an enclosure. I wanted to check my focus and thought I would just make some example text and see how it was working. I tried cardboard first without any issues with the text nowhere near the edges. I switched material, refocused and the wheels came off. I have put in a support ticket with Ortur and will see what they come up with.
I did get another error and it was different. Something about movement. Maybe my new Z axis adjustment add-on isn’t as stable as it should be. I’ll add that in here incase someone can see if this may hold a clue.
Project loaded in 0 milliseconds
Starting stream
Stream completed in 0:00
Starting stream
Stream completed in 0:00
Starting stream
Layer C00
Detect movement, terminate laser engraving!
Acceleration fluctuation:290
Reset Grbl.
Ortur Laser Master 2 Ready!
OLF 137.
Grbl 1.1f [’$’ for help]
[MSG:’$H’|’$X’ to unlock]
Stream completed in 0:22
Thanks for your reply Doc,
Ernie
I may have fixed this issue on my computer. After double and triple checking all my wiring connections and I have not heard back from Ortur so I just went ahead and updated the firmware. My laser framed fine and burned three different files.
I realized I was still on version 0.9.21 because of the install thing with the Com Surrogate when trying to upgrade to 0.9.24. I upgraded it with the COM Surrogate message and just click on ignore when that came up.
So, it was either running an older version of LightBurn (I won’t do that again) or the firmware v137 wasn’t playing nice.
Thank you everyone who chipped in with ideas.
Glad you got it working Ernie.
Cheers
David
I have the exact same problem with mine did you fix yours
Michelle,
Yes I got mine fixed. One of the errors I got probably won’t apply to anyone else. I got a movement error which was from putting my laser on top of a chest freezer. It’s mounted to a piece of plywood but I didn’t realize the freezer top was crowned and it made the whole thing wobble enough to throw that error.
I updated my firmware and the problem went away. You might want to try that but you do have to use a windows computer. If you have the Laser Master 2 here’s the link to the Ortur site: Ortur Laser Master 2 – Ortur
Be sure to read through the PDF before you start. Hope this helps you get back up and running.
Ernie
There is a way to update the firmware with Linux or Mac, it just requires mktools utility because of the silly way the MS-VFAT filesystems stores 2 directory names. ping me and I’ll look for the step-by-step I have used on my Linux system.
Hey Doug,
I have windows systems and the one video I found said you had to use windows. Your reply will hopefully help those who do use Macs.
1 Like
Yes, they do state it only works with Windows but that’s just because they are lazy and don’t want to support other systems. I’ve repaired a number of bricked controller boards since I’ve done STM32 development and I’ve been able to flash the bootloader. I don’t have Windows but did find an old Windows98 CDROM and booted a virtual machine and that’s how I validated what was going on. The bootloader looks for the filename in the hidden 2nd VFAT directory structure and the mtools package(available for Linux and Mac) contains mcopy which copies the firmware file and puts the name in both VFAT directory entries.
Learn to decode these error messages. We’ll try and help you do that… The problem is around (or at) line 52. If you post code look around these line numbers to find the offending code and NUMBER the lines to assist those helping you… 
The error itself is “9 G-code lock G-code commands are locked out during alarm or jog state.” It had an unrecoverable error. I’ve seen this when it did not home properly or some other positioning error. In Candle and other gcode senders that allow the ‘check’ option, to run the code without actually doing anything. If soft/hard limits are used this can help detect them. This sometimes turns up instructions that take the machine out of bounds. The controller can’t know ahead of time that an instruction will do that.
Does this apply? Factory response.
Jack,
Thank you for the info. The decoding part is way above my paygrade. I had read somewhere during this search about the grounding but the poster never shared any real info. The link you posted was what I needed to get that done. Thank you.
Ernie
Great, I’m glad it helped. I got the link from one of the users questions about that machine. LIghtburns people posted it. Credit due… Sorry it took so long.
Take care
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.