Wifi Periodically Disconnects?
-
@rogerpodacter here are my new specs. side note i used the format tool but it did not let me chose a cluster size, but it so happened to default using 32kb cluster size so that's good.
after only a few minutes, my DWC web interface is much more responsive. I will test a print nextl.
M122 S104 P10
10/11/2022, 8:02:50 AM SD read speed for 10.0MByte file was 1.69MBytes/sec 10/11/2022, 8:02:45 AM SD write speed for 10.0MByte file was 2.33MBytes/sec Testing SD card read speed... 10/11/2022, 8:02:39 AM M122 P104 S10 Testing SD card write speed...M122
10/11/2022, 7:59:57 AM M122 === Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.4.2 (2022-09-13 15:14:33) running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: J6RFD-NR6KL-K65J0-409NN-LK02Z-7M5YU Used output buffers: 1 of 40 (40 max) === RTOS === Static ram: 103684 Dynamic ram: 111348 of which 12 recycled Never used RAM 23500, free system stack 136 words Tasks: NETWORK(notifyWait,14.2%,240) HEAT(notifyWait,0.0%,342) Move(notifyWait,0.0%,276) CanReceiv(notifyWait,0.0%,774) CanSender(notifyWait,0.0%,336) CanClock(delaying,0.0%,339) TMC(notifyWait,1.2%,72) MAIN(running,83.5%,425) IDLE(ready,0.1%,30) AIN(delaying,0.9%,263), total 100.0% Owned mutexes: === Platform === Last reset 00:05:25 ago, cause: power up Last software reset at 2022-10-09 18:10, reason: User, GCodes spinning, available RAM 23812, slot 1 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00489000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x04 Aux0 errors 0,0,0 MCU revision 3, ADC conversions started 325705, completed 325705, timed out 0, errs 0 Step timer max interval 1472 MCU temperature: min 25.0, current 38.8, max 39.2 Supply voltage: min 23.9, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/1, heap memory allocated/used/recyclable 2048/10/0, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0, read errors 0, write errors 0, ifcnt 15, reads 29543, writes 15, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 0, read errors 0, write errors 0, ifcnt 15, reads 29543, writes 15, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 0, read errors 0, write errors 0, ifcnt 15, reads 29543, writes 15, timeouts 0, DMA errors 0, CC errors 0 Driver 3: standstill, SG min 0, read errors 0, write errors 0, ifcnt 15, reads 29542, writes 15, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 0, read errors 0, write errors 0, ifcnt 15, reads 29543, writes 15, timeouts 0, DMA errors 0, CC errors 0 Driver 5: standstill, SG min 0, read errors 0, write errors 0, ifcnt 9, reads 29549, writes 9, timeouts 0, DMA errors 0, CC errors 0 Driver 6: standstill, SG min 0, read errors 0, write errors 0, ifcnt 9, reads 29549, writes 9, timeouts 0, DMA errors 0, CC errors 0 Date/time: 2022-10-11 07:59:55 Cache data hit count 610770690 Slowest loop: 6.14ms; fastest: 0.13ms === Storage === Free file entries: 10 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 3.1ms, write time 0.0ms, max retries 0 === Move === DMs created 83, segments created 13, maxWait 32740ms, bed compensation in use: mesh, comp offset -0.016 === MainDDARing === Scheduled moves 12, completed 12, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 Heater 0 is on, I-accum = 0.3 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 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 SBC is idle in state(s) 0 Daemon is idle in state(s) 0 Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty === Filament sensors === Extruder 0: no data received === CAN === Messages queued 2949, received 6681, lost 0, boc 0 Longest wait 2ms for reply type 6026, peak Tx sync delay 13, free buffers 18 (min 17), ts 1628/1627/0 Tx timeouts 0,0,0,0,0,0 === Network === Slowest loop: 12.94ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 1 of 8 = WiFi = Network state is active WiFi module is providing access point Failed messages: pending 0, notready 0, noresp 0 WiFi firmware version 1.27 WiFi MAC address ea:68:e7:e5:63:f4 WiFi Vcc 3.38, reset reason Power up WiFi flash size 2097152, free heap 25296 WiFi IP address 192.168.1.10 Connected clients 1 Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0M39
10/11/2022, 7:59:18 AM M39 SD card in slot 0: capacity 7.95GB, partition size 7.94GB, free space 7.69GB, speed 22.50MBytes/sec, cluster size 32kB -
@rogerpodacter Unfortunately i just went to upload my first gcode file, and the wifi immediately disconnected. For some reason this did not solve the issue.
UPDATE: i cannot upload gcode, period. every upload attempt fails, no matter how many attempts i do. not sure what to do here...
The M122 S104 P10 command will not run for some reason. it just does not respond. I will try a reboot. EDIT: did not help. no response.
M122
10/11/2022, 1:24:10 PM M122 === Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.4.2 (2022-09-13 15:14:33) running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: J6RFD-NR6KL-K65J0-409NN-LK02Z-7M5YU Used output buffers: 2 of 40 (40 max) === RTOS === Static ram: 103684 Dynamic ram: 111564 of which 12 recycled Never used RAM 22684, free system stack 118 words Tasks: NETWORK(notifyWait,125.7%,199) HEAT(notifyWait,0.2%,336) Move(notifyWait,2.1%,253) CanReceiv(notifyWait,0.3%,772) CanSender(notifyWait,0.1%,325) CanClock(delaying,0.1%,339) TMC(notifyWait,10.6%,72) MAIN(running,204.9%,417) IDLE(ready,0.6%,30) AIN(delaying,7.4%,263), total 351.9% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 05:29:38 ago, cause: power up Last software reset at 2022-10-09 18:10, reason: User, GCodes spinning, available RAM 23812, slot 1 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00489000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x04 Aux0 errors 0,0,0 MCU revision 3, ADC conversions started 19778981, completed 19778980, timed out 0, errs 0 Step timer max interval 1471 MCU temperature: min 38.8, current 40.7, max 42.6 Supply voltage: min 23.9, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/1, heap memory allocated/used/recyclable 2048/504/494, gc cycles 1 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0, read errors 0, write errors 0, ifcnt 70, reads 64417, writes 55, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 0, read errors 0, write errors 0, ifcnt 70, reads 64417, writes 55, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 0, read errors 0, write errors 0, ifcnt 70, reads 64417, writes 55, timeouts 0, DMA errors 0, CC errors 0 Driver 3: standstill, SG min 0, read errors 0, write errors 0, ifcnt 70, reads 64418, writes 55, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 0, read errors 0, write errors 0, ifcnt 70, reads 64417, writes 55, timeouts 0, DMA errors 0, CC errors 0 Driver 5: standstill, SG min 0, read errors 0, write errors 0, ifcnt 9, reads 64472, writes 0, timeouts 0, DMA errors 0, CC errors 0 Driver 6: standstill, SG min 0, read errors 0, write errors 0, ifcnt 9, reads 64472, writes 0, timeouts 0, DMA errors 0, CC errors 0 Date/time: 2022-10-11 13:24:09 Cache data hit count 4294967295 Slowest loop: 185.91ms; fastest: 0.09ms === Storage === Free file entries: 10 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 7.6ms, write time 62.2ms, max retries 0 === Move === DMs created 83, segments created 38, maxWait 5764281ms, bed compensation in use: mesh, comp offset 0.000 === MainDDARing === Scheduled moves 61138, completed 61138, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 19], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 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 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 SBC is idle in state(s) 0 Daemon is idle in state(s) 0 Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty === Filament sensors === Extruder 0: no data received === CAN === Messages queued 237909, received 406295, lost 0, boc 0 Longest wait 5ms for reply type 6029, peak Tx sync delay 285, free buffers 18 (min 3), ts 97266/97266/0 Tx timeouts 0,0,0,0,0,0 === Network === Slowest loop: 243.73ms; fastest: 0.06ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 1 of 8 = WiFi = Network state is active WiFi module is providing access point Failed messages: pending 0, notready 0, noresp 0 WiFi firmware version 1.27 WiFi MAC address ea:68:e7:e5:63:f4 WiFi Vcc 3.38, reset reason Power up WiFi flash size 2097152, free heap 25248 WiFi IP address 192.168.1.10 Connected clients 1 Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0M39
10/11/2022, 1:25:35 PM M39 SD card in slot 0: capacity 7.95GB, partition size 7.94GB, free space 7.69GB, speed 22.50MBytes/sec, cluster size 32kB -
Do you have a different SD card entirely to test with?
-
@phaedrux i just tried with an 8gb SD card from an Ender 3, i removed all contents, and copied over the Duet backup. this behavior is weird as well, i could not upload anything. i did not format this other card, its already formatted FAT32. and it has 7.1 gb free out of 7.48 gb total. Here is the error screen.
-
@rogerpodacter i also formatted the Ender 3 card, 32kb cluster, and the Duet has the same behavior. it cannot upload anything. it fails immediately and times out the wifi connection.
I am going back to the Duet card and formatting with a 4kb cluster. not sure what is going on. are we sure Duet 3 Mini 5+ is supposed to use 32kb cluster size?
EDIT: setting back to 4kb cluster and the Duet behavior returned to normal. i'm not sure what that was about, i'd like to solve the disconnect issue. i could perhaps try 16kb cluster size, but something just seems strange that it struggled so much at 32kb.
-
Rather than using the windows format tool, can you try using the SD card formatter tool?
https://www.sdcard.org/downloads/formatter/
It should use the correct formatting based on the type of card. It's usually the safest bet.
One other thing I would like you to try is to replace the contents of the www folder on the SD card with fresh files from this zip file. These are the files used for DWC.
https://github.com/Duet3D/DuetWebControl/releases/download/v3.4.2/DuetWebControl-SD.zip
-
@phaedrux thanks. so all these tests i have been using the SD card format utility provided in the guide. for some reason this fails completely, additionally it doesnt seem to allow me to pick a cluster size.
But i just switched to using the windows 10 Disk Management, and this seems to work ok. i can select cluster size. and the DWC can now run M122 successfully, but it still fails uploads. so far i have tried cluster size 64kb, 32kb, 16kb, and all of them fail during an upload. 4kb fails too, but its hit and miss so sometimes it works; the other sizes fail 100% of the time.
EDIT: i just copied the DWC link from github you provided, using 64kb cluster size, and uploads are working. this is excellent! i will wait a day or so to see if it is long term. but this is promising so far. much appreciated!
EDIT 2: no, an upload just failed. but the success rate is far better now, it fails very rarely. so i will go with this. honestly i think it might be related to my windows machine somehow, but i dont have evidence of that just guessing.
-
@rogerpodacter said in Wifi Periodically Disconnects?:
additionally it doesnt seem to allow me to pick a cluster size.
That's because the settings are pre-determined by the type of SD card it is. Not sure why it would fail though. What happens with it?
Are you using the Duet in Access Point Mode? What kind of signal strength are you getting from your PC?
-
@phaedrux so i am on a corp wired network computer, so i cannot use traditional router wifi. the Duet is running ad hoc wifi access point where Duet broadcasts the network to my laptop.
the laptop is 24 inches from the printer showing full signal strength.
more info:
a test i often do is use the height map and scroll around quickly. there is stuttering there sometimes, and other times its smooth. my browser window is always open to the Duet, and after about 24 hours the Firefox tab becomes slow and sluggish and uses high CPU resources. i kill the task, restart Firefox, and return it to normal. I think these could somehow be related.actually i just killed the browser tab and restarted it and the success rate returns to normal. so i am now suspecting it is related to the browser becoming slow/sluggish. I assume its because the console log keeps growing over time so i should kill the browser every few hours.
-
So if the tab is freshly opened are you able to upload reliably?
-
@phaedrux yes so far today since i've done that it seems perfectly reliable. so it very likely could have been my computer causing this issue.
I guess a side note, only the DWC tab seems to grow in resources, its probably the console log constantly running...
-
@rogerpodacter did you see what errors the log was reporting?
Ian
-
@droftarts no i didnt pay attention, i was just speculating. but i just repeated the test.
this morning i checked the console log from overnight and there were zero messages for the last 12 hours, so that is good. but the browser tab was still running high consuming 10% CPU, so i had to kill the task. not sure if its a memory leak.
-
@rogerpodacter are you running the same version of DWC as RRF firmware? Otherwise we will need @chrishamm to investigate what’s causing the memory leak.
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
-
@droftarts It doesn't have to be a memory leak. When running DWC for hours, Safari often advises me to close the tab because it consumes quite a lot of resources, I.e. power. In my case, that’s simply some load on the CPU. Given that @chrishamm permanently scans the Duet’s object model, that’s exactly what I expect to happen.
-
@droftarts yes i'm running DWC 3.4.2 and RRF 3.4.2.
and my wifi has not disconnected at since yesterday. so far so good.
