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

    Network problem (noresp 1....8)

    Scheduled Pinned Locked Moved Unsolved
    Beta Firmware
    2
    7
    332
    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.
    • SIamundefined
      SIam
      last edited by

      Hi,
      I'm not sure if this is coincidence, since i'm running the WiFi/Ethernet 3.3RC2+3 (2021-05-19) and von Duet WiFi Server: 1.26 i have the Problem that the network after some hours not works anymore.
      I can't Access duet and ping works not too. When i disconet the Duet from mains i can see That the connection to the router will disconected too, when i now reconnect the duet to mains the connection to the router will etablished again. But i can't connect to it over web,telnet, ftp or ping.
      In the next test i connected my pc to the USB Port of the duet and i can see that the wifi seems to work. here the Result of M122

      m122
      <CR>
      === Diagnostics ===
      RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3RC2 (2021-05-11 14:55:01) running on Duet WiFi 1.02 or later + DueX5
      Board ID: 08DGM-95BNL-MGPSJ-6J9FD-3SJ6N-K1W3Y
      Used output buffers: 1 of 24 (14 max)
      === RTOS ===
      Static ram: 23876
      Dynamic ram: 78184 of which 12 recycled
      Never used RAM 12344, free system stack 184 words
      Tasks: NETWORK(ready,12.1%,396) ACCEL(notifyWait,0.0%,334) HEAT(delaying,0.0%,330) Move(notifyWait,0.1%,340) DUEX(notifyWait,0.0%,24) MAIN(running,87.8%,413) IDLE(ready,0.0%,29), total 100.0%
      Owned mutexes: WiFi(NETWORK) USB(MAIN)
      === Platform ===
      Last reset 00:03:23 ago, cause: power up
      Last software reset time unknown, reason: User, GCodes spinning, available RAM 12372, slot 0
      Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
      Error status: 0x00
      Aux0 errors 0,0,0
      Step timer max interval 0
      MCU temperature: min 29.1, current 29.7, max 30.1
      Supply voltage: min 0.4, current 0.5, max 0.6, under voltage events: 0, over voltage events: 0, power good: no
      Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
      Driver 0: position 0, ok, SG min/max not available
      Driver 1: position 0, ok, SG min/max not available
      Driver 2: position 0, ok, SG min/max not available
      Driver 3: position 0, ok, SG min/max not available
      Driver 4: position 0, ok, SG min/max not available
      Driver 5: position 0, ok, SG min/max not available
      Driver 6: position 0, ok, SG min/max not available
      Driver 7: position 0, ok, SG min/max not available
      Driver 8: position 0, ok, SG min/max not available
      Driver 9: position 0, ok, SG min/max not available
      Driver 10: position 0
      Driver 11: position 0
      Date/time: 1970-01-01 00:00:00
      Cache data hit count 4294967295
      Slowest loop: 10.24ms; fastest: 0.14ms
      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 0.9ms, write time 0.0ms, max retries 0
      === Move ===
      DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
      === MainDDARing ===
      Scheduled moves 0, completed moves 0, 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
      Heater 1 is on, I-accum = 0.0
      === 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 ready with "m122" 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.
      === Filament sensors ===
      Extruder 0 sensor: ok
      === DueX ===
      Read count 0, 0.00 reads/min
      === Network ===
      Slowest loop: 199.86ms; fastest: 0.07ms
      Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
      HTTP sessions: 0 of 8
      - WiFi -
      Network state is active
      WiFi module is connected to access point 
      Failed messages: pending 0, notready 0, noresp 1
      WiFi firmware version 1.26
      WiFi MAC address 2c:3a:e8:0b:06:33
      WiFi Vcc 3.44, reset reason Turned on by main processor
      WiFi flash size 4194304, free heap 24624
      WiFi IP address 192.168.188.36
      WiFi signal strength -50dBm, mode 802.11n, reconnections 0, sleep mode modem
      Clock register 00002002
      Socket states: 0 0 0 0 0 0 0 0
      ok
      

      The only thing i can see is that the noresp counter increases with each m122 Call

      m122
      === Diagnostics ===
      RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3RC2 (2021-05-11 14:55:01) running on Duet WiFi 1.02 or later + DueX5
      Board ID: 08DGM-95BNL-MGPSJ-6J9FD-3SJ6N-K1W3Y
      Used output buffers: 1 of 24 (14 max)
      === RTOS ===
      Static ram: 23876
      Dynamic ram: 78184 of which 12 recycled
      Never used RAM 12344, free system stack 184 words
      Tasks: NETWORK(ready,10.7%,396) ACCEL(notifyWait,0.0%,334) HEAT(delaying,0.0%,330) Move(notifyWait,0.1%,340) DUEX(notifyWait,0.0%,24) MAIN(running,89.2%,413) IDLE(ready,0.0%,29), total 100.0%
      Owned mutexes: WiFi(NETWORK) USB(MAIN)
      === Platform ===
      Last reset 00:06:08 ago, cause: power up
      Last software reset time unknown, reason: User, GCodes spinning, available RAM 12372, slot 0
      Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
      Error status: 0x00
      Aux0 errors 0,0,0
      Step timer max interval 0
      MCU temperature: min 28.8, current 29.4, max 29.7
      Supply voltage: min 0.5, current 0.5, max 0.5, under voltage events: 0, over voltage events: 0, power good: no
      Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
      Driver 0: position 0, ok, SG min/max not available
      Driver 1: position 0, ok, SG min/max not available
      Driver 2: position 0, ok, SG min/max not available
      Driver 3: position 0, ok, SG min/max not available
      Driver 4: position 0, ok, SG min/max not available
      Driver 5: position 0, ok, SG min/max not available
      Driver 6: position 0, ok, SG min/max not available
      Driver 7: position 0, ok, SG min/max not available
      Driver 8: position 0, ok, SG min/max not available
      Driver 9: position 0, ok, SG min/max not available
      Driver 10: position 0
      Driver 11: position 0
      Date/time: 1970-01-01 00:00:00
      Cache data hit count 4294967295
      Slowest loop: 0.24ms; fastest: 0.14ms
      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 0.0ms, write time 0.0ms, max retries 0
      === Move ===
      DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
      === MainDDARing ===
      Scheduled moves 0, completed moves 0, 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
      Heater 1 is on, I-accum = 0.0
      === 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 ready with "m122" 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.
      === Filament sensors ===
      Extruder 0 sensor: ok
      === DueX ===
      Read count 0, 0.00 reads/min
      === Network ===
      Slowest loop: 199.71ms; fastest: 0.08ms
      Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
      HTTP sessions: 0 of 8
      - WiFi -
      Network state is active
      WiFi module is connected to access point 
      Failed messages: pending 0, notready 0, noresp 4
      WiFi firmware version 1.26
      WiFi MAC address 2c:3a:e8:0b:06:33
      WiFi Vcc 3.44, reset reason Turned on by main processor
      WiFi flash size 4194304, free heap 24624
      WiFi IP address 192.168.188.36
      WiFi signal strength -49dBm, mode 802.11n, reconnections 0, sleep mode modem
      Clock register 00002002
      Socket states: 0 0 0 0 0 0 0 0
      ok
      

      The only thing i can do to get the duet back to work is to reset the Duet connection in the router. This problem i had this week two times and the only change was the latest Duet Update. The duet is connected to AVM Fritzbox 7590 and i Use round about 25 -30 esp8266 WiFi Boards for my (own developed) Smarthome this Modules have no issues.

      Now the question is is there something dieing or was there a change in the wifi Software?

      greets

      Andy

      Hypercube-Evolution-Hybrid, Piezo Orion, Orbiter
      Duet WiFi 1.02 or later + DueX5
      RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.0beta4 (2021-09-27 11:30:36)
      Duet WiFi Server: 1.26
      Duet Web Control 3.4.0beta4 (2021-09-27)

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

        Can you verify that going back to 3.2.2 and 1.25 resolves the problem?

        Z-Bot CoreXY Build | Thingiverse Profile

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

          @phaedrux i was today trying to reconstruct this issue (the two times as this issue arose was the printer a long time in Idle) but today nothing happens... I can try to go back to rff 3.2.2 and look what will happens then.

          Hypercube-Evolution-Hybrid, Piezo Orion, Orbiter
          Duet WiFi 1.02 or later + DueX5
          RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.0beta4 (2021-09-27 11:30:36)
          Duet WiFi Server: 1.26
          Duet Web Control 3.4.0beta4 (2021-09-27)

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

            Thanks. It would be helpful to know if this issue is for sure related to the wifi server firmware 1.26 before 3.3 goes final in the coming days. No other reported issues thus far though.

            Z-Bot CoreXY Build | Thingiverse Profile

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

              @phaedrux at the moment it works without any issue with 3.2.2 but take a look at this https://forum.duet3d.com/topic/23397/no-wifi-this-morning here it can maybe the same issue?

              ....
              WiFi -
              Network state is active
              WiFi module is connected to access point
              Failed messages: pending 0, notready 0, noresp 1
              ....
              

              Hypercube-Evolution-Hybrid, Piezo Orion, Orbiter
              Duet WiFi 1.02 or later + DueX5
              RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.0beta4 (2021-09-27 11:30:36)
              Duet WiFi Server: 1.26
              Duet Web Control 3.4.0beta4 (2021-09-27)

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

                @siam said in Network problem (noresp 1....8):

                but take a look at this https://forum.duet3d.com/topic/23397/no-wifi-this-morning here it can maybe the same issue?

                I don't think so. It looks like they have an old beta version of the wifi server. I think updating to 1.26 will solve their problem.

                Z-Bot CoreXY Build | Thingiverse Profile

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

                  @phaedrux The last week i had no issues with 3.2.2 so i will try today to go to the latest beta and try to get this problem

                  Hypercube-Evolution-Hybrid, Piezo Orion, Orbiter
                  Duet WiFi 1.02 or later + DueX5
                  RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.0beta4 (2021-09-27 11:30:36)
                  Duet WiFi Server: 1.26
                  Duet Web Control 3.4.0beta4 (2021-09-27)

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