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

    New Board Can't Connect to Wi-Fi.

    Scheduled Pinned Locked Moved
    General Discussion
    4
    18
    2.6k
    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.
    • dc42undefined
      dc42 administrators
      last edited by

      I presume you mean until the M582 S1 command, not M587 S1. I suggest the following:

      1. Check that your router is configured to provide a network on the 2.4GHz WiFi band. The Duet WiFi does not support 5GHz.

      2. Run M577 M587 with no parameters to list the configured WiFi networks, and check that the SSID shown is exactly the same as the one your WiFi network transmits on 2.4GHz, as shown on your smartphone if you scan for WiFi networks. SSIDs are case-sensitive.

      3. If the SSID is exactly correct then it is probably a signal strength issue. See https://duet3d.dozuki.com/Wiki/WiFi_disconnections_and_AJAX_timeout_errors#Section_How_to_improve_RSSI.

      Duet WiFi hardware designer and firmware engineer
      Please do not ask me for Duet support via PM or email, use the forum
      http://www.escher3d.com, https://miscsolutions.wordpress.com

      1 Reply Last reply Reply Quote 0
      • tonydacrowundefined
        tonydacrow
        last edited by

        Thanks for the help, DC42.

        I ran the M577 command and got the following: "ok<lf>" Nothing else. I confirmed that my network is running at 2.4 GHz and that signal strength is excellent with a link speed of 1.44 Mbps on my cell phone. Any other thoughts on what I can do?

        Thanks again.</lf>

        1 Reply Last reply Reply Quote 0
        • dc42undefined
          dc42 administrators
          last edited by

          I'm sorry. I meant M587.

          Duet WiFi hardware designer and firmware engineer
          Please do not ask me for Duet support via PM or email, use the forum
          http://www.escher3d.com, https://miscsolutions.wordpress.com

          1 Reply Last reply Reply Quote 0
          • tonydacrowundefined
            tonydacrow
            last edited by

            This post is edited to add correct information:

            Sadly, no joy.

            When I use the 587 command, I get the following: "Remembered networks:<lf>TNCAP2FCC19<lf>My Network Name<lf>your=network-My Network Name Fa<lf>your-network-My Network Name Fa<lf>My Network Name <lf>My Network Name 2<lf>ok<lf>"

            When I type the 552 S1 command, I still get: "ok<lf>WiFi reported error: no known networks found<lf>Wifi module is idle<lf>"

            Hope I'm not being dense…</lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf>

            1 Reply Last reply Reply Quote 0
            • tonydacrowundefined
              tonydacrow
              last edited by

              The latest: now an M587 command reports "M587: Failed to retrieve network list<lf>ok<lf>" This is after an M552 command that shows WiFi module idle. Seems like I have a defective board. Anyone else have any ideas before I return the board as defective?</lf></lf>

              1 Reply Last reply Reply Quote 0
              • dc42undefined
                dc42 administrators
                last edited by

                Please run M122 and check that the versions of main firmware (listed near the start of the response) and WiFi firmware (listed under the "Network" section) are compatible.

                Duet WiFi hardware designer and firmware engineer
                Please do not ask me for Duet support via PM or email, use the forum
                http://www.escher3d.com, https://miscsolutions.wordpress.com

                1 Reply Last reply Reply Quote 0
                • tonydacrowundefined
                  tonydacrow
                  last edited by

                  I had Firmware version 1.19.2 but upgraded to the latest 1.21 via SD card in the hopes that would help. When I run M122 I get the following:
                  m122
                  === Diagnostics ===<lf>Used output buffers: 1 of 32 (1 max)<lf>=== Platform ===<lf>RepRapFirmware for Duet 2 WiFi/Ethernet version 1.21 running on Duet WiFi 1.02 or later<lf>Board ID: 08DDM-9FAM2-LW4S4-6J1DA-3S46R-K3TZW<lf>Static ram used: 16152<lf>Dynamic ram used: 100600<lf>Recycled dynamic ram: 2032<lf>Stack ram used: 3576 current, 4420 maximum<lf>Never used ram: 7868<lf>Last reset 00:00:18 ago, cause: power up<lf>Last software reset details not available<lf>Error status: 0<lf>Free file entries: 10<lf>SD card 0 detected, interface speed: 20.0MBytes/sec<lf>SD card longest block write time: 0.0ms<lf>MCU temperature: min 21.3, current 23.6, max 23.7<lf>Supply voltage: min 1.4, current 1.5, max 1.5, under voltage events: 0, over voltage events: 0<lf>Driver 0: ok, SG min/max not available<lf>Driver 1: ok, SG min/max not available<lf>Driver 2: ok, SG min/max not available<lf>Driver 3: ok, SG min/max not available<lf>Driver 4: ok, SG min/max not available<lf>Date/time: 1970-01-01 00:00:00<lf>Slowest main loop (seconds): 0.001772; fastest: 0.000041<lf>=== Move === <warning: maximal="" number="" of="" bytes="" per="" line="" exceeded!="" check="" the="" end-of-line="" settings="" or="" increase="" limit="" in="" advanced="" terminal="" settings.="">I can't tell you how much I appreciate the help, DC!</warning:></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf>

                  1 Reply Last reply Reply Quote 0
                  • tonydacrowundefined
                    tonydacrow
                    last edited by

                    I noticed that in my last post, I exceeded the number of bytes per line which truncated the command reply. Here is the full display with the M122 command:

                    m122
                    === Diagnostics ===<lf>Used output buffers: 1 of 32 (1 max)<lf>=== Platform ===<lf>RepRapFirmware for Duet 2 WiFi/Ethernet version 1.21 running on Duet WiFi 1.02 or later<lf>Board ID: 08DDM-9FAM2-LW4S4-6J1DA-3S46R-K3TZW<lf>Static ram used: 16152<lf>Dynamic ram used: 100600<lf>Recycled dynamic ram: 2032<lf>Stack ram used: 3576 current, 4420 maximum<lf>Never used ram: 7868<lf>Last reset 00:02:09 ago, cause: power up<lf>Last software reset details not available<lf>Error status: 0<lf>Free file entries: 10<lf>SD card 0 detected, interface speed: 20.0MBytes/sec<lf>SD card longest block write time: 0.0ms<lf>MCU temperature: min 18.7, current 25.6, max 25.7<lf>Supply voltage: min 0.5, current 1.7, max 1.7, under voltage events: 0, over voltage events: 0<lf>Driver 0: ok, SG min/max not available<lf>Driver 1: ok, SG min/max not available<lf>Driver 2: ok, SG min/max not available<lf>Driver 3: ok, SG min/max not available<lf>Driver 4: ok, SG min/max not available<lf>Date/time: 1970-01-01 00:00:00<lf>Slowest main loop (seconds): 0.001768; fastest: 0.000041<lf>=== Move ===<lf>MaxReps: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0<lf>Scheduled moves: 0, completed moves: 0<lf>Bed compensation in use: none<lf>Bed probe heights: 0.000 0.000 0.000 0.000 0.000<lf>=== Heat ===<lf>Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1<lf>Heater 1 is on, I-accum = 0.0<lf>=== GCodes ===<lf>Segments left: 0<lf>Stack records: 1 allocated, 0 in use<lf>Movement lock held by null<lf>http is idle in state(s) 0<lf>telnet is idle in state(s) 0<lf>file is idle in state(s) 0<lf>serial is ready with "m122" in state(s) 0<lf>aux is idle in state(s) 0<lf>daemon is idle in state(s) 0<lf>queue is idle in state(s) 0<lf>autopause is idle in state(s) 0<lf>Code queue is empty.<lf>=== Network ===<lf>Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)<lf>HTTP sessions: 0 of 8<lf>- WiFi -<lf>Network state is running<lf>WiFi module is idle<lf>Failed messages: pending 0, notready 0, noresp 0<lf>WiFi firmware version 1.19.2<lf>WiFi MAC address 60:01:94:73:5b:4b<lf>WiFi Vcc 3.08, reset reason Turned on by main processor<lf>WiFi flash size 4194304, free heap 40544<lf>Socket states: 0 0 0 0 0 0 0 0<lf>=== Expansion ===<lf>ok</lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf>

                    1 Reply Last reply Reply Quote 0
                    • whosrdaddyundefined
                      whosrdaddy
                      last edited by

                      Please put LF as line ending (<eol>) in YAT, this will give you proper printouts</eol>

                      1 Reply Last reply Reply Quote 0
                      • tonydacrowundefined
                        tonydacrow
                        last edited by

                        Thanks for the tip, Whosrdaddy.

                        1 Reply Last reply Reply Quote 0
                        • tonydacrowundefined
                          tonydacrow
                          last edited by

                          Here is the command response in proper format:

                          ok
                          m122 <cr>=== Diagnostics ===
                          Used output buffers: 1 of 32 (9 max)
                          === Platform ===
                          RepRapFirmware for Duet 2 WiFi/Ethernet version 1.21 running on Duet WiFi 1.02 or later
                          Board ID: 08DDM-9FAM2-LW4S4-6J1DA-3S46R-K3TZW
                          Static ram used: 16152
                          Dynamic ram used: 100800
                          Recycled dynamic ram: 1832
                          Stack ram used: 3576 current, 4584 maximum
                          Never used ram: 7704
                          Last reset 00:01:29 ago, cause: power up
                          Last software reset details not available
                          Error status: 0
                          Free file entries: 10
                          SD card 0 detected, interface speed: 20.0MBytes/sec
                          SD card longest block write time: 0.0ms
                          MCU temperature: min 26.5, current 27.2, max 27.2
                          Supply voltage: min 1.6, current 1.7, max 1.7, under voltage events: 0, over voltage events: 0
                          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
                          Date/time: 1970-01-01 00:00:00
                          Slowest main loop (seconds): 0.004284; fastest: 0.000042
                          === Move ===
                          MaxReps: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0
                          Scheduled moves: 0, completed moves: 0
                          Bed compensation in use: none
                          Bed probe heights: 0.000 0.000 0.000 0.000 0.000
                          === 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 ===
                          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 running
                            WiFi module is idle
                            Failed messages: pending 0, notready 0, noresp 0
                            WiFi firmware version 1.19.2
                            WiFi MAC address 60:01:94:73:5b:4b
                            WiFi Vcc 3.08, reset reason Turned on by main processor
                            WiFi flash size 4194304, free heap 40544
                            Socket states: 0 0 0 0 0 0 0 0
                            === Expansion ===
                            ok</cr>
                          1 Reply Last reply Reply Quote 0
                          • dc42undefined
                            dc42 administrators
                            last edited by

                            You are running main firmware 1.21 but WiFi firmware 1.19.2. Please upgrade your wifi firmware to 1.21. As you can't connect via WiFi at present, you will need to move the SD card to a PC, copy the new DuetWiFiServer.bin file to /sys, eject or safely remove it, put the card back in the Duet, restart the Duet, and send M997 S1.

                            After that, if you run M122 it should report "WiFi firmware version 1.21" in the Network section.

                            Duet WiFi hardware designer and firmware engineer
                            Please do not ask me for Duet support via PM or email, use the forum
                            http://www.escher3d.com, https://miscsolutions.wordpress.com

                            1 Reply Last reply Reply Quote 0
                            • tonydacrowundefined
                              tonydacrow
                              last edited by

                              Sadly, still no joy.

                              I updated both firmware and wifi drivers to 1.21.

                              When I run M122, I get:
                              m122
                              === Diagnostics ===
                              Used output buffers: 1 of 32 (8 max)
                              === Platform ===
                              RepRapFirmware for Duet 2 WiFi/Ethernet version 1.21 running on Duet WiFi 1.02 or later
                              Board ID: 08DDM-9FAM2-LW4S4-6J1DA-3S46R-K3TZW
                              Static ram used: 16152
                              Dynamic ram used: 100800
                              Recycled dynamic ram: 1832
                              Stack ram used: 3576 current, 4900 maximum
                              Never used ram: 7388
                              Last reset 00:17:35 ago, cause: power up
                              Last software reset details not available
                              Error status: 0
                              Free file entries: 10
                              SD card 0 detected, interface speed: 20.0MBytes/sec
                              SD card longest block write time: 0.0ms
                              MCU temperature: min 31.8, current 35.3, max 35.4
                              Supply voltage: min 1.6, current 1.7, max 1.7, under voltage events: 0, over voltage events: 0
                              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
                              Date/time: 1970-01-01 00:00:00
                              Slowest main loop (seconds): 0.100089; fastest: 0.000041
                              === Move ===
                              MaxReps: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0
                              Scheduled moves: 0, completed moves: 0
                              Bed compensation in use: none
                              Bed probe heights: 0.000 0.000 0.000 0.000 0.000
                              === 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 ===
                              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 running
                                WiFi module is idle
                                Failed messages: pending 0, notready 0, noresp 0
                                WiFi firmware version 1.21
                                WiFi MAC address 60:01:94:73:5b:4b
                                WiFi Vcc 3.36, reset reason Turned on by main processor
                                WiFi flash size 4194304, free heap 19808
                                Socket states: 0 0 0 0 0 0 0 0
                                === Expansion ===
                                ok

                              When I run M587, I get:
                              m587
                              Remembered networks:
                              TNCAP2FCC19 IP=192.168.1.14 GW=0.0.0.0 NM=0.0.0.0
                              MY NETWORK NAME IP=0.0.0.0 GW=0.0.0.0 NM=0.0.0.0
                              your=network-MY NETWORK NAME IP=0.0.0.0 GW=0.0.0.0 NM=0.0.0.0
                              your-network-MY NETWORK NAME IP=0.0.0.0 GW=0.0.0.0 NM=0.0.0.0
                              MY NETWORK NAME IP=0.0.0.0 GW=0.0.0.0 NM=0.0.0.0
                              MY NETWORK NAME IP=0.0.0.0 GW=0.0.0.0 NM=0.0.0.0

                              Yet, when I run the M552 S1 after setting-up the network with the M587 S"MY NETWORK NAME" P"MY PASSWORD" command, I get:
                              m552 s1
                              ok
                              WiFi reported error: no known networks found
                              WiFi module is idle

                              ok

                              My wifi network has an apostrophe in its name. Perhaps that could that be the problem? Any additional thoughts? At this point I'm close to stumped…

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

                                Never trust an apostrophe and anything to do with computer naming.

                                Z-Bot CoreXY Build | Thingiverse Profile

                                1 Reply Last reply Reply Quote 0
                                • dc42undefined
                                  dc42 administrators
                                  last edited by

                                  Apostrophe in a quoted string forces the following character to lowercase. So you need to use two apostrophes to represent one, in both SSIDs and passwords.

                                  I suggest you send M588 "*" to delete all those dud remembered networks, then send the M587 command using two apostrophes in the SSID this time. Then send M587 without parameters to check it is remembered correctly.

                                  Duet WiFi hardware designer and firmware engineer
                                  Please do not ask me for Duet support via PM or email, use the forum
                                  http://www.escher3d.com, https://miscsolutions.wordpress.com

                                  1 Reply Last reply Reply Quote 0
                                  • tonydacrowundefined
                                    tonydacrow
                                    last edited by

                                    Huzzah! That was the issue; a silly little apostrophe in the network name. My Duet Wifi is now connected to my network.

                                    A big THANK YOU to all who helped, but especially to you dc42 for you patience and generosity with this issue!

                                    1 Reply Last reply Reply Quote 0
                                    • dc42undefined
                                      dc42 administrators
                                      last edited by

                                      No problem, it was you who suggested the apostrophe might be the problem and made the diagnosis easy. I've updated step 7 at https://duet3d.dozuki.com/Guide/1.%29+Getting+Connected+to+your+Duet/7?lang=en to cover the case of apostrophes in the SSID and password.

                                      Duet WiFi hardware designer and firmware engineer
                                      Please do not ask me for Duet support via PM or email, use the forum
                                      http://www.escher3d.com, https://miscsolutions.wordpress.com

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