# Luban // Snapmaker not powering off Laser between "Objects"

**URL:** <https://forum.snapmaker.com/t/luban-snapmaker-not-powering-off-laser-between-objects/33510>\
**Category:** Snapmaker Luban\
**Created:** [November 6, 2023, 7:45pm UTC](https://forum.snapmaker.com/t/luban-snapmaker-not-powering-off-laser-between-objects/33510 "2023-11-06T19:45:51Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![tpk](https://avatars.discourse-cdn.com/v4/letter/t/d2c977/32.png) [@tpk](https://forum.snapmaker.com/u/tpk)\
**Post date:** [November 6, 2023, 7:45pm UTC](https://forum.snapmaker.com/t/luban-snapmaker-not-powering-off-laser-between-objects/33510/1 "2023-11-06T19:45:51Z")

</div>

Hello ,

Maybe someone has an idea why Luban “engraves” the laser work path.

Before loading into workspace everything looks good.

In the workspace you can then see the paths of the laser.  
My problem is that the laser doesn’t switch off between each cut

 ![snap3](https://us1.discourse-cdn.com/flex022/uploads/snapmaker/original/3X/8/2/8245d1dd29c79d4c4f7d7a08bfd0be8550b66fc9.png)

Luban Version ist 4.9.1

Someone an idea?

Regards,  
Martin

---

<div class="post-metadata">

**Author:** ![tpk](https://avatars.discourse-cdn.com/v4/letter/t/d2c977/32.png) [@tpk](https://forum.snapmaker.com/u/tpk)\
**Post date:** [November 6, 2023, 7:49pm UTC](https://forum.snapmaker.com/t/luban-snapmaker-not-powering-off-laser-between-objects/33510/2 "2023-11-06T19:49:42Z")

</div>

![snap2](https://us1.discourse-cdn.com/flex022/uploads/snapmaker/original/3X/d/f/df0093601f0d1ca7b136296ea458a1c729390d35.png)

---

<div class="post-metadata">

**Author:** ![tpk](https://avatars.discourse-cdn.com/v4/letter/t/d2c977/32.png) [@tpk](https://forum.snapmaker.com/u/tpk)\
**Post date:** [November 6, 2023, 7:50pm UTC](https://forum.snapmaker.com/t/luban-snapmaker-not-powering-off-laser-between-objects/33510/3 "2023-11-06T19:50:17Z")

</div>

![grafik](https://us1.discourse-cdn.com/flex022/uploads/snapmaker/original/3X/c/2/c2eeda5d1a4c081537aebb59a3a7200194d577a9.png)

---

<div class="post-metadata">

**Author:** ![Skreelink](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.snapmaker.com/skreelink/32/16398_2.png) [@Skreelink](https://forum.snapmaker.com/u/Skreelink)\
**Post date:** [November 6, 2023, 10:25pm UTC](https://forum.snapmaker.com/t/luban-snapmaker-not-powering-off-laser-between-objects/33510/4 "2023-11-06T22:25:49Z")

</div>

Upgrade the firmware of your snapmaker to the latest version. Luban 4.9.0 changed the way the laser works, and requires at minimum firmware version 1.17.17.

---

<div class="post-metadata">

**Author:** ![Hauke](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.snapmaker.com/hauke/32/5704_2.png) [@Hauke](https://forum.snapmaker.com/u/Hauke)\
**Post date:** [November 7, 2023, 10:31am UTC](https://forum.snapmaker.com/t/luban-snapmaker-not-powering-off-laser-between-objects/33510/5 "2023-11-07T10:31:29Z")

</div>

I wish people would use the forum search more… This topic/solution is one of those that I’ve seen several times, also the DX replacement kit discussion is repeating itself all the time…

---

<div class="post-metadata">

**Author:** ![tpk](https://avatars.discourse-cdn.com/v4/letter/t/d2c977/32.png) [@tpk](https://forum.snapmaker.com/u/tpk)\
**Post date:** [November 7, 2023, 5:36pm UTC](https://forum.snapmaker.com/t/luban-snapmaker-not-powering-off-laser-between-objects/33510/6 "2023-11-07T17:36:29Z")

</div>

thank you for the hint. before my post i searched with google and can´t find anything, next time i search here 😉

---

<div class="post-metadata">

**Author:** ![nweolu](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.snapmaker.com/nweolu/32/23079_2.png) [@nweolu](https://forum.snapmaker.com/u/nweolu)\
**Post date:** [November 8, 2023, 10:26am UTC](https://forum.snapmaker.com/t/luban-snapmaker-not-powering-off-laser-between-objects/33510/7 "2023-11-08T10:26:29Z")

</div>

Facebook group has posts about it every other day. Ever since the firmware release. Very few people use search unfortunately.  
I hope dev team learned the lesson…