Can't access wifi
-
Everything erased and re-entered. Wifi shut down to erase the 0.0.0.0 entry. Wifi brought back up and confirmed all entries for the duet are gone.
As soon as I turned on power to the duet, both ip numbers show up with 0.0.0.0 being the connected ip address and the 192.168.xxx.xxx being the not connected number. When I direct the browser to 192.168.xxx.xxx, I get the right web screen but the console tells me "failed to connect to 192.168.xxx.xxx" -
At this point in time I'd try flashing RRF2 joining the network and going back to RRF3 if it works tbh. If it doesn't work I'd be tempted to try connecting to the ESP8266 and using esptool.py from the computer and erasing the whole flash before updating it with M997
oh, and thanks for seting the record straight about the qoutes, I never actually tried it myself come to think of it.
-
@jens55 said in Can't access wifi:
I now get two (!!!) entries in the client list on the correct network. One has the correct ip and is not properly connected, the other is as ip 0.0.0.0 but it shows as connected with good signal.
btw, is this on your wifi ruter or using m587 on the duet?
-
Have you tried the macro method yet?
On occasion where I've had issues with the wifi I have created a couple macros to help simplify the process of clearing and re-adding the network. I use a dedicated old wifi router for the printer network as a simple access point. The main router provides a DHCP reservation for the printer, so I don't have to set an IP on the DUET.
I have a PanelDue so I can run them from there, but you can execute them via USB terminal as well with M98 P.
; WifiReset.g ; Use in case wifi module is not running. (Blue light off) ; M291 R"Reset wifi module? Y/N" P"Caution. Will cause pause in print" S3 T10 M552 S0 ; Disable network module G4 S5 ; wait 5 seconds M552 S1 ; Enable network module M291 P"Wifi module reset. Check console or DWC.";WifiClear.g ; Clear all wifi networks ; M291 R"Clear WIFI networks? Y/N" P"Caution. New network must be added." S3 T10 M552 S0 ; Disable network module G4 S5 ; wait 5 seconds M588 S"*" ; Clear all saved wifi networls M291 R"WIFI networks forgotten." P"You must add a new WIFI network."; WifiAdd.g ; Add default wifi network ; M291 R"Add default WIFI network? Y/N" P"This will add duetwifi access point." S3 T10 M552 S0 ; Disable network module G4 S5 ; wait 5 seconds M587 S"duetwifi" P"password" ; Add duetwifi SSID to remembered networks list G4 S5 ; wait 5 seconds M552 S1 ; reenable wifi module M291 R"duetwifi SSID added." P"Check console to verify IP address."Works every time I've had an issue.
-
Yes, the connected clients thing is on my router and the M587 was done via the usb serial link.
On reflection, I think that the static IP that shows as not connected on the router is a reflection of the static IP being set up and the 0.0.0.0 ip is somehow done via the duet.
I am now thinking that maybe DHCP isn't properly set up on the duet and I will be exploring that. I will also read up and follow initial setup instructions and see if I missed something there. I had no issues with the initial setup so it's difficult to understand why I am having the issues now. I also don't understand why I would see a perfectly good duet web page in my browser when there is no connection (and I doubt anything is cached because these are new IP numbers)
I do have a memory card sitting here with my old RRF2 version and I did try that in between with no luck.
I have not tried the macro approach yet but will try that if the DHCP investigation doesn't get me anywhere.
-
The main benefit of the macro approach is that it completely removes any special character shenanigans over the terminal. And the convenience I suppose.
-
@jens55 said in Can't access wifi:
I do have a memory card sitting here with my old RRF2 version and I did try that in between with no luck.
you need to actually flash RRF2 to the Duet not just change sd cards btw.
-
Well ...... over the terminal I did a M552 S0 got the right reply and followed it up with M552 S1 and got a "connected"message
The router still shows IP 0.0.0.0 connected (with the right mac id) and a 192.168.xxx.xxx not connected (same mac id)
Ran a "home all" on the web interface and it did exactly what it was supposed to do.
So at this point I have a printer that seems connected, reported connected but isn't properly shown as connected on the router.
I haven't got the foggiest what I did to make it connect that is any different from what I did before other than the dwells were longer than the 1 second because I did it by hand over the terminal.
If nothing else, there is progress of sorts
Thanks for helping me resolve the connectivity issue. I will have to work on this some more to see if I can figure out what is going on.
-
@bearer said in Can't access wifi:
@jens55 said in Can't access wifi:
I do have a memory card sitting here with my old RRF2 version and I did try that in between with no luck.
you need to actually flash RRF2 to the Duet not just change sd cards btw.
Never did that ....
-
Why do I need to flash RRF2 rather than change the memory card from a previously running RRF2 setup? (other than to maybe deal with the remembered wifi stuff)
-
@Phaedrux said in Can't access wifi:
The main benefit of the macro approach is that it completely removes any special character shenanigans over the terminal. And the convenience I suppose.
I think I will set up the same macros for the next time (because there ALWAYS is a next time )
-
@jens55 what router is it that you have? Did you eventually save the SSID and password with, or without, I0.0.0.0 parameter set? Setting that shouldn’t be necessary, but if there’s a bug in the firmware, I’d guess it’ll be that it’s doing something odd with the 0.0.0.0 IP address, which is why you get that reported on the router. Then the router is doing some address mapping/translation to make it accessible.
Ian
-
@jens55 said in Can't access wifi:
Why do I need to flash RRF2 rather than change the memory card from a previously running RRF2 setup? (other than to maybe deal with the remembered wifi stuff)
first of all, you don't have to - but in order to try and see if there is a difference between RRF2 and RRF3 its not sufficient to just swap memory cards as the firmware is flashed to the MCU regardless of memory card.
the thinking is I know it works on RRF2, if RRF2 can store it properly in the WiFi module it should continiue working if you upgrade the MCU back to RRF3.
I got sidetracked with unexpected stuff othrewise I'd test it with RRF3 now.
-
It is a new Pepwave Surf Soho, an enterprise grade router.
I have the ssid and password set with no ip given however when I look at what the wifi radio remembers, it has the 0.0.0.0 ip set ... but that is always set like that because in theory that means 'use DHCP'.
The router is not set up to do any translating or anything. On top of that I have removed the static IP reservation from the router and the duet still connects to the same IP number although DHCP should give a completely different IP.
This could be related to the DHCP lease time and I have reduced that to an hour but it will take some time until it updates things. -
@bearer said in Can't access wifi:
@jens55 said in Can't access wifi:
first of all, you don't have to - but in order to try and see if there is a difference between RRF2 and RRF3 its not sufficient to just swap memory cards as the firmware is flashed to the MCU regardless of memory card.
Got it .... didn't realize that the mcu itself was flashed. Thanks!
-
what do you actually have in your config.g right now?
-
@Phaedrux said in Can't access wifi:
what do you actually have in your config.g right now?
-
OK, I am pretty sure I have a bug in the router. I rebooted the router and the duet part of the client list went down to a single device although it still is at the previous reserved IP number that is no longer reserved. I suspect that there is some aspect of the last IP number that is still being remembered. I no longer have the duet mac address on ip 0.0.0.0 ... another device has taken that place now
-
A closing update: I had the DHCP pool of IP numbers overlapping the statically assigned IP numbers so the router remembered what IP number was previously assigned. Once that configuration error was corrected, DHCP IP addresses were correct.
I still have the 0.0.0.0 entry which is now pointing to an Epson printer. I have no idea what the story there is but it has nothing to do with the Duet so I am closing this thread out.
Unfortunately, I have no idea what really was happening but I will set up the macros as suggested by Phaedrux - thanks! -
System referenced this topic
