# Luban console broken or firmware bug?

**URL:** <https://forum.snapmaker.com/t/luban-console-broken-or-firmware-bug/6615>\
**Category:** Snapmaker 2.0 (3-in-1)\
**Created:** [May 10, 2020, 8:35pm UTC](https://forum.snapmaker.com/t/luban-console-broken-or-firmware-bug/6615 "2020-05-10T20:35:44Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![e-maddin](https://avatars.discourse-cdn.com/v4/letter/e/85e7bf/32.png) [@e-maddin](https://forum.snapmaker.com/u/e-maddin)\
**Post date:** [May 10, 2020, 8:35pm UTC](https://forum.snapmaker.com/t/luban-console-broken-or-firmware-bug/6615/1 "2020-05-10T20:35:44Z")

</div>

I went to Luban to check my Extruder ratio . Connected via serial port, first command executed is M501 and then the console is constantly repeating “others \< Enclosure online: OFF”. I guess this is a firmware bug? @parachvte?  
Thanks, Martin

 ![image](https://us1.discourse-cdn.com/flex022/uploads/snapmaker/original/2X/0/0c29e05bc021a6d1b01196bfeb410f25a1a9af2d.png)

---

<div class="post-metadata">

**Author:** ![Isaac11](https://avatars.discourse-cdn.com/v4/letter/i/9de0a6/32.png) [@Isaac11](https://forum.snapmaker.com/u/Isaac11)\
**Post date:** [May 10, 2020, 8:41pm UTC](https://forum.snapmaker.com/t/luban-console-broken-or-firmware-bug/6615/2 "2020-05-10T20:41:29Z")

</div>

Hi  
It will be fixed with a new version of Luban that what @Edwin said on Facebook

---

<div class="post-metadata">

**Author:** ![Tone](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.snapmaker.com/tone/32/1278_2.png) [@Tone](https://forum.snapmaker.com/u/Tone)\
**Post date:** [May 10, 2020, 9:24pm UTC](https://forum.snapmaker.com/t/luban-console-broken-or-firmware-bug/6615/3 "2020-05-10T21:24:30Z")

</div>

I would think that this is a problem with the firmware. If it’s not, then I’m worried that Luban is filtering out other communications the firmware is putting out.

I’m real disappointed that they haven’t fixed the echoing problem to Luban. That should be a high priority fix. I’ve already expressed that opinion on the Luban Github Issues page.  
I really wish they would open up the Github page on the firmware too. Technically it should be and I think the GNU GENERAL PUBLIC LICENSE which it is covered by spells it out. Do we really have to start exerting our rights under that license?? @whimsycwd, @parachvte.

---

<div class="post-metadata">

**Author:** ![JKC20](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.snapmaker.com/jkc20/32/5208_2.png) [@JKC20](https://forum.snapmaker.com/u/JKC20)\
**Post date:** [May 11, 2020, 7:08am UTC](https://forum.snapmaker.com/t/luban-console-broken-or-firmware-bug/6615/4 "2020-05-11T07:08:25Z")

</div>

I have forwarded this request to our team.

---

<div class="post-metadata">

**Author:** ![e-maddin](https://avatars.discourse-cdn.com/v4/letter/e/85e7bf/32.png) [@e-maddin](https://forum.snapmaker.com/u/e-maddin)\
**Post date:** [May 11, 2020, 7:11am UTC](https://forum.snapmaker.com/t/luban-console-broken-or-firmware-bug/6615/5 "2020-05-11T07:11:14Z")

</div>

Thanks! What about the long promised open source availability for the firmware that @Tone mentioned?

---

<div class="post-metadata">

**Author:** ![JKC20](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.snapmaker.com/jkc20/32/5208_2.png) [@JKC20](https://forum.snapmaker.com/u/JKC20)\
**Post date:** [May 11, 2020, 7:44am UTC](https://forum.snapmaker.com/t/luban-console-broken-or-firmware-bug/6615/6 "2020-05-11T07:44:03Z")

</div>

That too. Seems like quite some people request that we open source our firmware.

---

<div class="post-metadata">

**Author:** ![e-maddin](https://avatars.discourse-cdn.com/v4/letter/e/85e7bf/32.png) [@e-maddin](https://forum.snapmaker.com/u/e-maddin)\
**Post date:** [May 11, 2020, 8:03am UTC](https://forum.snapmaker.com/t/luban-console-broken-or-firmware-bug/6615/7 "2020-05-11T08:03:55Z")

</div>

That’s not “quite some people”… it was one of the promises in the Kickstarter campaign. Thanks! 🙂

---

<div class="post-metadata">

**Author:** ![Edwin](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.snapmaker.com/edwin/32/13481_2.png) [@Edwin](https://forum.snapmaker.com/u/Edwin)\
**Post date:** [May 11, 2020, 1:52pm UTC](https://forum.snapmaker.com/t/luban-console-broken-or-firmware-bug/6615/8 "2020-05-11T13:52:58Z")

</div>

Yes, the new version of Snapmaker Luban 3.5.x, which is compatible for the enclosure will fix this flooded info issue. But, I am sorry that the software will not be released today because the engineers want to make it stable and need to fix some bugs in it.  
Please be tuned.

---

<div class="post-metadata">

**Author:** ![Edwin](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.snapmaker.com/edwin/32/13481_2.png) [@Edwin](https://forum.snapmaker.com/u/Edwin)\
**Post date:** [May 11, 2020, 1:54pm UTC](https://forum.snapmaker.com/t/luban-console-broken-or-firmware-bug/6615/9 "2020-05-11T13:54:43Z")

</div>

1, We have noticed this issue. We redesigned the layout of the calibration page when we released 5x5 calibration. This subscript is indeed different from the previous version.  
2, The current leveling procedure of the machine is the same as the previous version, so it does not affect the calibration result.  
3, The subscript will be modified to match the execution position, and we may release at the end of May, please stay tuned.

---

<div class="post-metadata">

**Author:** ![e-maddin](https://avatars.discourse-cdn.com/v4/letter/e/85e7bf/32.png) [@e-maddin](https://forum.snapmaker.com/u/e-maddin)\
**Post date:** [May 11, 2020, 3:21pm UTC](https://forum.snapmaker.com/t/luban-console-broken-or-firmware-bug/6615/10 "2020-05-11T15:21:28Z")

</div>

Thanks! No need to rush, good to hear that it’s sorted out already.