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

    Duet 2 WiFi | 3.2.2 to 3.3 Stuck

    Scheduled Pinned Locked Moved
    Firmware installation
    3
    11
    515
    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.
    • Phaedruxundefined
      Phaedrux Moderator @Jordan_Miller41
      last edited by Phaedrux

      @jordan_miller41 said in Duet 2 WiFi | 3.2.2 to 3.3 Stuck:

      The duet would no longer connect to my WiFi Network.

      Occasionally the wifi module firmware update will fail silently and the module won't work until the firmware is reapplied.

      Please try sending M997 S1 to reflash the wifi module.

      https://duet3d.dozuki.com/Wiki/FAQ#Section_Cannot_start_wifi_after_a_firmware_update

      Z-Bot CoreXY Build | Thingiverse Profile

      Jordan_Miller41undefined 1 Reply Last reply Reply Quote 0
      • daveman1010220undefined
        daveman1010220 @Jordan_Miller41
        last edited by

        @jordan_miller41 would you mind sharing your gcode configs? I have the same printer and it's completely broken after upgrading the firmware. I have fixed a lot of things but I currently am stuck with "no tools" configured/detected and I cannot figure out how to get past this.

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

          @daveman1010220 Probably a good idea to start a new thread with the details of your issue so we can help you out.

          Z-Bot CoreXY Build | Thingiverse Profile

          1 Reply Last reply Reply Quote 0
          • Jordan_Miller41undefined
            Jordan_Miller41 @Phaedrux
            last edited by

            @phaedrux Download and load 3.2.2 onto the SD card? Then send the M997 S1 command? Or do 3.3 and send command?

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

              The wifi firmware file should already be there either from 3.2.2 or 3.3, it doesn't matter at this point which. M997 S1 will try and use whichever version is present. Once it's flashed the module should start working again and then you can check what version is installed with M122 and update it if need be.

              Z-Bot CoreXY Build | Thingiverse Profile

              Jordan_Miller41undefined 1 Reply Last reply Reply Quote 0
              • Jordan_Miller41undefined
                Jordan_Miller41 @Phaedrux
                last edited by

                @phaedrux M122
                === Diagnostics ===
                RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02 or later
                Board ID: 08DGM-9T6BU-FG3SJ-6J9F2-3S06M-1AWHD
                Used output buffers: 3 of 24 (10 max)
                === RTOS ===
                Static ram: 23876
                Dynamic ram: 74876 of which 0 recycled
                Never used RAM 15664, free system stack 134 words
                Tasks: NETWORK(ready,19.9%,143) HEAT(delaying,0.0%,330) Move(notifyWait,0.1%,305) MAIN(running,78.6%,441) IDLE(ready,1.4%,29), total 100.0%
                Owned mutexes:
                === Platform ===
                Last reset 00:01:07 ago, cause: software
                Last software reset time unknown, reason: User, GCodes spinning, available RAM 15664, slot 0
                Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
                Error status: 0x08
                Aux0 errors 0,0,0
                Step timer max interval 0
                MCU temperature: min 23.0, current 24.1, max 24.3
                Supply voltage: min 13.5, current 13.6, max 13.9, under voltage events: 0, over voltage events: 0, power good: yes
                Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
                Driver 0: position 129859, standstill, SG min/max 0/377
                Driver 1: position 129859, standstill, SG min/max 0/1023
                Driver 2: position 129859, standstill, SG min/max 0/379
                Driver 3: position 0, standstill, SG min/max not available
                Driver 4: position 0, standstill, 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: 2021-08-09 18:47:50
                Cache data hit count 2612550386
                Slowest loop: 5.96ms; fastest: 0.17ms
                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 2.8ms, write time 0.0ms, max retries 0
                === Move ===
                DMs created 83, maxWait 41048ms, bed compensation in use: none, comp offset 0.000
                === MainDDARing ===
                Scheduled moves 8, completed moves 8, 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 idle 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: 1510.93ms; fastest: 0.00ms
                Responder states: HTTP(2) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
                HTTP sessions: 1 of 8

                • WiFi -
                  Network state is active
                  WiFi module is connected to access point
                  Failed messages: pending 0, notready 0, noresp 0
                  WiFi firmware version 1.25
                  WiFi MAC address ec:fa:bc:25:b8:32
                  WiFi Vcc 3.43, reset reason Turned on by main processor
                  WiFi flash size 4194304, free heap 24960
                  WiFi IP address 192.168.68.69
                  WiFi signal strength -51dBm, mode 802.11n, reconnections 0, sleep mode modem
                  Clock register 00002002
                  Socket states: 0 0 0 0 0 0 0 0

                Looks to be working now, thank you so much!

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

                  @jordan_miller41 said in Duet 2 WiFi | 3.2.2 to 3.3 Stuck:

                  WiFi firmware version 1.25

                  Looks like it used the previous wifi firmware from 3.2.2

                  To ensure you;ve got everything in the right place, upload this zip file once more to the system tab. It should update the wifi firmware this time to 1.26.

                  https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/Duet2and3Firmware-3.3.zip

                  Then you can remove all of the bin files from the system tab if you wish to tidy it up. All the firmware bin files are now located in the firmware folder. You can see them by clicking on the little drop down at the top of the file list, I think by default it says "system files" and you can click on it and choose "firmware files".

                  Z-Bot CoreXY Build | Thingiverse Profile

                  Jordan_Miller41undefined 1 Reply Last reply Reply Quote 1
                  • Jordan_Miller41undefined
                    Jordan_Miller41 @Phaedrux
                    last edited by

                    @phaedrux Ok, should I take the SD out and move this file into the /firmware folder I created?

                    3551cb80-451b-4c86-bb73-1000ff40dacb-image.png

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

                      More than that you can move all of the .bin files from the system folder into the firmware folder so that all the IAP files are there as well.

                      Z-Bot CoreXY Build | Thingiverse Profile

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

                        But if you still have access to dwc uploading that full zip file should do it already.

                        Can you check your DWC version to make sure it's 3.3?

                        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