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

    Duet WiFi web interface only half working

    Scheduled Pinned Locked Moved
    General Discussion
    5
    13
    1.1k
    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.
    • Danalundefined
      Danal
      last edited by

      Clearing cache, different browser, different device, all good advice.

      Reboot the router? Hmmm... must have some interesting proxying going on in that router. Or it doesn't like parallel TCP streams between local devices, or ...

      Certainly worth trying. I have had Duet not get on the network at all, until the router was rebooted. What a PITA.

      Delta / Kossel printer fanatic

      1 Reply Last reply Reply Quote 1
      • Danalundefined
        Danal
        last edited by Danal

        Also, when you upload new firmware via the web interface, it both uploads the files to the /sys directory and installs them into the flash memory on the board and/or wifi module by issuing separate M commands.

        If you've had trouble getting this to work, it is at least possible that your alternative methods (physical copy to the SD, etc, etc. ) got the files to /sys, but never loaded them to the board(s).

        As such, repeat the uploads via the web interface, or if that is too broken, look up the G-Code to actually install the firmware. Be sure the files on the SD /sys are correct, and issue those commands.

        Delta / Kossel printer fanatic

        niikundefined 1 Reply Last reply Reply Quote 1
        • niikundefined
          niik
          last edited by

          Thanks for the recommendation. I got momentary success but lost it again.

          I had previously cleared the cache but it didn't fix the issue, but I had not restarted my networking equipment. I had also previously removed and re-added the pairing in the access points web interface but that did not resolve the problem.

          Restarting the access point, router, and switch and also clearing cache fixed the problem. I'm not 100% sure what action resolved the issue this time since I did them all at the same time.

          I was able to connect to the page for a minute but then got another error "request timed out."

          List of actions.

          1. clear cache in Edge.
          2. restart network equipment
          3. restart duet
          4. connect to the webpage using edge
          5. everything working, uploaded gcode. FIXED!!
          6. try connecting using firefox (my main browser)
          7. page half loads (Img 1) in firefox, at the same time I get "request timed out" in Edge window (Img 2) BROKE!!
          8. close both browsers
          9. restart duet
          10. try connecting with Edge "page cant be reached"
          11. repeat steps 1-4
          12. "page cant be reached"

          Throughout all of this, I am watching ping and am getting responses when I should.

          We were so close.

          Img 1 ↓

          c727a0cd-2384-475d-bd79-4c90e398a091-image.png

          Img 2 ↓

          b5148d48-b276-48dc-b0e4-e01483c11edb-image.png

          Danalundefined 1 Reply Last reply Reply Quote 0
          • niikundefined
            niik @Danal
            last edited by niik

            @Danal said in Duet WiFi web interface only half working:

            Also, when you upload new firmware via the web interface, it both uploads the files to the /sys directory and installs them into the flash memory on the board and/or wifi module by issuing separate M commands.

            If you've had trouble getting this to work, it is at least possible that your alternative methods (physical copy to the SD, etc, etc. ) got the files to /sys, but never loaded them to the board(s).

            As such, repeat the uploads via the web interface, or if that is too broken, look up the G-Code to actually install the firmware. Be sure the files on the SD /sys are correct, and issue those commands.

            Thanks for the advice. I followed the guides and due to my own mistakes had to go as far as flashing a fresh firmware using USB and BOSSA since I accidentally delete everything. I am getting USB connection now and the board is reporting 2.04RC1, and webServer 1.23 with webControl 1.22.6 which is the firmware I was trying to install, so it seems like the process worked. However, the firmware upgrade mostly seems to have made the issue worse since originally I could connect fine just not upload but now I can't even connect.

            1 Reply Last reply Reply Quote 0
            • Danalundefined
              Danal @niik
              last edited by

              @niik said in Duet WiFi web interface only half working:

              Throughout all of this, I am watching ping and am getting responses when I should.

              This is absolutely key. Given that you can ping, the network is functioning correctly.

              So... even though we think it is all good... re-flash the Duet. Specifically:

              • Be sure the sys/Duet2CombinedFirmware and sys/DuetWiFiServer.bin files on the SD are the versions that you want. A fresh download won't hurt.

              • Issue M997 S0:1 and wait for it to complete!!

              • Power Cycle the Duet

              Delta / Kossel printer fanatic

              1 Reply Last reply Reply Quote 1
              • niikundefined
                niik
                last edited by

                After more troubleshooting, I have no idea...

                I tried updating the firmware using fallback procedure #1 (as @Danal recommended) and ran into some more issues, details below. I have also included another m122 result since I am now seeing errors in the console maybe the m122 will have more relevant info.

                Actions:

                1. downloaded firmware
                  Duet2CombinedFirmware.bin (from 2.04RC1)
                  DuetWiFiServer.bin (from 2.03)
                  iap4e.bin (from 2.03)
                2. loaded to SD card
                3. connected to board over USB using repetier
                4. sent M997 S0:1
                5. waited for completion (console counted to 100% then I listened for the USB device to disappear and reappear)
                  5)restarted
                6. pressed connect on Repetier → "Com port does not exist"
                7. try the other ports. still not working.
                8. check device manager → "Bossa port" showing instead of Duet
                9. decide to try another firmware version
                10. download Duet2CombinedFirmware.bin, DuetWiFiServer.bin, DuetWebControl.zip, iap4e.bin from version 1.21 and load them to the SD card
                11. loaded firmware using "BOSSA" app following fallback procedure #3
                12. connect to Duet over USB issue M997 S1 to load the WiFi server that matches the main.
                13. restart
                14. try to connect to webConsole → half loads. (img 3) and console reports Error: Can't open 0:/www/img/diabase_calibration_diagram.png.gz to read, error code 1
                  I get multiple of those errors depending on what is trying to load.
                15. remove SD And check that the files are on it. They are.
                16. delete and recreate the www folder and extract the WebControle files to it again
                17. put SD card back and try again. same issue

                Another observation is that after I try to connect to the webpage sometimes the Duet disconnects from USB and I drop like 2-3 pings, so it seems like it is getting reset.

                Full console log when trying to access the web page. ↓

                New conn on socket 0 for local port 80
                HTTP connection accepted
                Found responder
                Received 391 bytes
                Sending reply, file = yes
                HTTP req, command words { GET / HTTP/1.1 }, parameters { }
                New conn on socket 1 for local port 80
                HTTP connection accepted
                Found responder
                New conn on socket 2 for local port 80
                HTTP connection accepted
                Found responder
                Received 359 bytes
                Sending reply, file = yes
                HTTP req, command words { GET /css/dwc.css HTTP/1.1 }, parameters { }
                Received 412 bytes
                Sending reply, file = no
                HTTP req, command words { GET /img/diabase_calibration_diagram.png HTTP/1.1 }, parameters { }
                Error: Can't open 0:/www/img/diabase_calibration_diagram.png.gz to read, error code 5
                Error: Can't open 0:/www/img/diabase_calibration_diagram.png to read, error code 5
                Webserver: rejecting message with: 404 page not found
                New conn on socket 3 for local port 0
                HTTP connection accepted
                Found responder
                Received 342 bytes
                Sending reply, file = yes
                HTTP req, command words { GET /js/dwc.js HTTP/1.1 }, parameters { }
                New conn on socket 0 for local port 80
                HTTP connection accepted
                Found responder
                Received 355 bytes
                Sending reply, file = yes
                HTTP req, command words { GET /fonts/glyphicons.woff2 HTTP/1.1 }, parameters { }
                New conn on socket 0 for local port 80
                HTTP connection accepted
                Found responder
                Received 371 bytes
                Sending reply, file = yes
                HTTP req, command words { GET /css/bootstrap-theme.css HTTP/1.1 }, parameters { }
                New conn on socket 0 for local port 80
                HTTP connection accepted
                Found responder
                Received 414 bytes
                Sending reply, file = yes
                HTTP req, command words { GET /language.xml HTTP/1.1 }, parameters { }
                Error: Cannot read file.
                New conn on socket 0 for local port 80
                HTTP connection accepted
                Found responder
                Received 463 bytes
                Sending reply, file = no
                HTTP req, command words { GET /rr_connect HTTP/1.1 }, parameters { password=reprap time=2019-9-24T0:48:37 }
                New conn on socket 0 for local port 80
                HTTP connection accepted
                Found responder
                Received 442 bytes
                

                Img 3 ↓
                d5e340d5-f396-43de-be28-fb8b28ac8ce5-image.png

                serial: M122
                === Diagnostics ===
                Used output buffers: 1 of 32 (3 max)
                === Platform ===
                RepRapFirmware for Duet 2 WiFi/Ethernet version 1.21 running on Duet WiFi 1.0 or 1.01
                Board ID: 08DAM-999TL-MQ4SD-6J9FG-3S86R-T5AZZ
                Static ram used: 16152
                Dynamic ram used: 100400
                ReWiFi: Conn 0: free
                cycled dynamic ram: 2232
                Stack ram used: 3576 current, 4488 maximum
                Never used ram: 7800
                Last reset 00:34:18 ago, cause: power up
                Last software reset time unknown, reason: Stuck in spin loop, spinning module Platform, available RAM 11228 bytes (slot 2)
                SofWiFi: Conn 1: free
                tware reset code 0x4040 HFWiFi: Conn 2: free
                SR 0x00000000, CFSR 0x00000000, ICSR 0x0043380f, BFAR 0xe000ed38, SP 0x20001b5c
                Stack: 5754454e 00444ec3 004488dc 61000000 00000000 00000001 00448b11 20005494 00000001 20001774 10000000 00000001 20008c78 00006000 00000001 004451b5WiFi: Conn 3: free
                00000001 00000000 00000001 0041be93 0000000f 03b14fWiFi: Conn 4: free
                ff 00000000 0041cc01
                Error status: 1
                Free file entries: 10
                SD card 0 detected, interface speed: 20.0MBytes/sec
                SD card longest block write time: 0.0ms
                MCU temperature: min 25.7, current 35.9, max 36.7
                SupWiFi: Conn 5: free
                ply voltage: min 0.0, current 12.3, max 12.5, under voltage events: 0, over voWiFi: Conn 6: free
                ltage events: 0
                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,WiFi: Conn 7: free
                SG min/max not available
                Driver 4: standstill, SG min/max not available
                Date/time: 1970-01-01 00:00:00
                Slowest main loop (seconds): 0.053961; fastest: 0.000041
                === Move ===
                MaxReps: 6, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm 237, MaxWait: 18530WiFi:
                43626ms, Underruns: 0, 0
                Scheduled movWiFi: xmit: 0
                es: 3, completed moves: 3
                Bed compensation in use: mesh
                Bed probe heights: 0.000 0.000 0.000 0.000 0.000
                === Heat ===
                Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
                === GCodes ===
                Segments left: 0
                Stack records: 1 alWiFi: recv: 0
                located, 0 in use
                Movement lock held by null
                http is idle in state(s) 0
                teWiFi: fw: 0
                lnet 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
                autWiFi: drop: 0
                opause is idle in state(s) 0
                Code queue is empty.
                === Network ===
                Responder states: HTTP(0) HTTP(0) HTTP(0) HTTPWiFi: chkerr: 0
                (0) FTP(0) Telnet(0) Telnet(0)
                HTTP sessions: 0 of 8
                - WiFi -
                Network state is running
                WiFi module is connected to access point
                Failed messagesWiFi: lenerr: 0
                : pending 0, notready 0, noresp 0
                WiFi firmware version 1.21
                WiFi MAC address 5c:cf:7f:2c:25:13
                WiFi Vcc 3.39, reset reason Turned on by main processor
                WiFi flash size 4194304, free heap 16120
                WiFi IP address 192.168.1.181
                WiFi signal strength -47dBm, recoWiFi: memerr: 0
                nnections 0, sleep mode modem
                SoWiFi: rterr: 0
                cket states: 0 0 0 0 0 0 0 0
                === Expansion ===
                ok
                WiFi: proterr: 0
                WiFi: opterr: 0
                WiFi: err: 0
                WiFi: cachehit: 0
                WiFi:
                WiFi: xmit: 53
                WiFi: recv: 487
                WiFi: fw: 0
                WiFi: drop: 179
                WiFi: chkerr: 0
                WiFi: lenerr: 0
                WiFi: memerr: 0
                WiFi: rterr: 0
                WiFi: proterr: 179
                WiFi: opterr: 0
                WiFi: err: 0
                WiFi: cachehit: 1900
                WiFi:
                WiFi: xmit: 1968
                WiFi: recv: 5399
                WiFi: fw: 0
                WiFi: drop: 678
                WiFi: chkerr: 0
                WiFi: lenerr: 0
                WiFi: memerr: 0
                WiFi: rterr: 0
                WiFi: proterr: 0
                WiFi: opterr: 0
                WiFi: err: 0
                WiFi: cachehit: 0
                WiFi:
                WiFi: xmit: 24
                WiFi: recv: 0
                WiFi: drop: 0
                WiFi: chkerr: 0
                WiFi: lenerr: 0
                WiFi: memerr: 0
                
                Danalundefined 1 Reply Last reply Reply Quote 0
                • Danalundefined
                  Danal @niik
                  last edited by Danal

                  @niik said in Duet WiFi web interface only half working:

                  1. restart
                  2. try to connect to webConsole → half loads. (img 3) and console reports Error: Can't open 0:/www/img/diabase_calibration_diagram.png.gz to read, error code 1
                    I get multiple of those errors depending on what is trying to load.

                  That is really odd. There is no such file in a Duet's /www directory as distributed. In fact, there is no such directory as /www/img. DWC does not use images (png).
                  (It does use a favicon.ico.gz file, but no other images).

                  I do see that the functions that are built into DWC to automatically put various files in their correct directory, by file extension, WILL build a /www/img directory and put any .png, .jpg, or .jpeg files there. So, at some point in the past, some files with those extensions got uploaded.

                  My advice at this point:

                  First, try to fix the www directory:

                  • Put the SD in your PC and delete /www (and everything under it). Back it up first, if you wish.

                  • Download DuetWebControl-Duet2.zip This is R2.0.0-RC7, which should work fine with the firmware you've loaded. If you want another release, see here

                  • Unzip it into a new, empty /www on the SD. After the unzip, the directory should look like:
                    css (dir)
                    fonts (dir)
                    js (dir)
                    index.html.gz
                    favicon.ico.gz
                    ... and maybe one or two other files, but NO 'img' directory!

                  • Put that in the printer and see what you get.

                  If (and only if) that does not work, build a physically new SD. Be sure and start by formatting the new SD as a "FAT32", and be sure and UNcheck "quick format". Then copy stuff over. Including the newly built www directory.

                  Delta / Kossel printer fanatic

                  niikundefined 1 Reply Last reply Reply Quote 1
                  • Shaunundefined
                    Shaun
                    last edited by

                    I had the exact same. so this is what i had to do to fix this.

                    Check your wifi security on your router. duet doesnt seem to like multi mode authentication. Set your router to WPA2-PSK and your problem should be resolved. It wont drop off and the browser will work fine.

                    1 Reply Last reply Reply Quote 0
                    • niikundefined
                      niik @Danal
                      last edited by niik

                      Test 1
                      @Danal said in Duet WiFi web interface only half working:

                      First, try to fix the www directory:

                      • Put the SD in your PC and delete /www (and everything under it). Back it up first, if you wish.

                      • Download DuetWebControl-Duet2.zip This is R2.0.0-RC7, which should work fine with the firmware you've loaded. If you want another release, see here

                      • Unzip it into a new, empty /www on the SD. After the unzip, the directory should look like:
                        css (dir)
                        fonts (dir)
                        js (dir)
                        index.html.gz
                        favicon.ico.gz
                        ... and maybe one or two other files, but NO 'img' directory!

                      • Put that in the printer and see what you get.

                      8d200ddb-0cfc-49ec-92d7-c2b8af701c7e-image.png

                      Results:
                      Webpage loaded a 404 error and console also reported an error

                      New conn on socket 0 for local port 80
                      HTTP connection accepted
                      Found responder
                      Received 391 bytes
                      Sending reply, file = no
                      HTTP req, command words { GET / HTTP/1.1 }, parameters { }
                      Error: Can't open 0:/www/reprap.htm.gz to read, error code 4
                      Error: Can't open 0:/www/reprap.htm to read, error code 4
                      Error: Can't open 0:/www/html404.htm to read, error code 4
                      Webserver: rejecting message with: 404 page not found
                      

                      This result makes me think the WebControle and webServer versions I am using are not compatible.

                      Also, the M122 console output looks odd

                      12:32:18.716 : WiFi firmware versiWiFi: lenerr: 0
                      12:32:18.716 : on 1.21
                      

                      Test 2:
                      Migrate back to the 2.04RC1 and webServer 1.23 but keep using webControl 2.0.0-RC7

                      loaded relevant .bin files to the SD and installed using fallback procedure #1 steps

                      Results:

                      The page starts to load but gets stuck. I no longer get any errors in the console when trying to access the web console.

                      Verified firmware update

                      === Diagnostics ===
                      RepRapFirmware for Duet 2 WiFi/Ethernet version 2.04RC1 running on Duet WiFi 1.0 or 1.01
                      Board ID: 08DAM-999TL-MQ4SD-6J9FG-3S86R-T5AZZ
                      Used output buffers: 1 of 24 (2 max)
                      ....
                      - WiFi -
                      Network state is running
                      WiFi module is connected to access point
                      Failed messages: pending 0, notready 0, noresp 0
                      WiFi firmware version 1.23
                      

                      Never gets past this page.
                      page loading result from test 2

                      Test 3:
                      @Danal said in Duet WiFi web interface only half working:

                      If (and only if) that does not work, build a physically new SD. Be sure and start by formatting the new SD as a "FAT32", and be sure and UNcheck "quick format". Then copy stuff over. Including the newly built www directory.

                      Formated another SD card using SDformatter.exe with settings FULL(overWrite) FORMAT, SIZE ADJUSTMENT ON. The card was previously used in a Pi so I could not format it with windows until the Linux partitions were removed.

                      Confirmed FAT32 file system

                      Copied all files from SD1 to SD2.

                      Results: FIXED!!!

                      Page loaded and connected to the printer. I uploaded a file a ran a test print.

                      Couple small errors

                      • M141: not chamber heater has been configured for slot 0
                      • Failed to get file list - directory 0:/filaments not found

                      I think these are relatively self-explanatory errors and I can work through them.

                      Summery

                      After all the stuff I think I have an idea about how everything happened.

                      1. I had a network issue that caused my original upload problems.
                        1.1. Updating the firmware was probably not necessary
                      2. My first and second SD cards were bad leading to unexpected and unpredictable results.
                        2.1. SD1 has been in since I got the board so could have worn out.
                        2.2. SD2 is an almost new card that was used for pictures like once. So must have been defective or the format I ran on it when I first set it up completed with unknown errors.
                      3. SD3 was a card I had in a Pi and it seems to have fixed the issues I was having.
                      Danalundefined 1 Reply Last reply Reply Quote 0
                      • droftartsundefined
                        droftarts administrators
                        last edited by

                        SD card specification for Duet is here: https://duet3d.dozuki.com/Wiki/SD_Card
                        (I've just updated the bit about formatting, and size limit)
                        For M141 error (it's Cura) see: https://forum.duet3d.com/topic/11546/cura-4-2-1-to-duet2wifi-plugin-problem
                        You need to create a filaments folder on the SD card.

                        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
                        • Danalundefined
                          Danal @niik
                          last edited by

                          @niik said in Duet WiFi web interface only half working:

                          Results: FIXED!!!

                          YAY!!

                          Delta / Kossel printer fanatic

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