Duet WiFi Mini5+ will not connect to WiFi
-
Long story short: I first setup my Duet as DHCP and last night I tried to set a static IP by sending the M587 command through DWC. Yeah, I know hangs head in shame
I lost connection to the web interface, kicked myself, dragged out my MacBook and the USB cable, and connected up via terminal emulator.
M558 S-1 to shut off the module
ok
M558 S0 to put it in idle mode
ok
M587 S"myssid" P"mypassword"
<waits>
Try again.
<waits again>
3rd time's a charm.
<nothing>Ok, no worries, refresh the firmware with M997 S1.
After that, repeat above and get the same results.
Pff, fine. I regenerated the 'runonce.g' file using the Duet web configurator. Copy and paste it into my sys folder on the SD, boot up the Printer... no new devices connect to my wifi router.
Connect the terminal emulator again and run M588 "*" to forget the remembered networks and run through the manual setup steps again, and still get the same results.
I'm fresh out of ideas.
Latest firmware and wifiserver versions.
Help? -
Can you post your config.g and the results of M122?
What terminal software are you using? The mac can be problematic because it will send the commands being typed one character at a time as soon as it's typed.
Can you send these commands and report what they respond with?
M552
M552 S-1
M552 S0
M552 S1
M587 -
@phaedrux I was using SerialTools as suggested on the GettingConnected page. Since you mentioned the mac being problematic, I decided to give it a try with a Windows PC using YAT. First try with M587 got the OK response and M552 S1 had me back in the web interface.
So, thank you!
tbh, I'm kinda shocked that a windows program outdone a *nix OS at terminal emulation
-
@nate-nygren SerialTools is a bit finicky about input; you have to get the command right, without pressing delete or cursor keys. I think it sends each character to the Duet as you type them, rather than when you press return. If you navigate away from SerialTools to another application, and then back, in the middle of writing the command, it won't work. You should get an 'ok' when a command goes through correctly.
Also, make sure you're using straight quotes, eg
"rather than curly quotes, eg”I’ve looked around for a better serial terminal with GUI for Mac, that respects lowercase letters, but haven’t found one. I’m open to any suggestions!
Ian
-
@kaludon209 What?