Duet3D Logo

    Duet3D

    • Register
    • Login
    • Search
    • Categories
    • Tags
    • Documentation
    • Order

    DuetWifiServer upgrade freezes

    Firmware installation
    2
    8
    122
    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.
    • ctilley79
      ctilley79 last edited by

      Upgrading the wifi server within DWC causes the board to go unresponsive. After uploading the file, DWC prompts you to install the server, however the process never completes. You have to serial into the board and install the wifi server manually using M997 S1. Am I missing the proper procedure?

      1 Reply Last reply Reply Quote 0
      • ctilley79
        ctilley79 last edited by

        This is happened on all 3.2 betas as well as the final release.

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

          I've noticed this as well during some upgrades from 3.0 to 3.1.1. It's not known exactly why but the server firmware appears to complete successfully but has not or has been corrupted. Reflashing with M997 S1 usually corrects it first try, however that is annoying to have to use USB terminal to do so.

          Z-Bot CoreXY Build | Thingiverse Profile

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

            @ctilley79 said in DuetWifiServer upgrade freezes:

            This is happened on all 3.2 betas as well as the final release.

            Are you saying that every time you update via DWC it does this?

            Can you provide the results of M122?

            Z-Bot CoreXY Build | Thingiverse Profile

            ctilley79 1 Reply Last reply Reply Quote 0
            • ctilley79
              ctilley79 last edited by

              Yes. The issue happened when I upgraded the wifi server to 1.25 beta and 1.25 final via DWC. Happened when I was on the initial 3.2 betas(both DWC and RRF) and when I attempted to upgrade to wifi server 1.25 final after having already upgraded DWC and RRF to 3.2 final. My Kiwi friend Ray also had the same issue. If I can pull him away from his sheep, I may be able to get him to comment on this thread.

              M122
              === Diagnostics ===
              RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2 running on Duet WiFi 1.02 or later
              Board ID: 08DGM-956GU-DJMSN-6JKFD-3SD6M-1URHG
              Used output buffers: 3 of 24 (24 max)
              === RTOS ===
              Static ram: 23460
              Dynamic ram: 73552 of which 60 recycled
              Never used RAM 15008, free system stack 99 words
              Tasks: NETWORK(ready,157) HEAT(blocked,309) MAIN(running,378) IDLE(ready,19)
              Owned mutexes: WiFi(NETWORK)
              === Platform ===
              Last reset 21:04:37 ago, cause: software
              Last software reset at 2021-01-05 13:39, reason: User, GCodes spinning, available RAM 15284, slot 1
              Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
              Error status: 0x0c
              Aux0 errors 0,0,0
              MCU temperature: min 43.8, current 67.7, max 70.6
              Supply voltage: min 24.1, current 24.5, max 24.8, under voltage events: 0, over voltage events: 0, power good: yes
              Driver 0: position 32259, ok, SG min/max 0/267
              Driver 1: position 19453, standstill, SG min/max 0/300
              Driver 2: position 491, standstill, SG min/max 0/94
              Driver 3: position 0, ok, SG min/max 0/1023
              Driver 4: position 0, standstill, SG min/max 0/93
              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-01-06 10:44:06
              Cache data hit count 4294967295
              Slowest loop: 274.21ms; fastest: 0.11ms
              I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
              === Storage ===
              Free file entries: 9
              SD card 0 detected, interface speed: 20.0MBytes/sec
              SD card longest read time 2.0ms, write time 77.1ms, max retries 0
              === Move ===
              DMs created 83, maxWait 41231368ms, bed compensation in use: mesh, comp offset 0.000
              === MainDDARing ===
              Scheduled moves 40194, completed moves 40155, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 9], CDDA state 3
              === 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
              Heater 0 is on, I-accum = 0.5
              Heater 1 is on, I-accum = 0.3
              === GCodes ===
              Segments left: 1
              Movement lock held by null
              HTTP is idle in state(s) 0
              Telnet is idle in state(s) 0
              File is doing "G1 X142.231 Y111.471 E0.04183" 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: 269.05ms; fastest: 0.00ms
              Responder states: HTTP(0) 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 5c:cf:7f:76:60:cf
              WiFi Vcc 3.42, reset reason Power up
              WiFi flash size 4194304, free heap 24376
              WiFi IP address 192.168.1.85
              WiFi signal strength -41dBm, mode 802.11n, reconnections 0, sleep mode modem
              Clock register 00002002
              Socket states: 0 0 0 0 0 0 0 0
              
              Phaedrux 1 Reply Last reply Reply Quote 0
              • ctilley79
                ctilley79 @Phaedrux last edited by

                @Phaedrux Not sure why replying didn't tag you. requested info is above

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

                  @ctilley79 said in DuetWifiServer upgrade freezes:

                  MCU temperature: min 43.8, current 67.7, max 70.6

                  Are those temps correct?!

                  Can you try calibrating your CPU temp to see how far off those numbers may be?

                  https://duet3d.dozuki.com/Wiki/Calibrating_the_CPU_temperature

                  Even so that seems very very high. I don't know if heat has anything to do with your issues, but it might. Unfortunately for the wifi server flash issue there isn't much to be done about it at the moment. Apparently the module doesn't allow for CRC checks on the uploads of the firmware bin, so it's basically impossible to detect a bad upload. Future versions may try to force a lower baud rate on the flash upload to reduce chance of errors.

                  Z-Bot CoreXY Build | Thingiverse Profile

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

                    @Phaedrux That's because it was mid print, inside a 45C enclosure when I ran the M122 command for you. When I upgraded the wifi server, everything was cold running at a normal 37C or so. Cold or hot, upgrading wifi module firmware via DWC hangs. The file uploads fine when uploading via DWC. After upload, DWC prompts you if you want to install the uploaded firmware. That's when it hangs. After it fails, I reset the machine and then serial into the device. When you serial into the device, M997 S1 just bangs right along succeeding after 30 seconds.

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