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

    Duet2 wifi stuck repeating Wifi Error.

    Scheduled Pinned Locked Moved Unsolved
    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 @rechrtb
      last edited by

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

      @zBeeble Nothing beyond turning on the debug messages for network and WiFi. If I'm correct, you turned off the network debug messages though since it was too noisy? Also, please make sure it's logging to file so we don't miss anything.

      Yeah... the networking was generating a line every so often ... printer on or not.

      But the machine is connected to the home server ... which is always on. I'm using minicom ... which is set to log all traffic

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

        I generally have at least 2 computers (so I expect that to be 4 connections from time-to-time)... go this just now:

        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
WiFi: /home/renz/Projects/Duet3D/WiFiSocketServerRTOS/src/Connection.cpp(578): refused conn on port 80 already 4 conns

        ... but can have as many as 3 or 4. Is this number tunable?

        This doesn't seem to be my problem, tho... as it should recover.

        droftartsundefined 1 Reply Last reply Reply Quote 0
        • droftartsundefined
          droftarts administrators @zBeeble
          last edited by droftarts

          @zBeeble From the https://docs.duet3d.com/en/User_manual/Troubleshooting/WiFi_troubleshooting page, two things that might be relevant:

          • In Duet Web Control, in the Settings > Machine specific > Communication section, check that "Maximum number of AJAX retries" is at least 3.

          • Is the connection stable when the printer is idle, but unreliable when printing? If so then there may be too few CPU cycles to service the network interface, because of an excessive step pulse rate.

            • Check the M122 report after a disconnection during a print, or after completing the print, and look at the number of 'hiccups' ('MaxReps' in old firmware versions) figure in the 'DDARing' or 'Move' section of the diagnostics.
            • This value should be kept below about 50. If it is higher, reduce either microstepping (M350) or maximum speed (M203).
            • Please note, hiccups and MaxReps is reset when you run M122 so only the value the first time you run M122 after a disconnection or completion of a print is significant.

          Edit: Sorry, the above is old info, and MaxReps isn't reported in the current firmware M122 report. I've asked @dc42 how this information is reported now.
          Edit: Updated the above with info from dc42.

          Ian

          Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : TronXY X5S with Duet 3 MB6HC and Roto toolboard

          1 Reply Last reply Reply Quote 0
          • rechrtbundefined
            rechrtb @zBeeble
            last edited by

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

            as generating a line every so often ... printer on or not.

            But the machine is connected to the home server ... which is always on. I'm using minicom ... which is set to log all traffic

            Reply

            Those "already 4 conns" should be normal, especially when there are multiple clients with the web interface open.

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

              So... been printing OK... for awhile. Just started acting up today again. Oddly, the serial output is "chunky" .... and incomplete. One recent query:

              m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.1 (2024-04-19 14:40:46) running on Duet WiFi 1.02 or later
Board ID: 08DDM-9FAM2-LW4SD-6J9F8-3SN6J-T3ZRY
Used output buffers: 1 of 26 (26 max)
=== RTOS ===
Static ram: 23256
Dynamic ram: 72928 of which 12 recycled
Never used RAM 13540, free system stack 110 words
Tasks: NETWORK(1,ready,15.7%,175) HEAT(3,nWait 5,0.1%,307) Move(4,nWait 5,2.9%,298) MAIN(1,running,81.3%,711) IDLE(0,ready,0.0%,
29), total 100.0%
Owned mutexes: WiFi(NETWORK) USB(MAIN)
=== Platform ===
Last reset 10:03:58 ago, cause: power up
Last software reset at 2024-07-29 10:46, reason: User, Gcodes spinning, available RAM 17140, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x04
Aux0 errors 0,0,0
MCU temperature: min 35.4, current 35.9, max 36.9
Supply voltage: min 11.0, current 12.2, max 12.3, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/6, heap memory allocated/used/recyclable 2048/932/816, gc cycles 1
Events: 0 queued, 0 completed
Driver 0: ok, SG min 0
Driver 1: ok, SG min 0
Driver 2: ok, SG min 0
Driver 3: ok, SG min 0
Driver 4: standstill, SG min n/a
Driver 5:
Driver 6:
Driver 7:
Driver 8:
Driver 9:
Driver 10:
Driver 11:
Date/time: 2024-07-30 01:04:58
Cache data hit count 4294967295
Slowest loop: 11.10ms; fastest: 0.20ms
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 1.5ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 23, maxWait 448ms, bed compensation in use: mesh, height map offset -0.031, max steps late 0, m
in interval 0, bad calcs 0, ebfmin 0.00, ebfmax 1.00
next step interrupt due in 20 ticks, disab
              1 Reply Last reply Reply Quote 0
              • 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