# 2.1.02 is broken again and support Failed

**URL:** <https://forum.lightburnsoftware.com/t/2-1-02-is-broken-again-and-support-failed/190539>\
**Category:** LightBurn Hardware Compatibility\
**Created:** [June 11, 2026, 8:44am UTC](https://forum.lightburnsoftware.com/t/2-1-02-is-broken-again-and-support-failed/190539 "2026-06-11T08:44:12Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![jdlynch99](https://forum.lightburnsoftware.com/letter_avatar_proxy/v4/letter/j/dbc845/32.png) [@jdlynch99](https://forum.lightburnsoftware.com/u/jdlynch99)\
**Post date:** [June 11, 2026, 8:44am UTC](https://forum.lightburnsoftware.com/t/2-1-02-is-broken-again-and-support-failed/190539/1 "2026-06-11T08:44:12Z")

</div>

when 2.0 came out the return to home after loading material broke and stopped working here is the sequence i am talking about; (I run my job/ then I power off/ then I move laser out of way to load material/ power on/ laser returns to home yo start job) the return to home stopped working in 2.0 and i was told its not gonna get fixed. now with 2.1 it got fixed and return to home is working again. it works on 2.1.00-RC11 pre-release, it works on 2.1.00 release, it works on 2.1.01/ now comes 2.1.02 and its broken again I open a support ticket, and try to tell the tech to compare the code in the versions to see what changed the tech went off on some other tangent trying to make setting change that had no help or results, I was able to install each version and prove my theory the code change but no the tech decided to just abandon the ticket and follow the same as before and not do anything to try to resolve. I have 3 versions where the return to home works, then latest version its broken again its a software issue. not hardware, Light Burn Do Better with your support… Teach them how to use logic when trouble shooting, and to not just abandon your customer when it gets tough…

---

<div class="post-metadata">

**Author:** ![JediJeremy](https://forum.lightburnsoftware.com/user_avatar/forum.lightburnsoftware.com/jedijeremy/32/77848_2.png) [@JediJeremy](https://forum.lightburnsoftware.com/u/JediJeremy)\
**Post date:** [June 11, 2026, 2:03pm UTC](https://forum.lightburnsoftware.com/t/2-1-02-is-broken-again-and-support-failed/190539/2 "2026-06-11T14:03:46Z")

</div>

Support escalated your issue internally and at least two devs (one being me) have been trying to figure out what’s going on. We have multiple theories but as always we’re working with limited information and a moving target. We have to gather evidence and do internal checks.

They have definitely not abandoned you, but sometimes we do ask the same thing multiple times as the issue gets passed around and different people have a go, looking for the answer.

---

<div class="post-metadata">

**Author:** ![JediJeremy](https://forum.lightburnsoftware.com/user_avatar/forum.lightburnsoftware.com/jedijeremy/32/77848_2.png) [@JediJeremy](https://forum.lightburnsoftware.com/u/JediJeremy)\
**Post date:** [June 11, 2026, 2:21pm UTC](https://forum.lightburnsoftware.com/t/2-1-02-is-broken-again-and-support-failed/190539/3 "2026-06-11T14:21:32Z")

</div>

If it’s what we think then you actually benefited from a “bug” that other users demanded we roll back. (All to do with how not-quite-GRBL controllers respond vs the real GRBL spec, and have been diverging over the years. long story.)

Your controller requires a specific “flavor” of GCode, and we tried to make that the new flavor in the RC’s (because it’s mathematically correct!) but people wanted the classic flavor back again. That’s why it worked and then didn’t again.

Fortunately we have been preparing new flavors for exactly this reason, to cope with more options.

---

<div class="post-metadata">

**Author:** ![Crysteven1974](https://forum.lightburnsoftware.com/letter_avatar_proxy/v4/letter/c/e47c2d/32.png) [@Crysteven1974](https://forum.lightburnsoftware.com/u/Crysteven1974)\
**Post date:** [June 11, 2026, 3:11pm UTC](https://forum.lightburnsoftware.com/t/2-1-02-is-broken-again-and-support-failed/190539/4 "2026-06-11T15:11:28Z")

</div>

I’m having the same issue with my ortur pro master 2 and it comes up error code 'out of bounds" I put the image directly in the middle and it says the same. It won’t even frame I want to go back to the earlier version I purchased in March. 150$ is a lot to spend on a program that doesn’t work anymore

---

<div class="post-metadata">

**Author:** ![goeland86](https://forum.lightburnsoftware.com/user_avatar/forum.lightburnsoftware.com/goeland86/32/69290_2.png) [@goeland86](https://forum.lightburnsoftware.com/u/goeland86)\
**Post date:** [June 11, 2026, 3:22pm UTC](https://forum.lightburnsoftware.com/t/2-1-02-is-broken-again-and-support-failed/190539/5 "2026-06-11T15:22:00Z")

</div>

I’m the other dev looking at this, and I don’t know how you can have the same issue - not going back to home and “out of bounds” is a different error.

To help us help you, please reach out to the support email, with support data, a full log of the console when you try to start a job, and a configuration bundle. Until we get such information it’s very difficult to understand how things are broken for you.

---

<div class="post-metadata">

**Author:** ![LightBurn](https://forum.lightburnsoftware.com/user_avatar/forum.lightburnsoftware.com/lightburn/32/75577_2.png) [@LightBurn](https://forum.lightburnsoftware.com/u/LightBurn)\
**Post date:** [June 11, 2026, 4:45pm UTC](https://forum.lightburnsoftware.com/t/2-1-02-is-broken-again-and-support-failed/190539/6 "2026-06-11T16:45:03Z")

</div>

@Crysteven1974 - Can you confirm that your ‘Start From’ mode is set to ‘Absolute Coords’? If it isn’t, then it doesn’t matter where you put the art in the editing area of LightBurn.

The ‘User Origin’ and ‘Current Position’ modes work in specific ways and the grid in LightBurn isn’t used for those.

---

<div class="post-metadata">

**Author:** ![jdlynch99](https://forum.lightburnsoftware.com/letter_avatar_proxy/v4/letter/j/dbc845/32.png) [@jdlynch99](https://forum.lightburnsoftware.com/u/jdlynch99)\
**Post date:** [June 11, 2026, 5:07pm UTC](https://forum.lightburnsoftware.com/t/2-1-02-is-broken-again-and-support-failed/190539/7 "2026-06-11T17:07:11Z")

</div>

Yes I am in Absolute co0rds

---

<div class="post-metadata">

**Author:** ![LightBurn](https://forum.lightburnsoftware.com/user_avatar/forum.lightburnsoftware.com/lightburn/32/75577_2.png) [@LightBurn](https://forum.lightburnsoftware.com/u/LightBurn)\
**Post date:** [June 11, 2026, 6:05pm UTC](https://forum.lightburnsoftware.com/t/2-1-02-is-broken-again-and-support-failed/190539/8 "2026-06-11T18:05:22Z")

</div>

> [@jdlynch99](#):
>
> Teach them how to use logic when trouble shooting, and to not just abandon your customer when it gets tough

We do. We also teach them civility.

They’re not developers, and they can’t fix the code, so there are times where they simply hit the limits of their knowledge and have to escalate it to the dev team, which they’ve done. That means you now have two very well paid software engineers looking at your problem, but it also means that a solution is likely not going to happen overnight.

From what I understand, the reason your particular arrangement of hardware & firmware isn’t automatically homing right now is because of something we fixed to prevent issues that broke many other devices. The devs are trying to see if there’s a way we can make the “in between” behavior that you had in the RC version available behind a switch or something so putting it back doesn’t break the other devices that now work because of this fix.

If you can try to answer the questions they ask, clearly and without filling the responses with anger, this process will go a lot faster.

---

<div class="post-metadata">

**Author:** ![Aaron.F](https://forum.lightburnsoftware.com/user_avatar/forum.lightburnsoftware.com/aaron.f/32/87478_2.png) [@Aaron.F](https://forum.lightburnsoftware.com/u/Aaron.F)\
**Post date:** [June 11, 2026, 7:27pm UTC](https://forum.lightburnsoftware.com/t/2-1-02-is-broken-again-and-support-failed/190539/9 "2026-06-11T19:27:37Z")

</div>

@jdlynch99 I’m yet another LightBurn support agent, and I don’t have **all** the context of your previous tickets with my colleagues.

This suggestion should help your cause, if I’m understanding your workflow correctly:  
Enable this in the Device Settings:

 ![image](https://forum.lightburnsoftware.com/uploads/default/original/3X/c/e/ce1bfb3cfe7318796391e01b2f289d40e6152220.png)  
It will move the laser to the [Finish Position](https://docs.lightburnsoftware.com/latest/Reference/CoordinatesOrigin/#finish-position) after the job completes. Which means you don’t have to turn off the laser to remove the material, and don’t need to re-home.

* * *

You probably know this already:  
Homing the machine is needed whenever the laser gets moved by hand or if the controller is rebooted.  
The exact sequence is controlled by the firmware of your laser. It moves the axes and touches off on the limit switches, so the controller knows where the laserhead is.

If you have “Auto-Home on Startup” enabled in the Device Settings, LightBurn sends your machine the `$H` command when it connects to the laser, which initiates the homing sequence on the firmware.  
Unless, the not-quite-GRBL topic mentioned by @JediJeremy above actually sends it a `$H/n` (Newline symbol), which your controller doesn’t like!

**Therefore, my question:**  
Does the “Home” button in the Move panel work when you are connected to the machine?

---

<div class="post-metadata">

**Author:** ![LightBurn](https://forum.lightburnsoftware.com/user_avatar/forum.lightburnsoftware.com/lightburn/32/75577_2.png) [@LightBurn](https://forum.lightburnsoftware.com/u/LightBurn)\
**Post date:** [June 11, 2026, 9:16pm UTC](https://forum.lightburnsoftware.com/t/2-1-02-is-broken-again-and-support-failed/190539/11 "2026-06-11T21:16:07Z")

</div>

Split this topic on June 11, 2026, 9:16pm UTC

2 posts were split to a new topic: [LightBurn 2.1 Ortur Rotary / start point issue, plus camera trouble](https://forum.lightburnsoftware.com/t/lightburn-2-1-ortur-rotary-start-point-issue-plus-camera-trouble/190552)

---

<div class="post-metadata">

**Author:** ![LightBurn](https://forum.lightburnsoftware.com/user_avatar/forum.lightburnsoftware.com/lightburn/32/75577_2.png) [@LightBurn](https://forum.lightburnsoftware.com/u/LightBurn)\
**Post date:** [June 11, 2026, 9:19pm UTC](https://forum.lightburnsoftware.com/t/2-1-02-is-broken-again-and-support-failed/190539/12 "2026-06-11T21:19:08Z")

</div>

Split this topic on June 11, 2026, 9:19pm UTC

A post was merged into an existing topic: [LightBurn 2.1 Ortur Rotary / start point issue, plus camera trouble](https://forum.lightburnsoftware.com/t/lightburn-2-1-ortur-rotary-start-point-issue-plus-camera-trouble/190552/3)

---

<div class="post-metadata">

**Author:** ![system](https://forum.lightburnsoftware.com/user_avatar/forum.lightburnsoftware.com/system/32/64335_2.png) [@system](https://forum.lightburnsoftware.com/u/system)\
**Post date:** [July 11, 2026, 9:19pm UTC](https://forum.lightburnsoftware.com/t/2-1-02-is-broken-again-and-support-failed/190539/13 "2026-07-11T21:19:25Z")

</div>

Closed on July 11, 2026, 9:19pm UTC

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