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

    Received Duet2 WiFi with DOA WiFi

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    5
    17
    717
    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.
    • prestonthayneundefined
      prestonthayne
      last edited by

      I have not been able to get my Duet2 WiFi to connect to WiFi. I downloaded and installed the 2.05 firmware package from https://github.com/Duet3D/RepRapFirmware/releases. When I send the command to star the wifi nothing happens. The little light on the wifi (where the antenna board sticks out) never lights up and I just keep getting the message "wifi module is being started"

      Here is the terminal output when I send M115:

      <M115 sent>         
      FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.03 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2019-06-13b2
                                                                             ok
      

      Here's what I get when I send M552:

      <M552 sent>WiFi module is being started
                           ok
                             <M552 S0 sent>ok
                               <M552 sent>WiFi module is being started
                                                           ok
                                                             <M552 sent>WiFi module is being started
         ok
           <M552 sent>WiFi module is being started
                                       ok
                                         <M552 sent>WiFi module is being started
                                                                     ok
                                                                       <M552 sent>WiFi module is being started
                   ok
      

      I will keep getting the same message an hour later when I check back.

      Anyone else run into this and solve it?
      Thanks,
      Preston

      1 Reply Last reply Reply Quote 0
      • Vetiundefined
        Veti
        last edited by Veti

        the m115 command says you did not update the firmware and are still on 2.03

        did you by chance just update the wifi firmware and not the duet firmware as well?

        see
        https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware
        you need to send M997 S0 and M997 S1 to update both

        1 Reply Last reply Reply Quote 0
        • prestonthayneundefined
          prestonthayne
          last edited by

          I'm so sorry. I didn't mean to mislead. These are screenshots of what I got before I upgraded. After upgrading I get the same results (except it does show "...FIRMWARE_VERSION: 2.05...).

          prestonthayneundefined 1 Reply Last reply Reply Quote 0
          • prestonthayneundefined
            prestonthayne @prestonthayne
            last edited by

            @prestonthayne

            FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.05 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2019-12-13b1
                                             ok
                                               WiFi module is being started
                                                                           ok
                                                                             WiFi module is being started
                         ok
                           WiFi module is being started
                                                       ok
                                                         WiFi module is being started
                                                                                     ok
                                                                                       WiFi module is being started
                                   ok
                                     WiFi module is being started
                                                                 ok
                                                                   WiFi module is being started
               ok```
            1 Reply Last reply Reply Quote 0
            • A Former User?
              A Former User
              last edited by A Former User

              User M122 to verify wifi firmware version. (and see if you can have your terminal interpet line feeds (LF) as new lines, makes it easier to read)

              If your wifi version is 1.23 then try

              ;enable wifi debug
              M111 P14 S1
              ;clear old wifi
              M552 S-1  G4 S1
              M552 S0   G4 S1
              M588 S"*" G4 S1
              ;add new wifi
              M552 S-1  G4 S1
              M552 S0   G4 S1
              M587 S"enterssid" P"enterpasskey"
              ;start wifi
              M552 S1
              

              (if you type the commands by hand you can skip G4 S1 and just wait a second or two between each command, and skip the lines starting with ;, if you copy and paste you can include it all.)

              1 Reply Last reply Reply Quote 0
              • prestonthayneundefined
                prestonthayne
                last edited by

                @bearer said in Received Duet2 WiFi with DOA WiFi:

                thank you so much for your response and help. When I send M122 I don't see anything that indicates wifi firmware version (printout below). I also tried to send the commands that you suggested and when I send the M588 command I get "M588: Failed to reset the WiFi module to factory settings". I then tried M552 and it still gives "WiFi module is being started"

                M122 response:

                === Diagnostics ===
                RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05 running on Duet WiFi 1.02 or later
                Board ID: 
                Used output buffers: 1 of 24 (1 max)
                === RTOS ===
                Static ram: 25712
                Dynamic ram: 93428 of which 0 recycled
                Exception stack ram used: 256
                Never used ram: 11676
                Tasks: NETWORK(ready,1876) HEAT(blocked,1232) MAIN(running,3824) IDLE(ready,160)
                Owned mutexes:
                === Platform ===
                Last reset 00:04:13 ago, cause: power up
                Last software reset time unknown, reason: User, spinning module GCodes, available RAM 11612 bytes (slot 0)
                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 42.9, current 48.7, max 49.0
                Supply voltage: min 1.4, current 1.7, max 1.7, 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
                Date/time: 1970-01-01 00:00:00
                Cache data hit count 392271515
                Slowest loop: 100.44ms; 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
                === GCodes ===
                Segments left: 0
                Stack records: 2 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 assembling a command 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.17ms; 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 1, noresp 0
                Socket states: 0 0 0 0 0 0 0 0
                ok
                
                1 Reply Last reply Reply Quote 0
                • Phaedruxundefined
                  Phaedrux Moderator
                  last edited by

                  Download these two files and place them on the SD card in the /sys folder with your PC.

                  https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/Duet2CombinedFirmware.bin

                  https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/DuetWiFiServer-1.23.bin

                  Rename DuetWiFiServer-1.23.bin to DuetWiFiServer.bin

                  https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/DuetWebControl-SD-2.0.7.zip

                  Extract this zip file to the /www folder.

                  Now put the SD card back in the duet and power up via USB and send M997 S0:1 in the console to install the main and wifi firmwares.

                  Then send M122 again after it reboots and post the result.

                  Z-Bot CoreXY Build | Thingiverse Profile

                  prestonthayneundefined 1 Reply Last reply Reply Quote 0
                  • prestonthayneundefined
                    prestonthayne @Phaedrux
                    last edited by

                    @Phaedrux Thanks for your suggestion. I followed your directions and it looks like the sub-version did change from 2.05 to 2.05.1. I however still get the same results.

                    M122
                    === Diagnostics ===
                    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later
                    Board ID: 
                    Used output buffers: 1 of 24 (1 max)
                    === RTOS ===
                    Static ram: 25712
                    Dynamic ram: 93428 of which 0 recycled
                    Exception stack ram used: 304
                    Never used ram: 11628
                    Tasks: NETWORK(ready,1876) HEAT(blocked,1232) MAIN(running,3824) IDLE(ready,160)
                    Owned mutexes:
                    === Platform ===
                    Last reset 00:01:02 ago, cause: power up
                    Last software reset time unknown, reason: User, spinning module GCodes, available RAM 11612 bytes (slot 0)
                    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 40.1, current 47.1, max 47.1
                    Supply voltage: min 1.4, current 1.7, max 1.7, 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
                    Date/time: 1970-01-01 00:00:00
                    Cache data hit count 93718842
                    Slowest loop: 0.16ms; 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
                    === GCodes ===
                    Segments left: 0
                    Stack records: 2 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.16ms; 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 disabled
                    WiFi module is disabled
                    Failed messages: pending 2779096485, notready 2779096485, noresp 2779096485
                    Socket states: 0 0 0 0 0 0 0 0
                    ok
                    M552 S-1
                    ok
                    M552 S0
                    ok
                    M588 S"*"
                    M588: Failed to reset the WiFi module to factory settings
                    ok
                    
                    1 Reply Last reply Reply Quote 0
                    • A Former User?
                      A Former User
                      last edited by A Former User

                      edit: seems to be normal output of M122 after M552 S-1. So first try M552 S0 then M122

                      if still the same, then go with:

                      could you run M552 S-1 then M111 P14 S1 followed by another attempt at M997 S1 and post what happens?

                      prestonthayneundefined 1 Reply Last reply Reply Quote 0
                      • prestonthayneundefined
                        prestonthayne @A Former User
                        last edited by

                        @bearer

                        M552 S-1
                        ok
                        M111 P14 S1
                        Debugging enabled for modules: WiFi(14)
                        Debugging disabled for modules: Platform(0) Network(1) Webserver(2) GCodes(3) Move(4) Heat(5) DDA(6) Roland(7) Scanner(8) PrintMonitor(9) Storage(10) PortControl(11) DuetExpansion(12) FilamentSensors(13) Display(15)
                        ok
                        M997 S1
                        Trying to connect at 230400 baud: 
                         failed
                        Trying to connect at 115200 baud: 
                         failed
                        Trying to connect at 74880 baud: 
                         failed
                        Trying to connect at 9600 baud: 
                         failed
                        Error: Installation failed due to comm write error
                        ok
                        
                        dc42undefined 1 Reply Last reply Reply Quote 0
                        • A Former User?
                          A Former User
                          last edited by

                          to quote Monty Python "its dead, thats whats wrong with it"

                          prestonthayneundefined 1 Reply Last reply Reply Quote 0
                          • prestonthayneundefined
                            prestonthayne @A Former User
                            last edited by

                            @bearer said in Received Duet2 WiFi with DOA WiFi:

                            to quote Monty Python "its dead, thats whats wrong with it"

                            Not just "mostly dead?"

                            1 Reply Last reply Reply Quote 0
                            • A Former User?
                              A Former User
                              last edited by

                              I'll defer to the Duet people for the final word, but seems the wifi module has ceased to be; its not even connecting to the bootloader. (If the wifi module is okay then the uart on the main processor is toast, either way, RMA methinks)

                              prestonthayneundefined 1 Reply Last reply Reply Quote 0
                              • prestonthayneundefined
                                prestonthayne @A Former User
                                last edited by prestonthayne

                                @bearer Thanks for your time and expertise (and trip down Python memory lane). I will wait to hear what the Duet people have to say.

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

                                  When and where did you purchase the Duet Wifi?

                                  Z-Bot CoreXY Build | Thingiverse Profile

                                  prestonthayneundefined 1 Reply Last reply Reply Quote 0
                                  • prestonthayneundefined
                                    prestonthayne @Phaedrux
                                    last edited by

                                    @Phaedrux I purchased my board from MatterHackers on March 31, 2020. It took me a while to carve out the time to put it in my 3d printer and when I started to get ready to install it, I found that I couldn't get it to connect to my network. On May 4th I reached out to support @ matterhackers and wen't back and forth with them, trying several things to get it working to no avail. They then asked me to post on this forum because the CEO and Chief Designer needed to see a post here about defective boards.

                                    Thanks,
                                    Preston

                                    Here is the first email that I sent to support about this issue on May 4th:
                                    "I purchased a Duet 2 WiFi last month (Order #101-0000102-1607002) and am trying to set it up. I can’t get the WiFi to start up. When I sent the M552 S1 command in terminal it says ok, then when I send M552 it responds with “WiFi module is being started”. It keeps showing that forever (ok, actually I waited 30 min, but in computer 30 min might as well be forever) and the blue light on the wifi module never even blinks on. Incidentally, the WiFi module is quite hot to the touch.

                                    I’m not sure what to try to get the WiFi working. Please advise.

                                    Regards,
                                    Preston
                                    "

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

                                      @prestonthayne said in Received Duet2 WiFi with DOA WiFi:

                                      @bearer

                                      M552 S-1
                                      ok
                                      M111 P14 S1
                                      Debugging enabled for modules: WiFi(14)
                                      Debugging disabled for modules: Platform(0) Network(1) Webserver(2) GCodes(3) Move(4) Heat(5) DDA(6) Roland(7) Scanner(8) PrintMonitor(9) Storage(10) PortControl(11) DuetExpansion(12) FilamentSensors(13) Display(15)
                                      ok
                                      M997 S1
                                      Trying to connect at 230400 baud: 
                                       failed
                                      Trying to connect at 115200 baud: 
                                       failed
                                      Trying to connect at 74880 baud: 
                                       failed
                                      Trying to connect at 9600 baud: 
                                       failed
                                      Error: Installation failed due to comm write error
                                      ok
                                      

                                      Thanks for that report, it shows that uploading firmware to the WiFi module is not working. I am happy to approve a warranty replacement.

                                      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