Blank white screen in Luban after connection

Hello everyone,

while my new A350 works perfectly fine so far and I am pretty happy with the first print results via USB, I am still not able to connect via WiFi. on my PC I am connected to the router via LAN cable, so I guess that’s the reason why Luban cannot find the Snapmaker 2.0 on auto search. But I can connect wizh the printers IP. The Snapmakers toch pad then wants me to accept the connection, but I then only get a white screen in Luban (showing only the menu bar).

I could find one other user reporting this issue, but with no solution.

Perhaps anyone else can help me?

Thanks in advance gus! :wink:

1 Like

Hello @Noerdian ! welcome here.

Witch Version of Luban do you use? the latest?

Does it the same with out conection to the printer?

Hi @stefix!

I am using Luban V 3.12.3, which should be the latest, I guess?
No, when I just use Luban as a slice, export the G-code file to a USB stick and load that to the printer, everything is fine :slight_smile:

i have the same issue. Connected by manually typing the IP address.

A350 firmware v1.10.1_20200822
Luban version 3.12.3 (3.12.3.1132)

the developer console shows this error message

Uncaught TypeError: Cannot read property 'name' of undefined
    at n.value (app.8f7eb4d3ac965c8c…s?_=1606883368373:2)
    at Eo (app.8f7eb4d3ac965c8c…s?_=1606883368373:2)
    at So (app.8f7eb4d3ac965c8c…s?_=1606883368373:2)
    at Mo (app.8f7eb4d3ac965c8c…s?_=1606883368373:2)
    at Fa (app.8f7eb4d3ac965c8c…s?_=1606883368373:2)
    at za (app.8f7eb4d3ac965c8c…s?_=1606883368373:2)
    at Es (app.8f7eb4d3ac965c8c…s?_=1606883368373:2)
    at xs (app.8f7eb4d3ac965c8c…s?_=1606883368373:2)
    at vs (app.8f7eb4d3ac965c8c…s?_=1606883368373:2)
    at Wa (app.8f7eb4d3ac965c8c…s?_=1606883368373:2)

Downloaded the RC 3.13.0 (3.13.0.1270 as well got this error message in the console

TypeError: Cannot read property 'name' of undefined
    at n.value (app.4bf4e2261f7207780535.bundle.js?_=1608733899656:2)
    at Eo (app.4bf4e2261f7207780535.bundle.js?_=1608733899656:2)
    at So (app.4bf4e2261f7207780535.bundle.js?_=1608733899656:2)
    at Mo (app.4bf4e2261f7207780535.bundle.js?_=1608733899656:2)
    at Fa (app.4bf4e2261f7207780535.bundle.js?_=1608733899656:2)
    at za (app.4bf4e2261f7207780535.bundle.js?_=1608733899656:2)
    at Es (app.4bf4e2261f7207780535.bundle.js?_=1608733899656:2)
    at xs (app.4bf4e2261f7207780535.bundle.js?_=1608733899656:2)
    at vs (app.4bf4e2261f7207780535.bundle.js?_=1608733899656:2)
    at Wa (app.4bf4e2261f7207780535.bundle.js?_=1608733899656:2)

Hello @gilko,

indeed, I get the same error in the console. In the meantime I have written an email to the Snapmaker support with the console errors attached. I will let you know, when they have answered :wink:

Greetings

Thank you for the images and the link. Our software engineer seems to find the bug right now.

It would be appreciated if you can help us to do further investigation. I see that you are good at coding.

1, click ‘view’ button, click ‘toggle developer tools’ to view frontend log。
2, Find the log in the console tab, then follow the steps in the following figure

Please click the code “app.d0faz0491286----”

And then you will see these codes. Please click the curly braces and send me the screenshots of the console.

Here are some tutorials for your reference:

Please watch these videos on our official YouTube channel before you start to use the machine.

sorry. i’m not able to reproduce that error anymore.

I am also having this same problem.

The problem did NOT exist in Luban 3.11. The problem seems to have developed somewhere in 3.12, and has carried on to 3.13.

I have an A250.
My firmware version is V1.10.1_20200822.
My current version of Luban is 3.13.0

Please advise.

Hello everyone,

I just want to let you know, that the snapmaker team is still in contact with me. Currently a software engineer seems to work on that bug. You can also find it this bug appearing on Lubans Github page with high priority: https://github.com/Snapmaker/Luban/issues/640

I will let you know when I learn something new :wink:

It’s been high priority for 11 days, but no-one is assigned to work on it.

Perhaps we have different definitions for the meaning of ‘High Priority’.

The Snapmaker team had some more queries in the meantime. But they told me now this bug will be fixed for the next Luban update.

Is there an expected date when the next version will be released?

Good question, I wasn’t informed about the next release date.

Nobody knows.

There was a pre-release version put out a few weeks ago to prep for the rotary module.

Next release probably won’t occur until the rotary module ships.

Thanks to one of our user, Peter Weidmann, we have fixed this issue and the bug-fixed version of Snapmaker Luban will be released recently.

You can go to our GitHub release page and check it a few days later.

2 Likes

Hello everyone,

the update v3.13.1 is now available, which fixes this bug!
Just start Luban and search for updates :wink:

1 Like

I hadn’t used my A150 in a while, so when I went to use it today, I updated both the machine and the Snapmaker Libyan software (on Mac OS) with the latest…… I never had this issue before, but now every time I connect via WiFi to my A150, the Snapmaker Luban software goes blank (just a white screen). Any help would be greatly appreciated.

P.S. it’s Snapmaker Luban v4.3.0 with the firmware on my A150 being Snapmaker2_V1.11.4_20210201

Hello there :wink:

There is a new firmware available for the Snapmaker2: V1.14.2
So I would recommend updating it via Wifi or USB-stick.