Ortur LM2 Pro not using full work area

My Ortur LM2 Pro will not use it’s full 15.748" x 15.748" (400mmx400mm) work area.
i updated the laser firmware to its lastest as of today 2022-07-18 in hopes it would solve the issue but it hasnt.
using lightburn as the software but no matter the software version this issue still exists.
for some reason if the image i want to burn is larger than 13.6 inches. if i send it to frame the design, the laser will move about half an inch, stops moving and throws an error.
ERROR BELOW:

<Idle|MPos:0.000,0.000,0.000|Bf:35,512|FS:0,0|Pn:S|CL:0,100|PS:2,1|ER:4092,4091|Ov:100,100,100|A:|H:1,7>

ok

[GC:G0 G54 G92 G17 G21 G90 G94 G49 G98 G50 M5 M9 T0 F0 S0.]

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]

ok

Ortur Laser Master 2 Pro Ready!

OLF 157.

[MSG: Warning: Flame Sensor Disabled by User OverRide]

Grbl 1.1f [‘$’ for help]

[MSG:‘$H’|‘$X’ to unlock]

[MSG:Caution: Unlocked]

ok

before the laser firmware update the error was error 9 and said something about the flame sensor but the update disabled it so im not sure what else the issue could be.

my work area is set to its default of 400mm by 400mm, i then switch it to inches in settings because for some reason thats easier for my brain to visualize. for reference it is 15.748 inches. if i load up any design smaller than 13.6 inches it will work without issue but that isnt taking advantage of the full work area and this needs to be fixed asap as i have a customer in need of a 14.5 inch burn and my machine wont allow it. if the image is even set to 13.61 inches it will not work. this is very frustrating. please help! ive searched around but maybe im not using the correct key words im sorry if this has been solved. if it has could you please lead me in the right direction thank you!

Can you run this in Console and return results?

$$
$#

$$:
$$

$0=5.0

$1=5

$2=0

$3=2

$4=0

$5=7

$6=1

$10=2047

$11=0.050

$12=0.002

$13=0

$14=2

$15=0

$16=1

$17=0

$18=0

$19=0

$20=1

$21=1

$22=1

$24=600.000

$25=3000.000

$26=100

$27=3.000

$28=0.100

$29=0.0

$30=1000.

$31=0.

$32=1

$33=1000.000

$34=0.000

$35=0.000

$36=100.000

$37=0

$39=1

$40=1

$41=0

$42=1

$43=1

$44=3

$45=3

$46=0

$56=1.000

$57=1800.000

$58=395.000

$59=6000.000

$60=0

$61=0

$62=0

$63=3

$64=1

$65=0

$259=0

$260=15

$261=0

$262=400

$263=30

$100=80.000

$101=80.000

$102=80.000

$110=10200.000

$111=10200.000

$112=1200.000

$120=2200.000

$121=1800.000

$122=2200.000

$130=400.000

$131=400.000

$132=50.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]

[G59.1:0.000,0.000,0.000]

[G59.2:0.000,0.000,0.000]

[G59.3:0.000,0.000,0.000]

[G28:0.000,0.000,0.000]

error:7

EEPROM read failed. Reset and restored to default values.

ok

Thank you!

Can you run $# again? If you continue to get this message then can you reflash the latest firmware and try again?

same error so i reinstalled the firmware typed the command $# and same error as before.

Waiting for connection…

Project loaded in 300 milliseconds

Waiting for connection…

ok

[ORIGIN: China]

[PRODUCER: ORTUR]

[AUTHOR: ORTUR]

[MODEL: Ortur Laser Master 2 Pro]

[OLF: 157]

[DATE:22:11:10 - Jan 3 2022]

[VER:1.1f(STM32F103CB).20210705:]

[OPT:VNMZHSL,35,512,3]

Target buffer size found

ok

Homing

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]

[G59.1:0.000,0.000,0.000]

[G59.2:0.000,0.000,0.000]

[G59.3:0.000,0.000,0.000]

[G28:0.000,0.000,0.000]

error:7

EEPROM read failed. Reset and restored to default values.

ok

Try issuing a GRBL reset.

$RST=*

Then try pulling offsets again

$#

no luck same error i believe.

$RST=*

[MSG:Restoring defaults]

ok

Ortur Laser Master 2 Pro Ready!

OLF 157.

[MSG: Warning: Flame Sensor Disabled by User OverRide]

Grbl 1.1f [‘$’ for help]

$#

[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]

[G59.1:0.000,0.000,0.000]

[G59.2:0.000,0.000,0.000]

[G59.3:0.000,0.000,0.000]

[G28:0.000,0.000,0.000]

error:7

EEPROM read failed. Reset and restored to default values.

ok

I’ve never seen that persist beyond a firmware update and reset cycle.

Try resetting just the offset values:

$RST=#

Then power cycle and then try $# again.

ran $RST=# command then restarted the machine then ran $# and nothing :frowning: but i have to start another print for a client that is smaller than 13.6 so i will complete that burn (approx 7 hrs) so can i reply again when im done so we can continue troubleshooting please and thank you. ive seen your responses to others and youre incredibly helpful i think you may be my only hope but for now i gotta get a customers order done. thank you for your help so far and anything else youll be able to recommend tomorrow. thanks for trying. will reply again when the machine is free to troubleshoot. i wishi could make the customers order smaller that 14.5 but i cant :frowning:

Circle back once you get a chance.

Can you confirm what Start From mode you’re working in?

I’m also wondering if the $# issue is a red herring. Try running ? a few times until you get something that shows “WCO:”. You may never get one but if you do, respond back with the content.

im sorry im not sure what you mean by “Start from mode” if you can let me know ill tell you after this burn is finished. im about to start my burn but i ran that command a few times till a wco showed up

?

<Idle|MPos:0.000,0.000,0.000|Bf:35,512|FS:0,0|Pn:S|CL:0,100|PS:2,1|ER:4091,4091|WCO:44.920,52.650,0.000|Ov:100,100,100>

ok

As in Absolute Coords vs User Origin vs Current Position.

This represents the work offset that’s causing you all your troubles. So the trick in this will be in working out how to get rid of it.

Are you certain that the firmware flashing is completing correctly?

@OrturTech Have you seen this before? Any insight about how to address?

1 Like

If indeed there is a offset in the firmware, the sequence to clear should ge as you stated
$RST=*
Press enter
Wait for MSG: restorign defaults
Tap reset button → power back on again

I would recomend however
a) Make usre absolute coordenates are set
b) create a new project
c) draw a small square on the middle of the grid

Shift → FRAME

Alarm 2 error?

1 Like

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