#Wifi change issue

21 messages · Page 1 of 1 (latest)

pastel ginkgo
#

Having an issue with changing the WiFi settings on my Voron Trident. I moved a new wpa_supplicant.conf file into the bootfs partition on my Pi SD card with the new SSID but the printer isn't showing up on my connected devices list.

The SSID is "Elmos World" and initially I was wondering if the space in the SSID was causing an issue so I changed it to "Elmos\ World" and still no connection to the new network. Am I missing something? Everything I pulled from MainsailOS docs says to just move a new wpa_supplicant.conf file into the SD card and it would connect to the new network.

Anything else to try?

nova dirge
#

Maybe your wifi chip isn’t working

pastel ginkgo
#

The printer has been perfect over Wifi for months, we are switching to a different wifi setup so while both networks are running, I swapped the printer to the new network... it's not visible.

If I put it back on the other network I can see it, and it works fine. So nothing is physically broken.

pastel ginkgo
#

Just tested it again and switching the config back to the old network, the printer popped right up and Mainsail loads. So it's not the hardware.

tribal dagger
#

If your ssid is actually "Elmos world" (with quotation marks) that would be something that need escaping/encoding in the wifi config. If not (the more sane choice of network name), it shouldn't have to be more complicated than

network={
  ssid="Elmos World"
  psk="redacted"
}

with no need to escape the space.

#

Do you have NetworkManager installed (a thing to make it simpler to set up wifi on a desktop/laptop, or in the case of a 3d printer, via klipperscreen)? That basically "overrules" anything in wpa_supplicant.conf, so you'd either have to configure it in networkmanager or disable/uninstall it.

#

The main issue with RPi wifi is its rather crappy antenna, and it might be the new wifi is just too weak from inside the printer. You should be able to scan all visible networks with something like sudo iwlist scan. The output is a bit messy, but it shows signal level and "quality" there. What is a good signal level depends a bit on frequency and bandwidth (I have a bunch of numbers between -54 and -72, though I think the lower ones are some further away APs). Though if your new wifi is a lot lower than the old one (negative numbers, so lower = "minus bigger number") it might just be a signal strength issue. If it is, the solution is often a usb wifi dongle which might have a better antenna, but can also be mounted in a less unfavourable spot.

#

You should also be able to get some kind of logs from wpa supplicant to see if it's trying and failing to connect for some reason.

#

I've never really had any major issues having rpi's on wifi, but for some other devices I've used an external wifi bridge. Something like TP-Link TL-WR902AC (there are a few older/cheaper versions as well for older wifi standards), to let that do the wifiing and just run ethernet to the troublesome device.

ionic torrent
#

I don’t know how MainsailOS works, but if you are running network manager, nmcli is far friendlier than messing with config files.

tribal dagger
#

mainsailos is pretty much a standard raspbian with some 3d printer stuff on top.

#

I've had some shitty experiences with NetworkManager on a couple RPi's (making it be very unreliable on both wired and wifi, disabled it and all was normal again) so I'm rocking it oldschool with network conf, but that's just my preference.

hoary kettle
#

nmtui works well, a little bit simpler for those who aren’t the most comfortable with entering multiple command lines

pastel ginkgo
#

I'll look into these recommendations. Thank you

nova dirge
pastel ginkgo
#

I’ve retyped them multiple times JUST to make sure there wasn’t a typo.

nova dirge
#

Maybe your wifi protocol is different, different wifi protocols require different supplicants?

tribal dagger
nova dirge
ionic torrent