Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    Error M587:Failed to add SSID to remembered list.

    Scheduled Pinned Locked Moved
    Duet Web Control
    5
    22
    1.0k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Hiroakiundefined
      Hiroaki @Hiroaki
      last edited by

      @Hiroaki The version is 1.04.

      droftartsundefined 1 Reply Last reply Reply Quote 0
      • droftartsundefined
        droftarts administrators @Hiroaki
        last edited by

        @Hiroaki The M122 reply has been cut off, and the WiFi diagnostics is missing. If you are connecting with YAT:

        Set YAT to use <LF> as the end of line character. This will improve the readability of the messages coming from the Duet. Click "Text Settings" in the "Terminal Settings" and change "EOL sequence:" to <LF>. Click "OK" to close Text Settings. Click "OK" again to close Terminal Settings.

        Ian

        Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

        Hiroakiundefined 2 Replies Last reply Reply Quote 0
        • Hiroakiundefined
          Hiroaki @droftarts
          last edited by

          @droftarts Thank you.
          This is it.
          === Diagnostics ===
          RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later + DueX5
          Board ID: 08DJM-956GL-M43T0-6JKDL-3S86P-994YQ
          Used output buffers: 1 of 24 (2 max)
          === RTOS ===
          Static ram: 25712
          Dynamic ram: 93980 of which 84 recycled
          Exception stack ram used: 264
          Never used ram: 11032
          Tasks: NETWORK(ready,1884) HEAT(blocked,1232) DUEX(suspended,160) MAIN(running,3836) IDLE(ready,160)
          Owned mutexes:
          === Platform ===
          Last reset 00:06:48 ago, cause: power up
          Last software reset time unknown, reason: User, spinning module GCodes, available RAM 10896 bytes (slot 2)
          Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
          Error status: 0
          Free file entries: 10
          SD card 0 detected, interface speed: 20.0MBytes/sec
          SD card longest block write time: 0.0ms, max retries 0
          MCU temperature: min 29.5, current 32.0, max 65.8
          Supply voltage: min 0.0, current 0.5, max 0.6, under voltage events: 0, over voltage events: 0, power good: no
          Driver 0: ok, SG min/max not available
          Driver 1: ok, SG min/max not available
          Driver 2: ok, SG min/max not available
          Driver 3: ok, SG min/max not available
          Driver 4: ok, SG min/max not available
          Driver 5: ok, SG min/max not available
          Driver 6: ok, SG min/max not available
          Driver 7: ok, SG min/max not available
          Driver 8: ok, SG min/max not available
          Driver 9: ok, SG min/max not available
          Date/time: 1970-01-01 00:00:00
          Cache data hit count 681994076
          Slowest loop: 1.58ms; fastest: 0.05ms
          I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
          === Move ===
          Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms
          Bed compensation in use: none, comp offset 0.000
          === DDARing ===
          Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
          === Heat ===
          Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
          Heater 1 is on, I-accum = 0.0
          === GCodes ===
          Segments left: 0
          Stack records: 1 allocated, 0 in use
          Movement lock held by null
          http is idle in state(s) 0
          telnet is idle in state(s) 0
          file is idle in state(s) 0
          serial is ready with "M122" in state(s) 0
          aux is idle in state(s) 0
          daemon is idle in state(s) 0
          queue is idle in state(s) 0
          autopause is idle in state(s) 0
          Code queue is empty.
          === Network ===
          Slowest loop: 0.84ms; fastest: 0.00ms
          Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
          HTTP sessions: 0 of 8

          • WiFi -
            Network state is starting
            WiFi module is disabled
            Failed messages: pending 0, notready 0, noresp 0
            Socket states: 0 0 0 0 0 0 0 0
            ok
          droftartsundefined 1 Reply Last reply Reply Quote 0
          • Hiroakiundefined
            Hiroaki @droftarts
            last edited by

            @droftarts

            M552 s-1
            WiFi module stopped
            ok
            M552 s0
            ok
            M122
            then it was still

            • WiFi -
              Network state is starting
              WiFi module is disabled
              Failed messages: pending 0, notready 0, noresp 0
              Socket states: 0 0 0 0 0 0 0 0
              ok
            1 Reply Last reply Reply Quote 0
            • droftartsundefined
              droftarts administrators @Hiroaki
              last edited by

              @Hiroaki Send M552 S-1, then M122, M552 S0, then M122, and M552 S1, then M122. This is what the response from my Duet 2 WiFi looks like (you can just copy the WiFi part at the end):

              M552 S-1
              WiFi module stopped
              ok
              M122
              === Diagnostics ===
              RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05 running on Duet WiFi 1.02 or later
              Board ID: 08DGM-9T6BU-FG3SD-6JKD4-3S86N-KAMHF
              ...
              -WiFi -
              Network state is disabled
              WiFi module is disabled
              Failed messages: pending 0, notready 0, noresp 0
              Socket states: 0 0 0 0 0 0 0 0
              ok

              M552 S0
              ok
              WiFi module started
              M122
              ...
              -WiFi -
              Network state is running
              WiFi module is idle
              Failed messages: pending 0, notready 0, noresp 0
              WiFi firmware version 1.23
              WiFi MAC address a0:20:a6:31:b4:b9
              WiFi Vcc 3.36, reset reason Turned on by main processor
              WiFi flash size 4194304, free heap 30176
              Socket states: 0 0 0 0 0 0 0 0
              ok

              M552 S1
              ok
              WiFi module is connected to access point BTWholeHome-XXX, IP address 192.168.0.12
              M122
              ...
              -WiFi -
              Network state is running
              WiFi module is connected to access point
              Failed messages: pending 0, notready 0, noresp 0
              WiFi firmware version 1.23
              WiFi MAC address a0:20:a6:31:b4:b9
              WiFi Vcc 3.37, reset reason Turned on by main processor
              WiFi flash size 4194304, free heap 25568
              WiFi IP address 192.168.0.12
              WiFi signal strength -43dBm, reconnections 0, sleep mode modem
              Socket states: 0 0 0 0 0 0 0 0
              ok

              If you're not getting something similar, I'd guess that the WiFi module has failed. The usual reason for this is a power surge on the 3.3V line; the WiFi board and SD card are often the first to fail if this has happened, but can protect the main processor from failing.

              It is possible that the WiFi module firmware has not flashed correctly. Try downloading a fresh DuetWiFiServer-1.23.bin from https://github.com/Duet3D/RepRapFirmware/releases/tag/2.05.1 and upload it to the 'sys' folder on the SD card, then send M997 S1.

              Ian

              Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

              Hiroakiundefined 2 Replies Last reply Reply Quote 0
              • beachtecundefined
                beachtec
                last edited by beachtec

                Hello @Hiroaki... I have had this issue myself a few times. The advice here did solve it; but I had to do it a couple of times. Re-flashing the firmware more than once might be necessary. I also found that in BOSSA, using the setting "erase all" seemed to yield the best results. Good luck to you!

                Hiroakiundefined 1 Reply Last reply Reply Quote 0
                • Hiroakiundefined
                  Hiroaki @droftarts
                  last edited by

                  @droftarts Thank you. As it's getting late night, I will do it tomorrow.
                  By the way do you think it's possible to change the wifi module ?

                  1 Reply Last reply Reply Quote 0
                  • Hiroakiundefined
                    Hiroaki @beachtec
                    last edited by

                    @beachtec Thank you. I will try tomorrow. It's 0:21AM ...
                    Best Regards

                    1 Reply Last reply Reply Quote 0
                    • Hiroakiundefined
                      Hiroaki @droftarts
                      last edited by

                      @droftarts
                      One question .
                      Upload Duetwifiserver-1.23.bin to the SYS not WWW folder?
                      Regards

                      droftartsundefined 1 Reply Last reply Reply Quote 0
                      • droftartsundefined
                        droftarts administrators @Hiroaki
                        last edited by

                        @Hiroaki said in Error M587:Failed to add SSID to remembered list.:

                        One question .
                        Upload Duetwifiserver-1.23.bin to the SYS not WWW folder?

                        Yes, firmware updates go in the 'sys' folder. The 'www' folder is for DWC components.

                        Ian

                        Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

                        Hiroakiundefined 2 Replies Last reply Reply Quote 0
                        • Hiroakiundefined
                          Hiroaki @droftarts
                          last edited by

                          @droftarts ok Thank you.

                          1 Reply Last reply Reply Quote 0
                          • Phaedruxundefined
                            Phaedrux Moderator
                            last edited by

                            DuetWiFiServer-1.23.bin

                            I think you'll need to rename the file and remove the -1.23 part so that the final file name is just DuetWiFiServer.bin

                            Z-Bot CoreXY Build | Thingiverse Profile

                            Hiroakiundefined 1 Reply Last reply Reply Quote 0
                            • Hiroakiundefined
                              Hiroaki @droftarts
                              last edited by

                              @droftarts Hello
                              Thank you so much.
                              I could solve the problem.
                              sent M997 S1 and then ok.
                              I appreciate that.
                              Thank you

                              1 Reply Last reply Reply Quote 0
                              • Hiroakiundefined
                                Hiroaki @Phaedrux
                                last edited by

                                @Phaedrux Thank you.
                                This was also helped me !
                                Thank you.

                                1 Reply Last reply Reply Quote 0
                                • First post
                                  Last post
                                Unless otherwise noted, all forum content is licensed under CC-BY-SA