Alarm 2 on or near line 4, G-code motion target exceeds machine travel

I turned on my machine today to engrave something and when I tried to Frame it, it gives me the Alarm 2 on or near line 4, G-code motion target exceeds machine travel error. I have tried everything I can find on it, and nothing is working. Please help.

Absolute Coords

Starting stream
ALARM:2
G-code motion target exceeds machine travel. Machine position safely retained. Alarm may be unlocked. (Right-click the ‘Devices’ button to reset the connection)
On or near line 4:
Stream completed in 0:00
[MSG:Reset to continue]

I assume this was a perfectly working system earlier based on your wording? What coordinate system were you using?

Can you run these commands in Console and return output here please?

$I
$$
$#
?

Yes it worked perfectly fine about a week ago. Turned it on this morning and when I tried to run the Frame command, it gave me the Alarm 2 on or near line 4 error.

$I
[AUTHOR: ORTUR]
[MODEL: Ortur Laser Master 2]
[OLF: 142]
[DATE:18:41:30 - Dec 15 2021]
[VER:1.1h.210324:]
[OPT:VNZHI,99,512]
Target buffer size found

$$
$0=2.000
$1=25
$2=0
$3=0
$4=0
$5=0
$6=0
$10=3
$11=0.050
$12=0.002
$13=0
$20=1
$21=1
$22=1
$23=7
$24=600.000
$25=3000.000
$26=100
$27=3.000
$30=1000
$31=0
$32=1
$33=500.000
$50=0
$51=0.000
$52=0.000
$100=80.000
$101=80.000
$102=80.000
$110=9000.000
$111=9000.000
$112=1200.000
$120=2200.000
$121=1800.000
$122=2500.000
$130=400.000
$131=430.000
$132=1.000
ok

$#
[G54:0.000,0.000,0.000]
[G55:0.000,0.000,0.000]
[G56:0.000,0.000,0.000]
[G57:0.000,0.000,0.000]
[G58:0.000,0.000,0.000]
[G59:0.000,0.000,0.000]
[G28:0.000,0.000,0.000]
[G30:0.000,0.000,0.000]
[G92:0.000,0.000,0.000]
[TLO:0.000]
[PRB:0.000,0.000,0.000:0]
ok

?
<Idle|MPos:0.000,0.000,0.000|Bf:99,511|FS:0,0|Pn:P|WCO:0.000,0.000,0.000>
ok

Okay. Everything looks like it’s been cleared out.

Can you try it and see if it behaves as you expect?

Where was the laser head when you ran the last command?

Okay, so here is the weird thing. I just tried to do a word and it worked perfectly. I erased the word and trying to draw a circle, it gives me the same error code, but this time it is on or near line 5. :man_shrugging:


So when I try and frame this, it frames really narrow width, and almost the length of the machine???

Looks like you’re on the latest firmware? When did you apply the firmware? Any relationship to when the issues started?

Did you reset defaults after the firmware update?

If not, run this in console:
$RST=*

The issue started when I turned it on this morning, I updated the firmware during my google searches, and I did a reset on the defaults. The only thing that changed was I last used it during the “Trial” and I paid for it this morning, activated, and that is when it started…I am totally perplexed…

Can you go through this process:

  1. Restart laser and reconnect
  2. In console get status information:
    ?
  1. Move laser head to lower right and get status again ?
  2. Move to upper left and get status again
  3. Move to upper right and get status again

Capture output and report here.

Want to make sure you have access to all corners and position is reported as expected.

Can you attach the known bad file here? Want to review to see if there’s anything obvious in the file causing the issue.

Initial - Lower Left
?
<Idle|MPos:0.000,0.000,0.000|Bf:99,512|FS:0,0|Pn:P|WCO:0.000,0.000,0.000>
ok

Lower Right
?
<Idle|MPos:398.000,4.000,0.000|Bf:99,512|FS:0,0|Pn:P|WCO:0.000,0.000,0.000>
ok

Upper Left
?
<Idle|MPos:1.000,430.000,0.000|Bf:99,511|FS:0,0|Pn:P|WCO:0.000,0.000,0.000>
ok

Upper Right
?
<Idle|MPos:398.000,429.000,0.000|Bf:99,512|FS:0,0|Pn:P|WCO:0.000,0.000,0.000>
ok

If you are referring to the image, it doesn’t matter, any image does this…

No. I mean the specific .lbrn file.

Also, can you attach a screenshot of LightBurn with Move window open?

Not sure what the .lbrn file is… here is the screenshot the laser head sitting at the bottom right.

Save the file that you’re working from. That will be in the format of .lbrn or .lbrn2. Upload that file here.

Also, can you capture the full output of the failure message in console when you run this exact file?