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

    Unsolved Duet2 wifi stuck repeating Wifi Error.

    Duet Hardware and wiring
    6
    65
    1.6k
    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.
    • zBeebleundefined
      zBeeble
      last edited by

      Notably, on one output not shown, "slowest loop" was around 146ms.

      1 Reply Last reply Reply Quote 0
      • zBeebleundefined
        zBeeble
        last edited by

        I've turned on the debugging for 14 and 1 (wifi and network). Lots of chatter, but the printer is definitely acting up. The serial is no longer chunky, but at one point, I disconnected the serial ... which would reset the driver on the server.... and probably the duet, too.

        m111 and chatter look like:

        Debugging enabled for modules: Network(1 - 0xffffffff) WiFi(14 - 0xffffffff)
Debugging disabled for modules: Platform(0) Webserver(2) Gcodes(3) Move(4) Heat(5) Kinematics(6) InputShaping(7) unused(8) Print
Monitor(9) Storage(10) PortControl(11) DuetExpansion(12) FilamentSensors(13) Display(15) SbcInterface(16) CAN(17) Expansion(18)
New conn on socket 0 for local port 80
Found responder
Received 367 bytes
New conn on socket 1 for local port 80
Found responder
Received 329 bytes
New conn on socket 0 for local port 80
Found responder
New conn on socket 1 for local port 80
Found responder
Received 329 bytes
Received 367 bytes
New conn on socket 0 for local port 80
        1 Reply Last reply Reply Quote 0
        • Phaedruxundefined Phaedrux marked this topic as a question
        • Phaedruxundefined
          Phaedrux Moderator
          last edited by

          Have you tried updating to 3.5.2 yet? Or the 3.6 alpha release? I think the beta is upcoming as well.

          Z-Bot CoreXY Build | Thingiverse Profile

          zBeebleundefined 1 Reply Last reply Reply Quote 0
          • zBeebleundefined
            zBeeble
            last edited by

            The printer was idle, so I shut off the constant network chatter. wifi debug was still on (as it's fairly quiet). During the idle day, it said this:

            Debugging enabled for modules: WiFi(14 - 0xffffffff)
Debugging disabled for modules: Platform(0) Network(1) Webserver(2) Gcodes(3) Move(4) Heat(5) Kinematics(6) InputShaping(7) unus
ed(8) PrintMonitor(9) Storage(10) PortControl(11) DuetExpansion(12) FilamentSensors(13) Display(15) SbcInterface(16) CAN(17) Exp
ansion(18)
WiFi: /home/renz/Projects/Duet3D/WiFiSocketServerRTOS/src/Connection.cpp(578): refused conn on port 80 already 4 conns
WiFi: /home/renz/Projects/Duet3D/WiFiSocketServerRTOS/src/Connection.cpp(578): refused conn on port 80 already 4 conns

            Now.... 2 computers look at the web server and the web server is on an RFC 1918 address behind NAT ... so not general internet exposed.

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

              @Phaedrux said in Duet2 wifi stuck repeating Wifi Error.:

              Have you tried updating to 3.5.2 yet? Or the 3.6 alpha release? I think the beta is upcoming as well.

              I'm a little bit upgrade adverse ... you can convince me, but equally, I don't believe this is upgrade related.

              1 Reply Last reply Reply Quote 0
              • zBeebleundefined
                zBeeble
                last edited by

                OOB ... looking at your debug message ... you could probably significantly cut binary size by cutting /home/renz/Projects from the path of all debug messages --- ie: cut to the root of the project.

                1 Reply Last reply Reply Quote 0
                • zBeebleundefined
                  zBeeble
                  last edited by

                  OK. Now it's full-on inaccessible.

                  Lots of these lines scrolling on the console.

                  ResponseTimeout, pending=1
ResponseTimeout, pending=1
ResponseTimeout, pending=1
WiFi: /home/renz/Projects/Duet3D/WiFiSocketServerRTOS/src/Connection.cpp(578): refused conn on port 80 already 4 conns
ResponseTimeout, pending=1
WiFi: /home/renz/Projects/Duet3D/WiFiSocketServerRTOS/src/Connection.cpp(578): refused conn on port 80 already 4 conns
ResponseTimeout, pending=1
WiFi: /home/renz/Projects/Duet3D/WiFiSocketServerRTOS/src/Connection.cpp(578): refused conn on port 80 already 4 conns
                  1 Reply Last reply Reply Quote 0
                  • zBeebleundefined
                    zBeeble
                    last edited by

                    And just to be clear, two local computers are pointing at it and no network traffic (as expected) is coming from the router for it.

                    1 Reply Last reply Reply Quote 0
                    • zBeebleundefined
                      zBeeble
                      last edited by

                      This is the log from the first few glitches above (posted here) through starting a new print and then it glitching hard:

                      Debugging enabled for modules: WiFi(14 - 0xffffffff)
Debugging disabled for modules: Platform(0) Network(1) Webserver(2) Gcodes(3) Move(4) Heat(5) Kinematics(6) InputShaping(7) unus
ed(8) PrintMonitor(9) Storage(10) PortControl(11) DuetExpansion(12) FilamentSensors(13) Display(15) SbcInterface(16) CAN(17) Exp
ansion(18)
WiFi: /home/renz/Projects/Duet3D/WiFiSocketServerRTOS/src/Connection.cpp(578): refused conn on port 80 already 4 conns
WiFi: /home/renz/Projects/Duet3D/WiFiSocketServerRTOS/src/Connection.cpp(578): refused conn on port 80 already 4 conns
Done printing file
Finished printing file 0:/gcodes/CFFFP_DeckStand_Anker.gcode, print time was 13h 4m
ResponseTimeout, pending=1
ResponseBusy
ResponseBusy
ResponseBusy
ResponseBusy
ResponseBusy
ResponseBusy
ResponseBusy
ResponseBusy
ResponseBusy
ResponseBusy
ResponseBusy
ResponseBusy
ResponseBusy
ResponseBusy
ResponseBusy
ResponseBusy
ResponseBusy
ResponseBusy
ResponseBusy
ResponseBusy
ResponseTimeout, pending=1
ResponseTimeout, pending=1
ResponseTimeout, pending=1
ResponseTimeout, pending=1
ResponseTimeout, pending=1
ResponseTimeout, pending=1
ResponseTimeout, pending=1
ResponseTimeout, pending=1
ResponseTimeout, pending=1
ResponseTimeout, pending=1
ResponseTimeout, pending=1
ResponseTimeout, pending=1
ResponseTimeout, pending=1
ResponseTimeout, pending=1
ResponseTimeout, pending=1
ResponseTimeout, pending=1
ResponseTimeout, pending=1
ResponseTimeout, pending=1
ResponseTimeout, pending=1
ResponseTimeout, pending=1
ResponseTimeout, pending=1
ResponseTimeout, pending=1
ResponseTimeout, pending=1
ResponseTimeout, pending=1
ResponseTimeout, pending=1
ResponseTimeout, pending=1
ResponseTimeout, pending=1
ResponseTimeout, pending=1
ResponseTimeout, pending=1
ResponseTimeout, pending=1
ResponseTimeout, pending=1
ResponseTimeout, pending=1
ResponseTimeout, pending=1
ResponseTimeout, pending=1
ResponseTimeout, pending=1
ResponseTimeout, pending=1
WiFi: /home/renz/Projects/Duet3D/WiFiSocketServerRTOS/src/Connection.cpp(578): refused conn on port 80 already 4 conns
ResponseTimeout, pending=1
WiFi: /home/renz/Projects/Duet3D/WiFiSocketServerRTOS/src/Connection.cpp(578): refused conn on port 80 already 4 conns
ResponseTimeout, pending=1
WiFi: /home/renz/Projects/Duet3D/WiFiSocketServerRTOS/src/Connection.cpp(578): refused conn on port 80 already 4 conns
ResponseTimeout, pending=1
WiFi: /home/renz/Projects/Duet3D/WiFiSocketServerRTOS/src/Connection.cpp(578): refused conn on port 80 already 4 conns
ResponseTimeout, pending=1
                      1 Reply Last reply Reply Quote 0
                      • zBeebleundefined
                        zBeeble
                        last edited by

                        I delivered m111 p1 s1, and this is the changed repeating output:

                        WiFi: /home/renz/Projects/Duet3D/WiFiSocketServerRTOS/src/Connection.cpp(578): refused conn on port 80 already 4 conns
1ResponseTimeout, pending=1
WiFi: /home/renz/Projects/Duet3D/WiFiSocketServerRTOS/src/Con^?/renz/Projects/Duet3D/WiFiSocketServerRTOS/src/Connection.cpp(578
): refused conn on port 80 already 4 conns
ResponseTimeout, pending=1
WiFi: /hom^?s/Duet3D/WiFiSocketServerRTOS/src/Connection.cpp(578): refused conn on port 80 already 4 conns
ResponseTimeout, pending=1
ResponseTimeout, pending=1
ResponseTimeout, pending=1

Debugging enabled for modules: Network(1 - 0xffffffff) WiFi(14 - 0xffffffff)
Debugging disabled for modules: Platform(0) Webserver(2) Gcodes(3) Move(4) Heat(5) Kinematics(6) InputShaping(7) unused(8) Print
Monitor(9) Storage(10) PortControl(11) DuetExpansion(12) FilamentSensors(13) Display(15) SbcInterface(16) CAN(17) Expansion(18)
ResponseTimeout, pending=1
Bad recv status size
ResponseTimeout, pending=1
Bad recv status size
ResponseTimeout, pending=1
Bad recv status size
ResponseTimeout, pending=1
Bad recv status size
ResponseTimeout, pending=1
Bad recv status size
WiFi: /home/renz/Projec^?/home/renz/Projects/Duet3D/WiFiSocketServerRTOS/src/Connection.cpp(578): refused conn on port 80 already 4 conns
ResponseTimeout, pending=1
Bad recv status size
WiFi: /home/renz/Projects/Duet3D/WiFiSocketServerRTOS/src/Connection.cpp(578): refused conn on port 80 already 4 conns
ResponseTimeout, pending=1
Bad recv status size
WiFi: /home/renz/Projects/Duet3D/WiFiSocketServerRTOS/src/Connection.cpp(578): refused conn on port 80 already 4 conns
ResponseTimeout, pending=1
Bad recv status size
WiFi: /home/renz/Projects/Duet3D/WiFiSocketServerRTOS/src/Connection.cpp(578): refused conn on port 80 already 4 conns
ResponseTimeout, pending=1
Bad recv status size
WiFi: /home/renz/Projects/Duet3D/WiFiSocketServerRTOS/src/Connection.cpp(578): refused conn on port 80 already 4 conns
ResponseTimeout, pending=1
Bad recv status size
WiFi: /home/renz/Projects/Duet3D/WiFiSocketServerRTOS/src/Con^?uet3D/WiFiSocketServerRTOS/src/Connection.cpp(578): refused conn on port 80 already 4 conns
ResponseTimeout, pending=1
Bad recv status size
WiFi: /home/renz/Projects/^?t 80 already 4 conns
ResponseTimeout, pending=1
Bad recv status size
WiFi: /home/renz/Projects/Duet3D/WiFiSocketServerRTOS/src/Connection.cpp(578): refused conn on po^?/Connection.cpp(578): refused conn on port 80 already 4 conns
ResponseTimeout, pending=1
Bad recv status size
ResponseTimeout, pending=1
Bad recv status size
                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post
                        Unless otherwise noted, all forum content is licensed under CC-BY-SA