Editing file causes laser to skip areas

I have had this happen a couple of times now. I have a file that runs perfect. I edit the file, and the new file runs, but the laser beam turns off at random places throughout the file. If I catch it, I can hit pause, and then resume and the laser turns back on. If I don’t catch it, the machine continues on through the complete file, leaving areas uncut.

I have tried all the mechanical issues, connectors, etc.
I have tried completely shutting down machine and computer.

I can close that file, open a different file, and it will run complete, no problems.
I re-open the edited file and the problem returns.
I have edited several files without this issue, yet every once in a while this happens.

What in the world am I doing wrong??

In one of the files where this happens can you push “Save gcode” in Laser window and then save with a .txt extension? Upload file here for review.

flowerbabe.txt (259.8 KB)

File uploaded, thank you.

I don’t see anything in the gcode that would indicate a problem in the instructions being sent.

This is likely something electrical or a failure in one of the components. Potential candidates include power supply, controller, cable from controller to laser module, or the laser module itself.

Based on the description of this being intermittent I’m wondering if you have a partial wire break in the cable and it’s losing connection intermittently at certain areas of travel. If you have a meter you could check PWM and Power voltage at the cable near the laser module to see if the problem is north of that point. If you see no issue there then it’s likely a laser module failure. If the issue is north of that point then you’d have to isolate where the failure is introduced.

I appreciate your assistance. To clarify, this is only intermittent in files that have been edited. Original files do not ever give me this problem.
The cables test good and testing with two different laser modules give the exact same problem.

In what way are they edited? Can you confirm that the file for which you send the gcode was a potential problem file?

There was nothing in the gcode requesting the laser to turn off. If it’s shutting off it’s likely happening elsewhere. If you’re having this issue with two laser modules than it must be north of that.

When you tested the cables did you try causing a fault by flexing in different ways? If you’re relatively confident in the cable then I’d suggest checking voltages from the controller.

Yes sir, the file sent is the file I edited and is consistently shutting off the laser module in certain spots. By edited, I mean I moved or added lines to the graphic, edited nodes by deleting, adding or moving them, to create a different path. The original file did not have the word “babe”.
Ist edit, add that to the stem
2nd edit, add the vertical lines in the “B”, “a” and “e”
3rd edit, made the vertical lines thicker.
After the 3rd edit, the symptoms appeared. I will run a test and upload the issue

What is the source of the “original” in that case? What would distinguish an original file from an edited one?

Unless I’ve missed something entirely I can say with almost certainty that there’s nothing in the gcode file that would account for something like what you’re describing.

Do you have an example of a burn where this occurred? I may be misunderstanding what you’re experiencing.

Also, can you upload the .lbrn file for review?


As you can see, the laser module just shuts off as if those areas in the word “Babe” are blank.

The original file was an svg that was purchased. The first run of that file worked without problem. The first and second edit worked fine.

Here is the .lbrn file…
flowerbabe.lbrn2 (139.7 KB)

I’m noticing one thing. You have Constant Power Mode enabled. What firmware revision are you on? I recall there was a firmware bug where Constant Power Mode on some Ortur models was causing dropouts during deceleration.

The way you’ve constructed some of the edits looks like they’d have some odd acceleration/deceleration points. I suspect what’s happening is that due to those added areas with extreme acceleration/deceleration the firmware bug is presenting.

Try disabling Constant Power Mode and trying again.

And again, can you confirm your exact laser model and firmware revision?

Good lawd, I turned Constant Power Mode off and it worked…

The machine is an Ortur Laser Master 2S2 with a Laser Tree LT-80w module.
I am not well versed in editing, and do not know how to add accel/decel points…

Here is the information on startup:

[ORIGIN: China]

[PRODUCER: ORTUR]

[AUTHOR: ORTUR]

[MODEL: Ortur Laser Master 2 S2]

[OLF: 185]

[OLH: OLM_ESP_PRO_V1.2]

[OLM: GENERAL]

[DATE:20:46:41 - Nov 2 2021]

[VER:1.1f(ESP32).20210403:]

[OPT:VNMZHSL,35,4096,3]

I looked at Ortur firmware, and it appears I need to upgrade to version 1.90. Will do so immediately!
I also will attempt to become more educated on editing and accel/dcecel points.

Thank you so very much for the quick and insightful assistance!

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.