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

    Duet 2 Wifi: wifi no longer works

    Scheduled Pinned Locked Moved
    General Discussion
    3
    6
    233
    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.
    • tahiundefined
      tahi
      last edited by

      Hello everyone.

      I need help with the wifi on my card that has stopped working.

      The card is a Duet 2 Wifi rev 1.04c with integrated antenna purchased in January with the original 3.2 firmware on the card.
      I used the config tool and the wifi connected correctly. I had access to the web interface and the printer responded correctly.

      This morning the machine would not connect. The blue diode was not lit anymore.
      After a few tests that did not give anything, I thought that the files on the SD card might be corrupted.
      It turned out that the SD card was dead without me understanding why.

      So I changed it and copied the backup from the previous card.
      I launch the printer and... it still doesn't work.

      So I redid the configuration with the config tool by putting the information of my wifi. Still the same. No wifi diode and of course no connection.

      I connected my PC in USB and I did M115 followed by M122 which gave me that:

      M115
      FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.2 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2021-01-05
      ok
      M122
      === Diagnostics ===
      RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2 running on Duet WiFi 1.02 or later
      Board ID: 0JD0M-9P6B2-NJ4S8-6JKD4-3SD6Q-9U7AL
      Used output buffers: 1 of 24 (1 max)
      === RTOS ===
      Static ram: 23460
      Dynamic ram: 73112 of which 12 recycled
      Never used RAM 15496, free system stack 184 words
      Tasks: NETWORK(ready,521) HEAT(blocked,323) MAIN(running,442) IDLE(ready,19)
      Owned mutexes: USB(MAIN)
      === Platform ===
      Last reset 00:32:27 ago, cause: power up
      Last software reset details not available
      Error status: 0x00
      Aux0 errors 0,0,0
      MCU temperature: min 52.0, current 59.6, max 59.9
      Supply voltage: min 0.1, current 0.4, max 0.6, under voltage events: 0, over voltage events: 0, power good: no
      Driver 0: position 0, ok, SG min/max not available
      Driver 1: position 0, ok, SG min/max not available
      Driver 2: position 0, ok, SG min/max not available
      Driver 3: position 0, ok, SG min/max not available
      Driver 4: position 0, ok, SG min/max not available
      Driver 5: position 0
      Driver 6: position 0
      Driver 7: position 0
      Driver 8: position 0
      Driver 9: position 0
      Driver 10: position 0
      Driver 11: position 0
      Date/time: 1970-01-01 00:00:00
      Cache data hit count 2621479119
      Slowest loop: 100.93ms; fastest: 0.14ms
      I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
      === Storage ===
      Free file entries: 10
      SD card 0 detected, interface speed: 20.0MBytes/sec
      SD card longest read time 0.4ms, write time 0.0ms, max retries 0
      === Move ===
      DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
      === MainDDARing ===
      Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
      === AuxDDARing ===
      Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
      === Heat ===
      Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
      === GCodes ===
      Segments left: 0
      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
      USB is ready with "M122" in state(s) 0
      Aux is idle in state(s) 0
      Trigger is idle in state(s) 0
      Queue is idle in state(s) 0
      LCD is idle in state(s) 0
      Daemon is idle in state(s) 0
      Autopause is idle in state(s) 0
      Code queue is empty.
      === Network ===
      Slowest loop: 0.22ms; fastest: 0.00ms
      Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
      HTTP sessions: 0 of 8
      - WiFi -
      Network state is starting2
      WiFi module is disabled
      Failed messages: pending 0, notready 1, noresp 0
      Socket states: 0 0 0 0 0 0 0 0
      ok
      
      

      Since wifi is noted as disabled I tried an "M552 S1" and got this message:

      M552 S1
      "Turn off the current WiFi mode before selecting a new one
      ok"
      

      I tried to redo the manipulations of the first connection tutorial but nothing works.

      I tried to make a M558 S "*" and I got the following message:

      M558 S"*"
      "Error: M588: Failed to reset the WiFi module to factory settings: another SPI transfer is pending"
      

      I tried all the manipulations I found in the different topics but nothing works.

      I'm lost.
      What can I do?

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

        Try sending these network commands

        M552 S-1
        M552 S0
        M552 S1
        M997 S1
        M588 S"*"
        M587  M587 S"ABC" P"password"
        

        Z-Bot CoreXY Build | Thingiverse Profile

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

          @tahi also try reflashing the WiFi firmware with 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

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

            @Phaedrux said in Duet 2 Wifi: wifi no longer works:

            M997 S1

            @droftarts it's in there 😉

            Z-Bot CoreXY Build | Thingiverse Profile

            1 Reply Last reply Reply Quote 1
            • tahiundefined
              tahi
              last edited by

              Hello and thank you for your answers.

              I tried the manipulations and here is the result:

              M552 S-1
              WiFi module stopped
              ok
              M552 S0
              ok
              M552 S1
              Turn off the current WiFi mode before selecting a new one
              ok
              M997 S1
              T0:-273.1 /0.0 B:-273.1 /0.0
              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
              
              

              I'm starting to wonder if the wifi module might be down.

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

                Yes I think that may be the case.

                Where did you purchase the Duet Wifi in January? If from an authorized reseller, please contact them and initiate a warranty exchange. Include a link to this forum thread as authorization.

                Z-Bot CoreXY Build | Thingiverse Profile

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