Failed to add SSID to remember list
-
Hi,
I have been trying to get the board up and running today.
When I type M552 in YAT it gives the message
"WiFi module is being started<LF>ok<LF>"and then I typed the next command
M587 S"SSID name" P"password"
It gives the message
"Failed to add SSID to remembered list"I removed the SD card from the duet board and added the Duet2combinedfirmware.bin and duetwifiserver.bin to the sys folder after deleting the previous duetwifiserver.bin file. The sys folder did not contain any firmware file previously.
The two new files were from the latest 2.03 beta 3I first did M997 S0 to install the firmware
after which I did M115
The M587 S"ssid" P"password" was still the same
M587: Failed to add SSID to remembered list<LF>ok<LF>When I type M112 it gives me following message
Emergency Stop! Reset the controller to continue.ok<LF> -
- Run M115 to check that the 2.03beta3 firmware is installed (or at least version 2.02)
- Then run M997 S1 to install the DuetWiFiFirmware.bin file
- Then run M552 S0 to put the WiFi module in idle mode
- Then run M552 to check that it is in idle mode (not still "being started")
- Then you should be able to use M587 to add the SSID and password.
-
The M115 command gives the following message:
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.03beta3 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2019-03-25b6<LF>ok<LF>
The M997 S1 gives following message:
Trying to connect at 230400 baud: failed<LF>Trying to connect at 115200 baud: failed<LF>Trying to connect at 74880 baud: failed<LF>Trying to connect at 9600 baud: failed<LF>Error: Installation failed due to comm write error<LF>ok<LF>
I checked the bits per second under the serial port section it is given as 9600 (in YAT) which I am assuming is the baud rate.
Not sure why it dint connect with the 9600 baud rate ?
Went ahead with the other commands anyways , but no luck.
-
not able to get the firmware installed, any thing else I can do ??
-
@dc42
anything else that I can do ?? -
It looks like you have the main firmware installed. Have you updated the wifi server firmware as well?
-
I downloaded the duetwifiserver.bin file and replaced it with the one in the sys folder
Is there anything else that I have to do to install ?
-
@hussainsail2002 said in Failed to add SSID to remember list:
The M115 command gives the following message:
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.03beta3 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2019-03-25b6<LF>ok<LF>
The M997 S1 gives following message:
Trying to connect at 230400 baud: failed<LF>Trying to connect at 115200 baud: failed<LF>Trying to connect at 74880 baud: failed<LF>Trying to connect at 9600 baud: failed<LF>Error: Installation failed due to comm write error<LF>ok<LF>
I checked the bits per second under the serial port section it is given as 9600 (in YAT) which I am assuming is the baud rate.
Not sure why it dint connect with the 9600 baud rate ?
Went ahead with the other commands anyways , but no luck.
Looks like the WiFi module has failed. Please ask your supplier to replace your Duet.
-
@dc42
My supplier is e3d ,can I take a screen shot of this conversion ?
-
@hussainsail2002 said in Failed to add SSID to remember list:
@dc42
My supplier is e3d ,can I take a screen shot of this conversion ?
Yes, or if you are emailing them, include a link to this thread
-
@dc42 I had the same problem as OP and this fixed it first try. Thank you, and please consider adding this to the getting connected guide. Cheers!
-
A friend of mine has the same problem and has some wifi modules lying around. Would it solve the problem replacing the module or it has nothing to do with it?
-
@FelixH said in Failed to add SSID to remember list:
A friend of mine has the same problem and has some wifi modules lying around. Would it solve the problem replacing the module or it has nothing to do with it?
Probably nothing to do with it. Check that you are running recent main firmware (2.05 or 3.0 or 3.01beta) and WiFi module firmware (1.23).
-
well, apparently he solved it by resoldering the connections of the wifi module... I wouldn't have done it, bu he's braver... thanks