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

    Duet Wifi was working, but now won't connect to wifi

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    2
    3
    142
    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.
    • ZytaZiouZundefined
      ZytaZiouZ
      last edited by

      As the title says, I had this board setup and working great on firmware 3.0 and 3.1, but I updated to 3.1.1 and the printer sat for a bit waiting for a new fan, but when I went to test the new fan, the status lights were on but no wifi connection. Is my wifi module bad? If so is it possible to replace the module via soldering since my board is drastically out of warranty?

      What I've tried:
      The erase button and installing fresh 3.1.1 with freshly generated config.
      Erase and install 3.0.0
      Configuring wifi by gcode
      Checking it wasn't acting like it's own access point

      I can connect by USB, but what I get for the following commands:

      M115:
      FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.0 ELE
      CTRONICS: Duet WiFi 1.0 or 1.01 FIRMWARE_DATE: 2020-01-03b3

      M552:
      WiFi module is being started (never running, always started)

      M587
      Error: Failed to retrieve network list (With WIFI both on/off)

      M587 S"SSID" P"password"
      Error: Failed to add SSID to remembered list

      M122
      === Diagnostics ===
      RepRapFirmware for Duet 2 WiFi/Ethernet version 3.0 running on Duet WiFi 1.0 or
      1.01
      Board ID: 08DAM-999TL-MQ4S4-6J9F6-3S46L-TNHVY
      Used output buffers: 3 of 24 (13 max)
      === RTOS ===
      Static ram: 30516
      Dynamic ram: 91208 of which 12 recycled
      Exception stack ram used: 320
      Never used ram: 9016
      Tasks: NETWORK(ready,1888) HEAT(blocked,1240) MAIN(running,3736) IDLE(ready,156)
      Owned mutexes:
      === Platform ===
      Last reset 00:39:16 ago, cause: power up
      Last software reset time unknown, reason: Hard fault, spinning module GCodes, av
      ailable RAM 9152 bytes (slot 2)
      Software reset code 0x0063 HFSR 0x40000000 CFSR 0x00020000 ICSR 0x0041f003 BFAR
      0xe000ed38 SP 0x2001ff74 Task 0x5754454e
      Stack: 0044b753 0047bb90 6000000f 00000000 20003d50 e000ed04 00026d36 a5a5a5a5 0
      0451eaf 00000000 00000000 e000ed04 00455efd a5a5a5a5 200055dc a5a5a5a5 10000000
      e000ed04 20003d50 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5
      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 33.0, current 33.3, max 33.5
      Supply voltage: min 12.3, current 12.4, max 12.4, under voltage events: 0, over
      voltage events: 0, power good: yes
      Driver 0: standstill, SG min/max not available
      Driver 1: standstill, SG min/max not available
      Driver 2: standstill, SG min/max not available
      Driver 3: standstill, SG min/max not available
      Driver 4: standstill, SG min/max not available
      Date/time: 1970-01-01 00:00:00
      Cache data hit count 3080553735
      Slowest loop: 0.22ms; fastest: 0.11ms
      I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets
      0
      === Move ===
      Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
      Bed compensation in use: none, comp offset 0.000
      === MainDDARing ===
      Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0
      , 0
      === AuxDDARing ===
      Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0
      , 0
      === Heat ===
      Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
      Heater 1 is on, I-accum = 0.0
      === 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.22ms; fastest: 0.01ms
      Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(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
      1 Reply Last reply Reply Quote 0
      • Phaedruxundefined
        Phaedrux Moderator
        last edited by

        Can you try reinstalling the wifi server firmware 1.23?

        Also try to update to 3.1.1 again.

        Z-Bot CoreXY Build | Thingiverse Profile

        ZytaZiouZundefined 1 Reply Last reply Reply Quote 0
        • ZytaZiouZundefined
          ZytaZiouZ @Phaedrux
          last edited by

          @Phaedrux That fixed it! I didn't expect it to, since I thought the newest firmware files simply bundled both the main firmware and wifi firmware, but I am happy to report I was wrong.

          Thank you so much. I was dreading trying to figure out how to fix the board if the wifi was bad.

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