Luban
Luban copied to clipboard
Snapmaker
Bug: Wifi disconnects on every Snapmaker power off
My Snapmaker started to lose the wifi network on every power off after the new update. I'm running Luban last version and Snapmaker firmware last version too.
Every time I open my Snapmaker I need to go to config and type the pasword of the wifi. Then, the machine is connected to wifi forever until I power off the machine and power it on again.
~While I have this same issue, I don't necessarily think it's a Luban problem (so this probably isn't the right place for it)~. It's also reported in the forums here: https://forum.snapmaker.com/t/wifi-not-connecting-at-startup/16628. It started happening after the Feb V1.11.4 update
Edit
At first I thought this wasn't the right place for it, but it was likely a regression introduced by https://github.com/Snapmaker/Luban/pull/714.
Just adding my experience here as well, I've also been having this issue this since the Feb update.
Just adding my experience here as well, I've also been having this issue this since the Feb update.
Same here
At first I thought this wasn't the right place for it, but it was likely a regression introduced by #714.
If it happens on Snapmaker reboots, it's not an issue of Luban (though Luban has its own problem on user experience).
We are unable to reproduce the issue in our office, but we have some guesses on what the problem is. Now we are adding some test code to our firmware, and then build a test firmware (I will upload the firmware later). Could you help us to use the test firmware to see if the issue still occurs? @paauserrat
btw, we start to use Github project to manage issues posted here, you can check on project to track their status.
Updated 2021.04.23: Test firmware below, unzip and update it via USB disk. ~Snapmaker2_V255.0.0_20210423.bin.zip~
Updated 2021.04.29: Second try for test firmware, fix side cases Snapmaker2_V255.0.0_20210429.bin.zip
Notice: After upgrading to the new firmware, you need to turn off the machine and then turn it on again.
Hi! I installed the test firware and it seems to be fixed. At first, I needed to turn wifi off, turn it on again and it automatically reconnected. I turned Snapmaker 2.0 off and on and it automatically reconected to my wifi! Congrats :)
Do I need to re-install the official last firmware release or I can be running the Test you provided without any problem?
Do I need to re-install the official last firmware release or I can be running the Test you provided without any problem?
You can use the test firmware without problems, it's based on v1.12.1 (under testing) to be released. We will collect more feedback from users on the test firmware, once the fix is confirmed, it will be released as an patch as well.
**Updated 2021.04.29: Second try for test firmware, fix side cases Snapmaker2_V255.0.0_20210429.bin.zip
This update didn't solve the issue.
This update did not solve me issue.
On Wed, May 12, 2021, 03:33 slipperysam1984 @.***> wrote:
This update didn't solve my issue either.
Sam
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Snapmaker/Luban/issues/788#issuecomment-839621583, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIEJRBBILUTOMLXKQWLX33DTNJDOBANCNFSM4YAVCBNA .
Hi, we are still working on this issue. We got some report that the test firmware had solved the problem after reboot the machine, but we still collecting feedback to make sure our changes can fix this issue.
Please check your machine turn off and turn it on after test firmware upgraded. If the issue still occurs, please let us know.
@shuwn @slipperysam1984 @sublime24 Hi! Did the issue still persist after machine reboot? If you can export the log from the machine, we can check it and try to find out what's the status with the test firmware.
You can export log file from the touchscreen by these steps:
- Make your U-disk is connected in touchscreen
- Click Settings > Export log
- Wait for touchscreen export log to the U-disk successfully
@shuwn @ slipperysam1984 @ sublime24 嗨！重新啟動計算機後問題仍然存在嗎？如果您可以從計算機中導出日誌，我們可以對其進行檢查並嘗試找出測試固件的狀態。
您可以通過以下步驟從觸摸屏導出日誌文件：
- 使您的U盤通過觸摸屏連接
- 單擊設置>導出日誌
- 等待觸摸屏導出日誌到U盤成功
FYI
I'm having the same problem. A350, no wifi connection after machine reboot. Latest version Snapmaker2_V1.12.0.
I'm also having the same problem. It seems fixed at first but it isnt't
I encountered this issue but why this silly bug doesn't be fixed immediately?
same problem here, persistent since >6 months... this is ridiculous!
https://github.com/Snapmaker/Luban/issues/788#issuecomment-824811503. Maybe you can try this firmware.
after installing the latest firmware, going back to factory settings via developer mode, installing the firmware her the issue seems solved. I really hopes it stays that way.
after installing the latest firmware, going back to factory settings via developer mode, installing the firmware her the issue seems solved. I really hopes it stays that way.
For what it's worth (I'm late to this) I have never experienced any problems with my WiFi on my Snapmaker. It connects automatically without fail every single time.
When I got the machine I immediately updated to 1.9, it stayed there until I upgraded to 1.12.1, so an update in between 1.9 and 1.12.1 must've screwed it up and it doesn't get reset with subsequent updates so the machine remembers that bug and keeps it until being factory reset.
Have you updated? That seemed to fix the issue.
On Tue, Dec 28, 2021, 2:44 PM qriusGate @.***> wrote:
I just got my snapmaker and am having this issue as well
— Reply to this email directly, view it on GitHub https://github.com/Snapmaker/Luban/issues/788#issuecomment-1002274870, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIEJRBGWQHYJH57XUJMBCUTUTIOTHANCNFSM4YAVCBNA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID: @.***>