OLM3 Getting Error -> ALARM:2 G-code motion target exceeds machine travel

[rickestrada]

My Ortur Laser Master 3 was working, and then the Lightburn license ran out. So I renewed my license, and my laser was giving me an error.

ALARM:2

*G-code motion targets exceed machine travel. The machine position is safely retained. The alarm may be unlocked. (Right-click the ‘Devices’ button to reset the connection.)

On or near line 70:

1. I went ahead and updated LightBurn Software from 1.4.01 to 1.4.04, but that did not help.

2. I updated the latest firmware for my laser to OLM3_Firmware_Release_210, but that did not help.

My settings appeared to RESET after updating the LightBurn license, requiring me to reenter my WiFi settings.

Any help is appreciated, as this is frusturating. Here is my settings.

[berainlb (PY)]

Enable “Out of bounds warning” in Edit->Device Settings.

That may warn you before you get into this situation.

You should never get this alarm if you follow these conditions:

1. You home the machine before each session
2. You use jogging controls exclusively. Do not move the laser head by hand after homing.
3. You don’t ignore any warnings

Additionally, using Absolute Coords as your Start From mode makes this much simpler.

[rickestrada]

So when hit START it starts to cut out the shape then fails at the same place each time with the error in the console. Well I have had my OLM3 for 1 year and never had the issue. Then the LICENSE expired on my LightBurn then it seemed the issue started after I renewed my license

[berainlb (PY)]

Can you run these commands in Console and return the full output?

$H
$I
$$
$#
?

[JohnJohn (John Johnson)]

@rickestrada

fails at the same place each time with the error in the console.

This is Key.

Click File, click Save GCode and save the file somewhere convenient.
Happy to open it here and look at line 70 to see what’s happening.

I see that you have chosen “Cut Selected Graphics” in the Laser window.

Is it possible that you have selected other Graphics outside the work area?

The Dots and controls we’re seeing around that part only apply to that specific active piece.

Another option to see what’s going on is the Preview window. It will show you what you’re about to send.

Click Window, then click Preview (2nd line down from the top)

If you don’t see the pink or red traverse lines, activate the Show Traversal Moves switch at the bottom left of the preview window. Sometimes Traversal lines go out of bounds.

If you have a wheel-mouse you can zoom in and out and drag the preview around.

[misken (Melvin)]

Did you check the firmware settings if the maximum travel distance ($131) is also set to 850 as in your LightBurn configuration? I guess it has been reset.

Lately, I got a huge number of reports that the LightBurn update also changed firmware values. It should not, so I guess it might be a bug. I got these reports constantly over the last two years, but during the last few months, the number has grown exponentially. I don’t know what’s going on there.

[rickestrada]

Here is what I get when I type $H in console

$H

<Home|MPos:-600.000,-600.000,0.000|Bf:63,131071|FS:0,0|CL:0,0|PS:2,0>

<Home|MPos:0.000,0.000,0.000|Bf:63,131071|FS:1131,0|CL:0,0|PS:2,0|VA:24483,53|A:SFM>

<Home|MPos:-39.950,-39.950,0.000|Bf:63,131071|FS:1131,0|CL:0,0|PS:2,0>

<Home|MPos:-79.970,-79.970,0.000|Bf:63,131071|FS:1131,0|CL:0,0|PS:2,0>

<Home|MPos:-119.980,-119.980,0.000|Bf:63,131071|FS:1131,0|CL:0,0|PS:2,0>

<Home|MPos:0.000,0.000,0.000|Bf:63,131071|FS:848,0|CL:0,0|PS:2,0|WCO:0.000,0.000,0.000|VA:24480,34>

ok

[rickestrada]

MISKEN here are all my settings below. As you can see $131=400

I will try to change that now and see if it makes a difference.

ok

$$

$0=5.0

$1=100

$2=0

$3=1

$4=7

$5=0

$7=0

$10=2047

$11=0.050

$12=0.002

$13=0

$14=0

$15=3

$16=1

$17=4

$18=0

$20=1

$21=0

$22=1

$23=7

$24=600.0

$25=800.0

$26=100

$27=1.000

$28=0.100

$29=0.0

$30=1000.000

$31=0.000

$32=1

$33=2000.0

$34=0.0

$35=0.0

$36=100.0

$37=0

$39=1

$40=1

$41=0

$42=1

$43=1

$44=3

$45=0

$46=0

$56=1.0

$57=1800.0

$58=395.0

$59=6000.0

$60=0

$61=1

$62=0

$63=3

$64=0

$70=31

$73=3

$74=BlockChain

$75=*********

$76=OLM3_AP_6AE2

$77=12345678

$100=100.000

$101=100.000

$102=100.000

$110=20040.000

$111=20040.000

$112=600.000

$120=2000.000

$121=1800.000

$122=200.000

$130=400.000

$131=400.000

$132=100.000

$140=600

$141=1000

$142=800

$150=16

$151=16

$152=16

$160=0.000

$161=0.000

$162=0.000

$180=20040.000

$181=14028.000

$182=600.000

$200=65.0

$201=50.0

$202=60.0

$210=100

$211=100

$212=100

$220=50.0

$221=60.0

$222=60.0

$270=115200

$271=115200

$272=115200

$300=OLM3_STA_6AE2

$301=1

$302=192.168.5.1

$303=192.168.5.1

$304=255.255.255.0

$305=23

$306=80

$307=81

$308=21

$310=OLM3_AP_6AE2

$312=192.168.5.1

$313=192.168.5.1

$314=255.255.255.0

$330=admin

$331=user

$332=255

$339=3

$341=0

$342=30.0

$343=30.0

$344=180.0

$345=200.0

$384=0

$392=5.0

$393=3.0

$600=0

$601=5

$602=0

$603=5.0

$604=6.0

$605=1

$606=1

$607=0

$608=1

$609=10.000

$610=0

$611=0

$612=1

$613=6960

$614=0

$615=api.ortur.cn

$616=0

$617=0

$622=111

ok

[berainlb (PY)]

@rickestrada

As you can see $131=400

This is very likely the issue. What’s strange is that you should have had the same issue even before the upgrade.

[rickestrada]

Like I mentioned everything was working fine for the past year. Then my LICENSE on my LIGHTBURN expired… I RENEWED the LICENSE but something was got RESET because when I paid for the UPDATE LICENSE $30 I had to re-enter my WIFE SSID and PASSWORD as that not working as they got erased. There was still the ERROR so I UPDATED the FIRMWARE and the LightBurn SOFTWARE to 1.4.04. And still had the issue. Once I changed the Variable that you mentioned from $131=400 to $131=850 everything seems to be working as it should. Thanks again for your help as not quite clear why everything got RESET.

THANKS AGAIN!

[misken (Melvin)]

@rickestrada

Thanks again for your help as not quite clear why everything got RESET.

If you upgraded the firmware, all settings usually got reset to their default values. In that case, LightBurn was not the issue, but the firmware upgrade.