I have three new Snapmaker 2’s, but only two are setup at the moment.
Both machines are connected to the same DEDICATED router, and so is my windows PC.
The router name shows up on BOTH SM touch screens.
When I go to connect to a machine using Luban, only ONE of the named SM’s shows up on the WiFi list. (The first one I setup). The second one is NOT on the list.
However, I CAN connect to the second machine by manually entering it’s IP address.
Why would one machine automatically show up on the list, and the other one need a manual connection? I have rebooted all the machines and the PC but nothing changes.
I will admit to not understanding the different capabilities provided by the different interfaces, mainly because it does not seem to be addressed in the literature. In fact I don’t even recall the mention of a USB connection. Where do you plug it in?
The idea that they may not have “considered that someone may purchase more than one machine”. is hard to fathom, since there is a pull down list of possible devices to connect to, so wouldn’t that imply that there would be more than one to choose from?
Also, regarding what will and will not work with USB vs WiFi.
I guess the requirement is that you MUST use WiFi on a laser setup? (in order to use the camera, which seems essential for layout.)
In my case, the the unit that will not connect automatically is a Laser machine, and it’s interesting that the Camera does not currently work. In fact, I’ve tried two different laser modules, and in both cases, the laser works, but not the camera. When trying to do a calibrate, the camera returns solid black or white images.
Is this something that needs to be an automatic named connection vs a Manual IP connection?
I think you hit the nail on the head. It could also be a WiFi issue, I’ve run into issues before where I have so many devices connected to WiFi that my router will randomly kick one off the network even though the unlucky machine still shows it seeing the network and says is connected but it just gets an error if I try to do anything with it. The majority of people don’t have as much equipment as I do.
Yes, they did have different names, but they had the same prefix ending with a different number. Perhaps the algorithm that compares them isn’t very good.
Hi，if you enable the hot spot on your phone and let both pc and two machines connect to the hot spot, will the two machines show up in the list? Thanks
Actually that IS what I was doing, Both machines and the one PC were attached to the phone’s hotspot. I could connect to one machine by name, but the other one I had to add it’s IP address because it did not show up on the list by name.
Well, it would be great if a Snapmaker staff could verify this. I have to assume they have more than one running at a time on a network in their lab/office/homes
.
My situation is considerably worse, I’m afraid. Computer and Snapmaker both connect just fine via WiFi to house router, and Snapmaker was able to verify latest firmware when it went through setup. Problem: Neither Windows Explorer nor Luban can see the Snapmaker, and entering the IP address in Luban manual connection results in pop-up “3000 millisecond time-out exceeded.” Luban is also latest version.
Anything for this?
@WilliamBosacker its a firewall setting, if their router is on default settings it will be caused by windows firewall and network sharing, if they have network sharing restricted to where they can’t see other devices on their network like paper printers or other pc’s it will not see the Snapmaker either. It is restricted by default in windows.
@mystic22222 you need to enable network sharing in windows, the same way you have to in order to use a printer wirelessly on your network through all computers. As this is a separate issue than the OP’s, PM me if you don’t know how, I can walk you through this.
the snapmaker doesn’t appear to be announcing itself with a standard discovery protocol (mdns, ssdp, ws-discovery - at least not that i could see using wireshark) so it won’t show up in windows network explorer.
It appears it may use a custom multicast packet - in which case your router may not pass this between vlans and if you have igmp snooping enabled its possible your router is suppressing the packet - try flipping your igmp switch / ap / router settings; also try enabling multicast routing if your router supports it (not all do) AND you are using vlans.