I’m trying to connect manually to my new 2.0 through Luban 3.12.3 and 3.13 when I click the + button to add a connection and then enter the IP of the printer the Luban window goes blank and just sits there. I did get the confirm message on the SM, and it then shifts to a “disconnect” button on the screen, but nothing changes on the software side of things.
The device is connected to a school device network which works to connect to for other devices like smart boards and such.
The Snapmaker WiFi has a very strange configuration. There seem to be lots of problems if you try and access other than from a device on the same wifi network as the Snapmaker. So if your laptop/PC is on a wired connection or the wifi changes to a non Chinese wifi channel, see below, you can have problems. There are lots of comments in the forum, just search WiFi and try and find something that matches your school network configuration.
I’m having a slightly different Luban connection problem. Got my A350 about a week ago and have been printing successfully every day, including today. But this evening when I tried to print an STL file again (had printed it successfully earlier today) I get some weird messages. It generates and loads the G-Code but when I click the connection button it says “Device not Recognized”. It never did that before. So I make the choices for my particular machine and get connected. Then I click “Send to Device via wifi” which works fine. Now the fun part: I click the start button on the touchscreen and get “FabScreen Has Stopped” and something about Google_app_measurement.db. What’s this all about and how do I fix it? Thanks!
Well, this is embarrassing! I discovered a loose connection that I had forgotten to reconnect!!! No wonder “FabScreen” had stopped! So I’m back in business!!
when one job is getting printed we cannot send next file in memory , we have to wait for the current job to be completed. is there any solution for this. also if we upload the file the file transfer happens but you cant access the current setting screen and the screen gets locked with the attached screen.
