# Ortur LM2 Pro S2 freezes in Busy state in LightBurn (works fine in LaserGRBL)

**URL:** <https://forum.lightburnsoftware.com/t/ortur-lm2-pro-s2-freezes-in-busy-state-in-lightburn-works-fine-in-lasergrbl/178002>\
**Category:** Ortur Lasers\
**Tags:** grbl, homing, ortur, LightBurn\
**Created:** [August 20, 2025, 8:52pm UTC](https://forum.lightburnsoftware.com/t/ortur-lm2-pro-s2-freezes-in-busy-state-in-lightburn-works-fine-in-lasergrbl/178002 "2025-08-20T20:52:23Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![segorada](https://forum.lightburnsoftware.com/letter_avatar_proxy/v4/letter/s/a9a28c/32.png) [@segorada](https://forum.lightburnsoftware.com/u/segorada)\
**Post date:** [August 20, 2025, 8:52pm UTC](https://forum.lightburnsoftware.com/t/ortur-lm2-pro-s2-freezes-in-busy-state-in-lightburn-works-fine-in-lasergrbl/178002/1 "2025-08-20T20:52:23Z")

</div>

Hi everyone,

I recently had to replace the **motherboard of my Ortur Laser Master 2 Pro S2** because the original one was damaged due to a USB overload. The new board is recognized and connects fine to both LightBurn and LaserGRBL.

### So far:

- The machine boots up correctly, LightBurn shows it as connected.
- GRBL commands work: I can send jog commands like `G91` + `G0 X10/Y10` and it moves normally.
- Homing `$H` also works after enabling `$22=1`.
- The GRBL settings look correct (steps, speeds, travel limits, etc.).

### **The problem**

- In **LightBurn** , the machine often freezes when I try to jog using the arrow keys. It stays in **Busy** state and doesn’t recover.
- If I try to frame a job → Busy.
- If I send a job → Busy.
- If I jog with the arrows → Busy.
- Basically, almost any action in LightBurn leads to Busy.
- Sometimes the console shows **`ALARM:8`** (_“Homing fail. Pull off failed to clear limit switch”_).
- If I run **`$RST=$`** to reset defaults, then after that **`$X`** (unlock) makes the machine freeze permanently in Busy. It looks like `$RST=$` loads defaults that don’t match Ortur’s parameters.

### **Important notes**

- This only happens in **LightBurn**.
- In **LaserGRBL** , everything works fine — I can move with arrows, jog, frame, even reset with `$RST=*`, power cycle, reconnect, and it all works smoothly.
- In LightBurn, I can sometimes frame once right after unlocking, but as soon as I try to run a job, it freezes in Busy.

### **Current GRBL settings** (before reset):

```auto
$100=80.000
$101=80.000
$102=2124.000
$110=10200.000
$111=10200.000
$112=600.000
$120=2200.000
$121=800.000
$122=200.000
$130=400.000
$131=400.000
$132=100.000
...

```

### **$$**

$0=5.0  
$1=100  
$2=0  
$3=6  
$4=7  
$5=7  
$6=1  
$10=2047  
$11=0.050  
$12=0.002  
$13=0  
$14=6  
$15=0  
$16=1  
$17=4  
$18=0  
$19=0  
$20=1  
$21=1  
$22=1  
$23=7  
$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=0  
$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  
$100=80.000  
$101=80.000  
$102=2124.000  
$110=10200.000  
$111=10200.000  
$112=600.000  
$120=2200.000  
$121=1800.000  
$122=200.000  
$130=400.000  
$131=400.000  
$132=100.000  
$259=0  
$260=70  
$261=0  
$262=400  
$263=0  
$264=0  
$265=50  
$266=100  
$267=0  
$268=0  
$269=0  
$270=5120

### **Questions**

1. With a replacement motherboard, is it normal that `$RST=*` breaks the machine?
2. Should I avoid `$RST=*` completely and instead just reload Ortur’s values manually?
3. Is there a config file or “factory defaults” specifically for the **OLM2 Pro S2** that I should load?
4. Why would everything work in **LaserGRBL** , but not in **LightBurn** (v1.7.08)?

I really want to use **LightBurn** , not LaserGRBL.

Thanks in advance — the machine itself works fine, but LightBurn constantly puts it into Busy state and I can’t jog, frame, or send jobs reliably.

---

<div class="post-metadata">

**Author:** ![segorada](https://forum.lightburnsoftware.com/letter_avatar_proxy/v4/letter/s/a9a28c/32.png) [@segorada](https://forum.lightburnsoftware.com/u/segorada)\
**Post date:** [August 20, 2025, 8:53pm UTC](https://forum.lightburnsoftware.com/t/ortur-lm2-pro-s2-freezes-in-busy-state-in-lightburn-works-fine-in-lasergrbl/178002/2 "2025-08-20T20:53:07Z")

</div>

This is how the lightburn freezes.

 ![image](https://forum.lightburnsoftware.com/uploads/default/original/3X/4/e/4e55880bc51eb97b644071688a4de6c6763bb307.png)

In order to unfreeze it, i need to change te COM, and then select again COM3.

 ![image](https://forum.lightburnsoftware.com/uploads/default/original/3X/8/6/869b4091aff02648691437a8c95500de87ee24e4.png)

---

<div class="post-metadata">

**Author:** ![MikeyH](https://forum.lightburnsoftware.com/letter_avatar_proxy/v4/letter/m/43a26b/32.png) [@MikeyH](https://forum.lightburnsoftware.com/u/MikeyH)\
**Post date:** [August 21, 2025, 12:12am UTC](https://forum.lightburnsoftware.com/t/ortur-lm2-pro-s2-freezes-in-busy-state-in-lightburn-works-fine-in-lasergrbl/178002/3 "2025-08-21T00:12:33Z")

</div>

> [@segorada](#):
>
> Should I avoid `$RST=*` completely and instead just reload Ortur’s values manually?

Definitely the best choice if the board is not an Ortur replacement board. If it is, not all manufacturers burn their parameter settings to permanent memory, leaving default settings of the board maker.

> [@segorada](#):
>
> LightBurn constantly puts it into Busy state and I can’t jog, frame, or send jobs reliably.

This appears to be a communications issue, but…

1. Boot up = ok
2. Return to zero = ok
3. $X (unlock) = ok

None of this indicates a problem.

But this might…

> [@segorada](#):
>
> ```auto
> $120=2200.000
> $121=800.000
> 
> ```

That Xaxis acceleration value seems to be quite aggressive. The X & Y accel values are usually the same value. Try changing **$120=800** and see if that helps.

If not, it could be a corrupt copy of Lightburn. Download a fresh copy of your current version and install it.

---

<div class="post-metadata">

**Author:** ![segorada](https://forum.lightburnsoftware.com/letter_avatar_proxy/v4/letter/s/a9a28c/32.png) [@segorada](https://forum.lightburnsoftware.com/u/segorada)\
**Post date:** [August 21, 2025, 4:18pm UTC](https://forum.lightburnsoftware.com/t/ortur-lm2-pro-s2-freezes-in-busy-state-in-lightburn-works-fine-in-lasergrbl/178002/4 "2025-08-21T16:18:06Z")

</div>

Hi Mickey,

Thanks!

I changed the values you suggested, it will work fine until I typed “$x”

 ![image](https://forum.lightburnsoftware.com/uploads/default/original/3X/e/3/e39a35d88a29dc0ff147a20e6d08551d66a2b60e.png)

Here I reset the machine, reconnect trough usb, unlock and move with arrows, busy.

 ![image](https://forum.lightburnsoftware.com/uploads/default/original/3X/d/8/d8f390410d213fd3231280dde98325e49bd90ad9.png)

If I use ALT + L (Set laser position), the laser moves perfectly.  
It just “busy” when using the “Move” window.

 ![image](https://forum.lightburnsoftware.com/uploads/default/original/3X/b/7/b7193ca8a1a1b648f5ab76a81a19f6485ce99df8.png)

Heres I’m using this version insstead of 1.7.08 that’s the latests with my licence.

> **[Index of /LightBurn/Release/LightBurn-v1.6.03/](https://release.lightburnsoftware.com/LightBurn/Release/LightBurn-v1.6.03/)**

---

<div class="post-metadata">

**Author:** ![MikeyH](https://forum.lightburnsoftware.com/letter_avatar_proxy/v4/letter/m/43a26b/32.png) [@MikeyH](https://forum.lightburnsoftware.com/u/MikeyH)\
**Post date:** [August 21, 2025, 4:34pm UTC](https://forum.lightburnsoftware.com/t/ortur-lm2-pro-s2-freezes-in-busy-state-in-lightburn-works-fine-in-lasergrbl/178002/5 "2025-08-21T16:34:56Z")

</div>

Why did you do the **$RST=$**? Please recheck the $120 parameter.

---

<div class="post-metadata">

**Author:** ![segorada](https://forum.lightburnsoftware.com/letter_avatar_proxy/v4/letter/s/a9a28c/32.png) [@segorada](https://forum.lightburnsoftware.com/u/segorada)\
**Post date:** [August 21, 2025, 6:33pm UTC](https://forum.lightburnsoftware.com/t/ortur-lm2-pro-s2-freezes-in-busy-state-in-lightburn-works-fine-in-lasergrbl/178002/6 "2025-08-21T18:33:00Z")

</div>

My mistake, now setting $120 and $121 to equally 800, then setting a 19x19mm square, then pressing “Frame”, “Busy” again:

 ![image](https://forum.lightburnsoftware.com/uploads/default/original/3X/e/4/e41b043a54b81056b22c2c54d7d13815b2ce798e.png)

I recently change the dafault USB B - USB A to a new one thinking it could be, but works fine in LaserGRBL, Lightburn is where can complete any action.

 ![image](https://forum.lightburnsoftware.com/uploads/default/original/3X/4/d/4d92c4f240e7c1d646fef1f71c743952a5d228fa.png)  
 ![image](https://forum.lightburnsoftware.com/uploads/default/original/3X/6/6/6667f13e31e60996e5be862df5f3c006d4b13489.png)  
 ![image](https://forum.lightburnsoftware.com/uploads/default/original/3X/f/0/f0e738de03dea6acb7078c164b29d9e2b4c0449d.jpeg)

---

<div class="post-metadata">

**Author:** ![segorada](https://forum.lightburnsoftware.com/letter_avatar_proxy/v4/letter/s/a9a28c/32.png) [@segorada](https://forum.lightburnsoftware.com/u/segorada)\
**Post date:** [September 2, 2025, 3:48pm UTC](https://forum.lightburnsoftware.com/t/ortur-lm2-pro-s2-freezes-in-busy-state-in-lightburn-works-fine-in-lasergrbl/178002/7 "2025-09-02T15:48:26Z")

</div>

**Well,**

The program correctly recognizes the laser position, but it still gets stuck whenever I click on any of the buttons in the red square (jog controls / frame, etc.).

- The console shows `<Idle|MPos:...>` but LightBurn status bar goes into **Busy** and stays there.
- This only happens in **LightBurn** — in **LaserGRBL** everything works fine (jog, frame, homing, jobs).
- GRBL reports correctly, homing works, and I can send manual `G0` moves from the console without any issues.

 ![image](https://forum.lightburnsoftware.com/uploads/default/original/3X/4/9/49ae012b3260f2c6a9fdd30aece67869be9cb718.png)

Waiting for connection…  
ok  
[ORIGIN: China]  
[PRODUCER: ORTUR]  
[AUTHOR: ORTUR]  
[MODEL: Ortur Laser Master 2 Pro S2]  
[OLF: 191]  
[OLH: OLM\_ESP\_PRO\_V1.2]  
[SN: 98B198962B60F4E47D23199626A821B5]  
[OLM:GENERAL]  
[DATE:15:05:32 - Mar 13 2023]  
[VER:1.1f(ESP32).20210403:]  
[OPT:VNMZHSL,35,7680,3]  
Target buffer size found  
ok  
Homing  
ok  
Starting stream

> Here the console freezes and shows **“BUSY”**  
> [MSG:Pgm End]  
> Stream completed in 0:00  
> \<Idle|MPos:0.000,0.000,0.000|Bf:35,7679|FS:0,0|Pn:PXY|CL:0,100|PS:2,1|ER:0,0|WCO:0.000,0000,0.000|VA:24620,0|Ov:100,100,100|A:S|H:1,7\>  
> Here the console freezes and shows **“BUSY”**

$x  
Waiting for connection…  
Waiting for connection…  
ok  
[ORIGIN: China]  
[PRODUCER: ORTUR]  
[AUTHOR: ORTUR]  
[MODEL: Ortur Laser Master 2 Pro S2]  
[OLF: 191]  
[OLH: OLM\_ESP\_PRO\_V1.2]  
[SN: 98B198962B60F4E47D23199626A821B5]  
[OLM:GENERAL]  
[DATE:15:05:32 - Mar 13 2023]  
[VER:1.1f(ESP32).20210403:]  
[OPT:VNMZHSL,35,7680,3]  
Target buffer size found  
ok  
Homing  
ok  
$x  
ok  
ok  
Starting stream

> Here the console freezes and shows **“BUSY”**  
> [MSG:Pgm End]  
> Stream completed in 0:03  
> \<Idle|MPos:20.000,0.000,0.000|Bf:35,7680|FS:0,0|Pn:P|CL:0,100|PS:2,1|ER:0,0|WCO:0.000,0.000,0.000|VA:24609,0|A:S|H:1,7\>  
> Here the console freezes and shows **“BUSY”**

$x  
Waiting for connection…  
ok  
[ORIGIN: China]  
[PRODUCER: ORTUR]  
[AUTHOR: ORTUR]  
[MODEL: Ortur Laser Master 2 Pro S2]  
[OLF: 191]  
[OLH: OLM\_ESP\_PRO\_V1.2]  
[SN: 98B198962B60F4E47D23199626A821B5]  
[OLM:GENERAL]  
[DATE:15:05:32 - Mar 13 2023]  
[VER:1.1f(ESP32).20210403:]  
[OPT:VNMZHSL,35,7680,3]  
Target buffer size found  
ok  
Homing  
ok

> Here the console freezes and shows **“BUSY”**  
> \<Idle|MPos:0.000,0.000,0.000|Bf:35,7680|FS:0,0|Pn:P|CL:0,100|PS:2,1|ER:0,0|VA:24661,0|A:S|H:1,7\>  
> Here the console freezes and shows **“BUSY”**

Waiting for connection…  
ok  
[ORIGIN: China]  
[PRODUCER: ORTUR]  
[AUTHOR: ORTUR]  
[MODEL: Ortur Laser Master 2 Pro S2]  
[OLF: 191]  
[OLH: OLM\_ESP\_PRO\_V1.2]  
[SN: 98B198962B60F4E47D23199626A821B5]  
[OLM:GENERAL]  
[DATE:15:05:32 - Mar 13 2023]  
[VER:1.1f(ESP32).20210403:]  
[OPT:VNMZHSL,35,7680,3]  
Target buffer size found  
ok  
Homing  
ok  
Starting stream

> Here the console freezes and shows **“BUSY”**  
> [MSG:Pgm End]  
> Stream completed in 0:13  
> \<Idle|MPos:55.000,92.000,0.000|Bf:35,7680|FS:0,0|Pn:P|CL:0,100|PS:2,1|ER:0,0|WCO:0.000,0.000,0.000|VA:24620,0|A:S|H:1,7\>  
> Here the console freezes and shows **“BUSY”**

Waiting for connection…  
Waiting for connection…  
ok  
[ORIGIN: China]  
[PRODUCER: ORTUR]  
[AUTHOR: ORTUR]  
[MODEL: Ortur Laser Master 2 Pro S2]  
[OLF: 191]  
[OLH: OLM\_ESP\_PRO\_V1.2]  
[SN: 98B198962B60F4E47D23199626A821B5]  
[OLM:GENERAL]  
[DATE:15:05:32 - Mar 13 2023]  
[VER:1.1f(ESP32).20210403:]  
[OPT:VNMZHSL,35,7680,3]  
Target buffer size found  
ok  
Homing  
ok  
\<Idle|MPos:0.000,0.000,0.000|Bf:35,7680|FS:0,0|Pn:P|CL:0,100|PS:2,1|ER:0,0|VA:24647,0|A:S|H:1,7\>

---

<div class="post-metadata">

**Author:** ![MikeyH](https://forum.lightburnsoftware.com/letter_avatar_proxy/v4/letter/m/43a26b/32.png) [@MikeyH](https://forum.lightburnsoftware.com/u/MikeyH)\
**Post date:** [September 3, 2025, 10:06am UTC](https://forum.lightburnsoftware.com/t/ortur-lm2-pro-s2-freezes-in-busy-state-in-lightburn-works-fine-in-lasergrbl/178002/8 "2025-09-03T10:06:46Z")

</div>

Did it work for 10 days, or did you just not use it for that long?

It appears You are connecting, and short basic commands to the laser controller are working. But when you try to stream something, it does not cooperate. Try unchecking the **Enable DTR signal** in the Device Setings window.

---

<div class="post-metadata">

**Author:** ![segorada](https://forum.lightburnsoftware.com/letter_avatar_proxy/v4/letter/s/a9a28c/32.png) [@segorada](https://forum.lightburnsoftware.com/u/segorada)\
**Post date:** [September 4, 2025, 8:38pm UTC](https://forum.lightburnsoftware.com/t/ortur-lm2-pro-s2-freezes-in-busy-state-in-lightburn-works-fine-in-lasergrbl/178002/9 "2025-09-04T20:38:28Z")

</div>

I didn’t use the laser for about 10 days.

In **LaserGRBL it works fine** , but in **LightBurn it constantly shows “Busy”**.

 ![image](https://forum.lightburnsoftware.com/uploads/default/original/3X/1/b/1bf005d9af71c3e09cf974b050cfb152d567d972.png)

I updated the firmware with the **ESP .bin version** and restored the defaults.

When I connect the laser, unlock (`$X`) and press one arrow, it moves correctly.  
But on the **second click on any arrow, the machine freezes and shows “Busy” immediately**.

**Console output when it gets stuck:**

> \<Idle|MPos:0.000,0.000,0.000|Bf:35,7680|FS:0,0|Pn:P|CL:0,100|PS:2,1|ER:0,0|VA:24703,0|A:S|H:1,7\>

---

<div class="post-metadata">

**Author:** ![MikeyH](https://forum.lightburnsoftware.com/letter_avatar_proxy/v4/letter/m/43a26b/32.png) [@MikeyH](https://forum.lightburnsoftware.com/u/MikeyH)\
**Post date:** [September 5, 2025, 5:06pm UTC](https://forum.lightburnsoftware.com/t/ortur-lm2-pro-s2-freezes-in-busy-state-in-lightburn-works-fine-in-lasergrbl/178002/10 "2025-09-05T17:06:15Z")

</div>

In the Console window, enter **$#** and post what it lists here.

---

<div class="post-metadata">

**Author:** ![segorada](https://forum.lightburnsoftware.com/letter_avatar_proxy/v4/letter/s/a9a28c/32.png) [@segorada](https://forum.lightburnsoftware.com/u/segorada)\
**Post date:** [September 8, 2025, 2:58pm UTC](https://forum.lightburnsoftware.com/t/ortur-lm2-pro-s2-freezes-in-busy-state-in-lightburn-works-fine-in-lasergrbl/178002/11 "2025-09-08T14:58:04Z")

</div>

> [@MikeyH](#):
>
> $#

Hi Mike, here’s what it shows after $#  
$#  
[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]  
[G30:0.000,0.000,0.000]  
[G59.6:0.000,0.000,0.000]  
[G92:0.000,0.000,0.000]  
[HOME:0.000,0.000,0.000:7]  
[TLO:0.000]  
[PRB:0.000,0.000,0.000:0]  
ok

---

<div class="post-metadata">

**Author:** ![MikeyH](https://forum.lightburnsoftware.com/letter_avatar_proxy/v4/letter/m/43a26b/32.png) [@MikeyH](https://forum.lightburnsoftware.com/u/MikeyH)\
**Post date:** [September 8, 2025, 3:12pm UTC](https://forum.lightburnsoftware.com/t/ortur-lm2-pro-s2-freezes-in-busy-state-in-lightburn-works-fine-in-lasergrbl/178002/12 "2025-09-08T15:12:04Z")

</div>

Ok, that eliminates the possibility of a G54 offset, which can impact positioning.

Before we can change GRBL settings, we need to figure out what is wrong.

1. Turn off **Auto-Home on Startup** in the Device Settings window.
2. Set **$22=0** in the Console window.
3. Turn off the laser and put it in the middle of the machine.
4. Turn on the laser power.
5. Enter **$X** in the Console window.
6. Did you get **Busy** or **Ok**?

At this point, we are trying to determine if the PC is actually talking to the controller, and it is answering.

Update: Also set **$20** and **$21** to zero for now.

---

<div class="post-metadata">

**Author:** ![segorada](https://forum.lightburnsoftware.com/letter_avatar_proxy/v4/letter/s/a9a28c/32.png) [@segorada](https://forum.lightburnsoftware.com/u/segorada)\
**Post date:** [September 8, 2025, 3:27pm UTC](https://forum.lightburnsoftware.com/t/ortur-lm2-pro-s2-freezes-in-busy-state-in-lightburn-works-fine-in-lasergrbl/178002/13 "2025-09-08T15:27:58Z")

</div>

[ORIGIN: China]  
[PRODUCER: ORTUR]  
[AUTHOR: ORTUR]  
[MODEL: Ortur Laser Master 2 Pro S2]  
[OLF: 191]  
[OLH: OLM\_ESP\_PRO\_V1.2]  
[SN: 98B198962B60F4E47D23199626A821B5]  
[OLM:GENERAL]  
[DATE:15:05:32 - Mar 13 2023]  
[VER:1.1f(ESP32).20210403:]  
[OPT:VNMZHSL,35,7680,3]  
Target buffer size found  
ok  
$x  
ok  
$22=0  
ok  
[ORIGIN: China]  
[PRODUCER: ORTUR]  
[AUTHOR: ORTUR]  
[MODEL: Ortur Laser Master 2 Pro S2]  
[OLF: 191]  
[OLH: OLM\_ESP\_PRO\_V1.2]  
[SN: 98B198962B60F4E47D23199626A821B5]  
[OLM:GENERAL]  
[DATE:15:05:32 - Mar 13 2023]  
[VER:1.1f(ESP32).20210403:]  
[OPT:VNMZHSL,35,7680,3]  
Target buffer size found  
ok  
$x  
[MSG:Caution: Unlocked]  
ok  
$20=0  
ok  
$21=0  
ok

> I clicked the right arrow, moved ok.

ok

> I clicked the up arrow, busy

ok

**\<Idle|MPos:30.994,0.000,0.000|Bf:35,7679|FS:0,0|Pn:P|CL:0,100|PS:2,1|ER:0,0|VA:24564,0|Ov:100,100,100|A:S\>**

> Device selection to unfreeze it

Waiting for connection…  
ok  
[ORIGIN: China]  
[PRODUCER: ORTUR]  
[AUTHOR: ORTUR]  
[MODEL: Ortur Laser Master 2 Pro S2]  
[OLF: 191]  
[OLH: OLM\_ESP\_PRO\_V1.2]  
[SN: 98B198962B60F4E47D23199626A821B5]  
[OLM:GENERAL]  
[DATE:15:05:32 - Mar 13 2023]  
[VER:1.1f(ESP32).20210403:]  
[OPT:VNMZHSL,35,7680,3]  
Target buffer size found  
ok  
ok

> Clicked right arrow, freezed

ok  
\<Idle|MPos:30.994,0.000,0.000|Bf:35,7679|FS:0,0|Pn:P|CL:0,100|PS:2,1|ER:0,0\>

---

<div class="post-metadata">

**Author:** ![MikeyH](https://forum.lightburnsoftware.com/letter_avatar_proxy/v4/letter/m/43a26b/32.png) [@MikeyH](https://forum.lightburnsoftware.com/u/MikeyH)\
**Post date:** [September 8, 2025, 3:36pm UTC](https://forum.lightburnsoftware.com/t/ortur-lm2-pro-s2-freezes-in-busy-state-in-lightburn-works-fine-in-lasergrbl/178002/14 "2025-09-08T15:36:49Z")

</div>

Cycle the power and enter $X.  
Now try the **Down** arrow.  
Cycle the power and try the **Up** arrow.  
Cycle the power and try the **Left** arrow.

We are trying to determine the result of each directional arrow without any previous command.

---

<div class="post-metadata">

**Author:** ![segorada](https://forum.lightburnsoftware.com/letter_avatar_proxy/v4/letter/s/a9a28c/32.png) [@segorada](https://forum.lightburnsoftware.com/u/segorada)\
**Post date:** [September 8, 2025, 3:44pm UTC](https://forum.lightburnsoftware.com/t/ortur-lm2-pro-s2-freezes-in-busy-state-in-lightburn-works-fine-in-lasergrbl/178002/15 "2025-09-08T15:44:50Z")

</div>

I did turn off, turn on and $X.  
Moved up arrow, right arrow and down arrow. Moved ok, but when tried left arrow, frozen out.

turn off, turn on and $x  
Only move up - Ok (but only keeping the arrow click, if let go the first click, and click again “busy”)

turn off, turn on and $x  
Only move down - busy (freezes)

turn off, turn on and $x  
Only move right - Ok (but only keeping the arrow click, if let go the first click, and click again “busy”)

turn off, turn on and $x  
Only move left - busy (freezes)

---

<div class="post-metadata">

**Author:** ![MikeyH](https://forum.lightburnsoftware.com/letter_avatar_proxy/v4/letter/m/43a26b/32.png) [@MikeyH](https://forum.lightburnsoftware.com/u/MikeyH)\
**Post date:** [September 8, 2025, 3:58pm UTC](https://forum.lightburnsoftware.com/t/ortur-lm2-pro-s2-freezes-in-busy-state-in-lightburn-works-fine-in-lasergrbl/178002/16 "2025-09-08T15:58:10Z")

</div>

So it will not move Left or Down.  
But it will Home in that direction.

Set via Console window:  
$20=0  
$21=0  
$22=1  
Turn off **Auto-Home on Startup** in the Device Settings window.  
Cycle the power to laser.  
Turn on **CNC Machine** in the Device Settings window. If this makes it work, it is not the solution, but will tell us what is.

---

<div class="post-metadata">

**Author:** ![segorada](https://forum.lightburnsoftware.com/letter_avatar_proxy/v4/letter/s/a9a28c/32.png) [@segorada](https://forum.lightburnsoftware.com/u/segorada)\
**Post date:** [September 8, 2025, 4:03pm UTC](https://forum.lightburnsoftware.com/t/ortur-lm2-pro-s2-freezes-in-busy-state-in-lightburn-works-fine-in-lasergrbl/178002/17 "2025-09-08T16:03:35Z")

</div>

Did it.

After CNC it’s working, at least with the arrows.  
BUT  
The axis are inverted now.

---

<div class="post-metadata">

**Author:** ![MikeyH](https://forum.lightburnsoftware.com/letter_avatar_proxy/v4/letter/m/43a26b/32.png) [@MikeyH](https://forum.lightburnsoftware.com/u/MikeyH)\
**Post date:** [September 8, 2025, 4:12pm UTC](https://forum.lightburnsoftware.com/t/ortur-lm2-pro-s2-freezes-in-busy-state-in-lightburn-works-fine-in-lasergrbl/178002/18 "2025-09-08T16:12:35Z")

</div>

ok!

Turn off the CNC switch and **Home** the machine.  
Make sure the **Origin** radio button is correct in the Device Settings window. If it is, then report what is at the top of the Move window.

 ![Positions in Move Window](https://forum.lightburnsoftware.com/uploads/default/original/3X/5/c/5c539a3842a1ceba465c818d939a4505662572ac.jpeg)

---

<div class="post-metadata">

**Author:** ![segorada](https://forum.lightburnsoftware.com/letter_avatar_proxy/v4/letter/s/a9a28c/32.png) [@segorada](https://forum.lightburnsoftware.com/u/segorada)\
**Post date:** [September 8, 2025, 4:21pm UTC](https://forum.lightburnsoftware.com/t/ortur-lm2-pro-s2-freezes-in-busy-state-in-lightburn-works-fine-in-lasergrbl/178002/19 "2025-09-08T16:21:37Z")

</div>

![image](https://forum.lightburnsoftware.com/uploads/default/original/3X/4/a/4a924349868fc9ce7e79433060ca9fb00bb161b3.png)

 ![image](https://forum.lightburnsoftware.com/uploads/default/original/3X/e/1/e1009c41c869a5b209b30d765d61a3755fe107d7.png)

Also, while testing the arrow keys, I noticed something strange with the working area:

- If I move the laser with **ALT+L** (set laser position), it works.
- But if I set a position further than **150 mm** (on X or Y), the laser moves very close to the limits, as if the working area was only 200×200 mm.
- The actual machine size should be **400×400 mm** , but the motion is **distorted** — it does not match the real physical travel.

---

<div class="post-metadata">

**Author:** ![MikeyH](https://forum.lightburnsoftware.com/letter_avatar_proxy/v4/letter/m/43a26b/32.png) [@MikeyH](https://forum.lightburnsoftware.com/u/MikeyH)\
**Post date:** [September 8, 2025, 4:28pm UTC](https://forum.lightburnsoftware.com/t/ortur-lm2-pro-s2-freezes-in-busy-state-in-lightburn-works-fine-in-lasergrbl/178002/20 "2025-09-08T16:28:43Z")

</div>

> [@segorada](#):
>
> If I move the laser with **ALT+L** (set laser position), it works.

Not sure what you are doing here. Is this setting the Origin? Are you usung **Absolute Coords** in the Laser window?

> [@segorada](#):
>
> motion is **distorted** — it does not match the real physical travel.

You may have to do a calibration. So we have an accurate starting set of GRBL parameters, do a **$$** in the Console window and paste here.

[Next page](https://forum.lightburnsoftware.com/t/ortur-lm2-pro-s2-freezes-in-busy-state-in-lightburn-works-fine-in-lasergrbl/178002.md?page=2)
