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

    Duet 2 WiFi Board Connection Issues

    Scheduled Pinned Locked Moved
    Duet Web Control
    3
    3
    218
    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.
    • Nazarundefined
      Nazar
      last edited by

      Hello everyone,

      I've been facing persistent issues with my Duet 2 WiFi board and I'm hoping to get some guidance.

      Problem Description:

      • I'm experiencing significant instability with the Wi-Fi connection. The connectivity is not only hard to establish but also frequently drops.
      • Often, I find myself having to restart the machine to regain connection.
      • After the machine has been idle for a while, re-establishing a connection becomes near impossible without a restart.
      • Even after restarting and initiating a print, the board becomes unavailable, rendering me unable to pause the print or adjust the offset.
      • Sometimes when I am trying to connect machine will restart.

      What I've Tried:

      • I've attached the results of two M122 commands for further inspection. (it was sent right after the machine restarted on its own)
      • My setup includes some conditional G-code with while loops, but I've ensured they don't run in the background.
      • I've made efforts to minimize the use of global variables and ensured no macros run in the background to maintain efficiency.

      From my perspective, it feels like the board may be running out of RAM or facing a similar resource constraint.

      I would sincerely appreciate any insights or suggestions on what the underlying issue might be. Thank you in advance for your time and expertise.

      === Diagnostics === 
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.0-rc.1 (2023-08-31 16:16:15) running on Duet WiFi 1.02 or later 
Board ID: 0JD0M-9X6JA-JUNSS-6JTDA-3SN6L-KALVT 
Used output buffers: 26 of 26 (26 max) 
Error in macro line 34 while starting up: Driver 5 does not support x64 microstepping with interpolation 
Driver 6 does not support x64 microstepping with interpolation 
Driver 7 does not support x64 microstepping with interpolation 
=== RTOS === 
Static ram: 23076 
Dynamic ram: 77604 of which 0 recycled 
Never used RAM 9608, free system stack 184 words 
Tasks: NETWORK(2,nWait,10.6%,221) HEAT(3,nWait,0.1%,329) Move(4,nWait,0.0%,364) MAIN(1,running,85.7%,743) IDLE(0,ready,3.6%,29), total 100.0% 
Owned mutexes: WiFi(NETWORK) 
=== Platform === 
Last reset 00:00:35 ago, cause: software 
Last software reset at 2023-10-03 16:40, reason: HeatTaskStuck, Platform spinning, available RAM 7556, slot 1 
Software reset code 0x4140 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f80f BFAR 0xe000ed38 SP 0x200046c0 Task MAIN Freestk 3301 ok 
Stack: 00000000 2000412c 10000000 e000e000 004e99ba 0045e8af 0045e020 61000000 0045e011 41caf940 ffffffff 00000000 0003673b 00000000 20001158 ffffffff 20010ff8 00000000 0045e0d7 20004770 20004794 00000002 0045b531 0000003e 00446335 2000479c 00430ee1 
Error status: 0x00 
Aux0 errors 0,0,0 
MCU temperature: min 29.1, current 30.4, max 30.6 
Supply voltage: min 21.0, current 24.2, max 26.1, under voltage events: 0, over voltage events: 0, power good: yes 
Heap OK, handles allocated/used 99/8, heap memory allocated/used/recyclable 2048/592/312, gc cycles 0 
Events: 0 queued, 0 completed 
Driver 0: ok, SG min n/a 
Driver 1: ok, SG min n/a 
Driver 2: ok, SG min n/a 
Driver 3: ok, SG min n/a 
Driver 4: ok, SG min n/a 
Driver 5:  
Driver 6:  
Driver 7:  
Driver 8:  
Driver 9:  
Driver 10:  
Driver 11:  
Date/time: 2023-10-03 16:40:55 
Cache data hit count 1287819209 
Slowest loop: 8.65ms; fastest: 0.21ms 
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 3.7ms, write time 4.5ms, max retries 0 
=== Move === 
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, ebfmin 0.00, ebfmax 0.00 
no step interrupt scheduled 
Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0 
=== DDARing 0 === 
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 
=== Heat === 
Bed heaters 2 -1 -1 -1, chamber heaters 3 -1 -1 -1, ordering errs 0 
Heater 0 is on, I-accum = 0.0 
=== GCodes === 
Movement locks 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 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 
Q0 segments left 0 
Code queue 0 is empty 
=== Filament sensors === 
Extruder 0 sensor: no filament 
Extruder 1 sensor: no filament 
=== Network === 
Slowest loop: 7.81ms; fastest: 0.00ms 
Responder states: HTTP(0) HTTP(0) HTTP(1) HTTP(0) FTP(0) Telnet(0) 
HTTP sessions: 1 of 8 
=== WiFi === 
Interface state: active 
Module is connected to access point  
Failed messages: pending 0, notrdy 0, noresp 0 
Firmware version 2.1beta4 
MAC address e8:db:84:a7:99:15 
Module reset reason: Turned on by main processor, Vcc 3.38, flash size 2097152, free heap 39596 
WiFi IP address 192.168.31.132 
Signal strength -54dBm, channel 2, mode 802.11n, reconnections 0 
Clock register 00002002 
Socket states: 0 0 3 0 0 0 0 0

      === Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.0-rc.1 (2023-08-31 16:16:15) running on Duet WiFi 1.02 or later + DueX5
Board ID: 0JD2M-958DA-F64T0-6J1DD-3SJ6J-KQW72
Used output buffers: 3 of 26 (20 max)
=== RTOS ===
Static ram: 23076
Dynamic ram: 78104 of which 0 recycled
Never used RAM 9108, free system stack 184 words
Tasks: NETWORK(2,nWait,41.0%,221) HEAT(3,nWait,0.1%,286) Move(4,nWait,0.0%,364) DUEX(5,nWait,0.0%,26) MAIN(1,running,58.0%,739) IDLE(0,ready,0.9%,29), total 100.0%
Owned mutexes: SD0(NETWORK)
=== Platform ===
Last reset 00:01:35 ago, cause: software
Last software reset at 2023-10-03 15:22, reason: StuckInSpinLoop, Gcodes spinning, available RAM 9108, slot 2
Software reset code 0x4083 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f80f BFAR 0xe000ed38 SP 0x200026b8 Task NETW Freestk 4294966919 ok
Stack: 2000afb8 2000afc8 20002744 0047442c 00429df9 0043e02d 0043a820 210f0000 0045e0d7 20008c88 2000afc8 2000afc8 00000000 20008c88 0043e0ef 00000000 2000afcc 00000001 2000274c 00000101 00000000 00000000 00000000 00000000 00000000 00000000 2000ce74
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 41.4, current 42.2, max 42.5
Supply voltage: min 24.0, current 24.2, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/6, heap memory allocated/used/recyclable 2048/416/336, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min n/a
Driver 1: standstill, SG min n/a
Driver 2: standstill, SG min n/a
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5: standstill, SG min n/a
Driver 6: standstill, SG min n/a
Driver 7: standstill, SG min n/a
Driver 8: standstill, SG min n/a
Driver 9: standstill, SG min n/a
Driver 10: 
Driver 11: 
Date/time: 2023-10-03 15:24:49
Cache data hit count 3105460338
Slowest loop: 11.05ms; fastest: 0.20ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 7
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 3.7ms, write time 4.6ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, ebfmin 0.00, ebfmax 0.00
no step interrupt scheduled
Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
=== DDARing 0 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 2 -1 -1 -1, chamber heaters 3 -1 -1 -1, ordering errs 0
Heater 0 is on, I-accum = 0.0
=== GCodes ===
Movement locks 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 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
Q0 segments left 0
Code queue 0 is empty
=== Filament sensors ===
Extruder 0 sensor: no filament
Extruder 1 sensor: ok
=== DueX ===
Read count 1, 0.63 reads/min
=== Network ===
Slowest loop: 97.67ms; fastest: 0.00ms
Responder states: HTTP(2) HTTP(0) HTTP(0) HTTP(2) FTP(0) Telnet(0)
HTTP sessions: 2 of 8
=== WiFi ===
Interface state: active
Module is connected to access point 
Failed messages: pending 0, notrdy 0, noresp 0
Firmware version 2.1beta4
MAC address b4:8a:0a:f7:0a:cd
Module reset reason: Turned on by main processor, Vcc 3.34, flash size 2097152, free heap 30508
WiFi IP address 192.168.31.184
Signal strength -51dBm, channel 2, mode 802.11n, reconnections 0
Clock register 00002002
Socket states: 3 0 0 3 0 0 0 0
      1 Reply Last reply Reply Quote 0
      • Phaedruxundefined
        Phaedrux Moderator
        last edited by

        Can you try placing this wifi server bin file in your firmwares folder on the SD card and then send M997 S1 to reflash the module?

        https://github.com/Duet3D/DuetWiFiSocketServer/releases/download/1.27/DuetWiFiServer.bin

        Z-Bot CoreXY Build | Thingiverse Profile

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

          @Phaedrux I had the same issue on RRF3.5rc1. Downgrading the server to the version you linked helped.

          Duet 2 Wifi, Ooznest Workbee CNC 1510

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