Disconnected laser mid-job

I am trying to see why my MOPA 100W fiber laser suddenly disconnects during a job in lightburn. I have tried running material tests (varying frequency and speed), as well as simple text runs. It was working last week. I don’t think there has been any firmware, software, or driver updates. It is sporadic and sometimes finishes half of the job, then I see “disconnected” in the device area, then “ready”. I have tried reboots, file recreation, and preset files in the material testing dropdown…all to no avail. what am I missing?

Generally speaking, these are usually from low cost (cheap) usb cables…

It can be the OS of your computer turning off the usb port, but I doubt it.


I’d try some cables first. I found my usb connector on the machine to be rather flaky.

Get down there and wiggle them…

:smiley_cat:

I am able to run simple jpeg style etches. Whenever I try the “material test” runs it stops mid way. Is it perhaps a corrupted file? UBS cord doesn’t seem to make a difference either way.

this is the debug log if it makes any sense:
12:07:22.781 D: “LightBurn 1.7.08” “Tue Aug 5 2025”
12:07:30.005 D: removed 26 linear segs
12:07:30.006 D: removed 2 linear segs
12:07:30.006 D: removed 4 linear segs
12:07:30.007 D: removed 4 linear segs
12:07:30.008 D: removed 4 linear segs
12:07:30.008 D: removed 5 linear segs
12:07:30.009 D: removed 1 linear segs
12:07:30.009 D: removed 1 linear segs
12:07:30.009 D: removed 1 linear segs
12:07:30.009 D: removed 2 linear segs
12:07:30.010 D: removed 3 linear segs
12:07:30.011 D: removed 2 linear segs
12:07:30.012 D: 1 floaters
12:07:30.013 D: PathTree build: 1
12:07:32.422 D: EnableZ: false Relative: false
12:07:32.422 D: removed 31 linear segs
12:07:32.422 D: removed 2 linear segs
12:07:32.422 D: removed 4 linear segs
12:07:32.423 D: removed 4 linear segs
12:07:32.423 D: removed 4 linear segs
12:07:32.423 D: removed 5 linear segs
12:07:32.423 D: removed 1 linear segs
12:07:32.423 D: removed 1 linear segs
12:07:32.423 D: removed 1 linear segs
12:07:32.423 D: removed 2 linear segs
12:07:32.423 D: removed 3 linear segs
12:07:32.423 D: removed 2 linear segs
12:07:32.427 D: Optimize by score: 0 ms
12:07:32.427 D: CutBuilder took: 4 ms
12:07:32.427 D: ------------------------------
12:07:32.449 D: Protocol::GenerateCuts time: 22
12:08:08.953 D: Clipboard data present:
12:08:08.953 D: (“application/x-qt-windows-mime;value="PNG"”, “application/x-qt-image”, “application/x-qt-windows-mime;value="CanUploadToCloudClipboard"”, “application/x-qt-windows-mime;value="CanIncludeInClipboardHistory"”)

As of now. Update to 2.0 has taken care of the issue.

1 Like