WiFi setup issues
-
Hello,
I'm the proud owner of a new Duet WiFi controller for a delta printer I recently purchased from Ultibots.
At first I had issues connecting to the board from my Windows PC over USB using the cable that came with the Duet. The Duet was powering up, but my PC wasn't even recognizing that there was a USB device connected. After much hair pulling, I tried a different USB cable, and it came up on the first try. So, I'm now at the point where I can run Pronterface and send gcode commands, so I'm attempting to set up WiFi.
I'm able to connect to the DuetWifi SSID from my phone. I select the appropriate SSID for my 2.4GHz ATT UVerse home network, and enter the password (yes, I've verified that they are correct) into the web page, and then click "Save and reboot". After that, the web page says "All set!" and "(Please reboot me.)". At this point, I go to Pronterface and do the M552 S0 command, followed by M552 S1. After 30 seconds or so, I get a response saying that WiFi is running as an access point with the SSID DuetWiFi.
So, it sounds to me like the WiFi connection is not being established. Is there something I'm doing wrong in this process? I'm doing my best to follow the directions on the Getting_connected page on the wiki.
If it looks like my sequence is correct, then is there any way to troubleshoot issues during the WiFi connection sequence? For example, some kind of super-secret debug output that I can enable over USB to figure out why the connection is failing?
Thanks in advance for your help.
-
There is a known bug with the handling of WiFi access passwords at present, which is that non-ascii characters in the password are not handled correctly. Might this be the problem?
-
There is a known bug with the handling of WiFi access passwords at present, which is that non-ascii characters in the password are not handled correctly. Might this be the problem?
The only non alpha numeric characters in the password are '+' and '=', but last I checked, those were ASCII.
-
I'll take a look at the code tomorrow. I did wonder whether it wasn't doing URI decoding, and if that's the case then i think the + character would be a problem too.
-
Thanks, that makes sense.
I'm not able to change the password on this router, but in the meantime, I've set up another access point with an all numeric password. The duet is able to connect just fine in this case, so it's time to get on with the build…
I'll take a look at the code tomorrow. I did wonder whether it wasn't doing URI decoding, and if that's the case then i think the + character would be a problem too.
