Wifi Periodically Disconnects?

RogerPodacter

I use a Duet 3 Mini 5+, Toolboard 1LC, on a CoreXY printer. I dont know if this is my computer or the Duet behavior, but i see these regular disconnects from wifi, and it interupts various things like when i upload a Gcode it kills it right in the middle of the upload, etc. I suspect it might be my computer because i am connected to 2 networks simultaneously so i can wifi to the Duet and ethernet to the regular internet.

10/9/2022, 5:20:33 PM 	Connection established
10/9/2022, 5:18:07 PM 	Connection interrupted, attempting to reconnect...
HTTP request timed out
10/9/2022, 5:15:10 PM 	Upload of Calibration cube_0.2mm_PLA_18m.gcode successful after 3s
10/9/2022, 5:14:06 PM 	Connection established
10/9/2022, 5:12:10 PM 	Connection interrupted, attempting to reconnect...
HTTP request timed out
10/9/2022, 5:11:59 PM 	Upload of config.g successful after 0s
10/9/2022, 5:11:02 PM 	Connection established
10/9/2022, 5:05:31 PM 	Connection interrupted, attempting to reconnect...
HTTP request timed out
10/9/2022, 5:05:20 PM 	Upload of config.g successful after 0s
10/9/2022, 5:04:34 PM 	Connection established

M98 "config.g"

10/9/2022, 5:32:05 PM 	Warning: Heater 0 predicted maximum temperature at full power is 328°C
Accelerometer 121:0 type LIS3DH with orientation 16 samples at 1344Hz with 10-bit resolution
Warning: the height map was loaded when the current Z=0 datum was not determined by probing. This may result in a height offset.
Warning: Macro file config-override.g not found

M122 B121

10/9/2022, 5:34:05 PM 	M122 B121
Diagnostics for board 121:
Duet TOOL1LC rev 1.1 or later firmware version 3.4.2 (2022-09-13 15:06:56)
Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
All averaging filters OK
Never used RAM 2172, free system stack 62 words
Tasks: Move(notifyWait,0.0%,153) HEAT(notifyWait,0.4%,77) CanAsync(notifyWait,0.0%,65) CanRecv(notifyWait,0.0%,76) CanClock(notifyWait,0.0%,65) ACCEL(notifyWait,0.0%,61) TMC(delaying,3.0%,57) MAIN(running,91.6%,351) IDLE(ready,0.0%,26) AIN(delaying,4.9%,142), total 100.0%
Last reset 00:03:38 ago, cause: software
Last software reset data not available
Driver 0: pos 0, 690.0 steps/mm,standstill, SG min 0, read errors 0, write errors 1, ifcnt 43, reads 43805, writes 15, timeouts 19, DMA errors 0, CC errors 0, failedOp 0x6c, steps req 0 done 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
Peak sync jitter -3/6, peak Rx sync delay 216, resyncs 0/0, no step interrupt scheduled
VIN voltage: min 23.8, current 24.1, max 24.1
MCU temperature: min 41.1C, current 41.1C, max 46.4C
Last sensors broadcast 0x00000002 found 1 195 ticks ago, 0 ordering errs, loop time 1
CAN messages queued 4434, send timeouts 7, received 1951, lost 0, free buffers 37, min 37, error reg 110000
Last cancelled message type 4519 dest 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
Accelerometer: LIS3DH, status: 00
I2C bus errors 0, naks 3, other errors 0
=== Filament sensors ===
Interrupt 4 to 9us, poll 6 to 1870us
Driver 0: pos 2274.61, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0

droftarts

@rogerpodacter I would suspect an SD card issue. Please post your config.g, the response to M122 (for the main board) and also the response to M39. You can run a speed test on the SD card; see https://docs.duet3d.com/User_manual/RepRapFirmware/SD_card#troubleshooting-sd-card-issues
Please also post what SD card you are using.

Ian

RogerPodacter

@droftarts I'll did the SD card test. i am using the stock card that came with the Duet 3 Mini 5+, i'm not sure what quality it is but i assume its decent quality.

M122 mainboard

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: 3 of 40 (40 max)
=== RTOS ===
Static ram: 103684
Dynamic ram: 111564 of which 216 recycled
Never used RAM 22384, free system stack 112 words
Tasks: NETWORK(notifyWait,82.1%,177) HEAT(notifyWait,0.7%,336) Move(notifyWait,20.8%,251) CanReceiv(notifyWait,1.3%,772) CanSender(notifyWait,0.7%,325) CanClock(delaying,0.3%,339) TMC(notifyWait,40.5%,72) MAIN(running,116.8%,415) IDLE(ready,4.0%,30) AIN(delaying,28.1%,263), total 295.2%
Owned mutexes:
=== Platform ===
Last reset 26:15:59 ago, cause: software
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 94561267, completed 94561267, timed out 0, errs 0
Step timer max interval 1486
MCU temperature: min 39.8, current 44.2, max 45.6
Supply voltage: min 23.9, current 24.0, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/2, heap memory allocated/used/recyclable 2048/1724/1672, gc cycles 9
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, read errors 0, write errors 1, ifcnt 36, reads 10039, writes 214, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, SG min 0, read errors 0, write errors 1, ifcnt 35, reads 10039, writes 214, timeouts 0, DMA errors 0, CC errors 0
Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 36, reads 10038, writes 214, timeouts 0, DMA errors 0, CC errors 0
Driver 3: ok, SG min 0, read errors 0, write errors 1, ifcnt 38, reads 10034, writes 217, timeouts 1, DMA errors 0, CC errors 0, failedOp 0x6a
Driver 4: ok, SG min 0, read errors 0, write errors 1, ifcnt 38, reads 10035, writes 217, timeouts 1, DMA errors 0, CC errors 0, failedOp 0x6c
Driver 5: standstill, SG min 0, read errors 0, write errors 1, ifcnt 49, reads 10244, writes 9, timeouts 0, DMA errors 0, CC errors 0
Driver 6: standstill, SG min 0, read errors 0, write errors 1, ifcnt 49, reads 10243, writes 9, timeouts 0, DMA errors 0, CC errors 0
Date/time: 2022-10-10 20:26:12
Cache data hit count 4294967295
Slowest loop: 231.91ms; fastest: 0.07ms
=== Storage ===
Free file entries: 9
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 8.2ms, write time 149.4ms, max retries 0
=== Move ===
DMs created 83, segments created 42, maxWait 32940340ms, bed compensation in use: mesh, comp offset -0.016
=== MainDDARing ===
Scheduled moves 247070, completed 247030, hiccups 0, stepErrors 0, LaErrors 0, Underruns [4, 0, 35], CDDA state 3
=== 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.4
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 1
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is doing "G1 X122.439 Y149.252 E0.00226" 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
Queued 'M107' for move 247034
Queued 'M107' for move 247037
Queued 'M107' for move 247038
Queued 'M107' for move 247039
Queued 'M107' for move 247048
Queued 'M107' for move 247055
Queued 'M107' for move 247060
Queued 'M107' for move 247068
=== Filament sensors ===
Extruder 0: no data received
=== CAN ===
Messages queued 1670401, received 1981721, lost 0, boc 0
Longest wait 6ms for reply type 6029, peak Tx sync delay 291, free buffers 18 (min 3), ts 472797/472796/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 219.58ms; 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 22656
WiFi IP address 192.168.1.10
Connected clients 2
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

config.g

; General preferences
G90                                     ; send absolute coordinates...
M83                                     ; ...but relative extruder moves
M550 P"V-Core3"                         ; set printer name
M669 K1                                 ; CoreXY
G21                                     ; Set Units to Millimeters

; Network
M552 S2                                 ; enable network
M586 P0 S1                              ; enable HTTP
M586 P1 S0                              ; disable FTP
M586 P2 S0                              ; disable Telnet

G4 S2 ; wait for expansion boards to start

; Drives
M569 P0.0 S0 D2	                        ; Left Z physical drive 0.0 goes forwards
M569 P0.1 S0 D2                         ; Rear Z physical drive 0.1 goes forwards
M569 P0.2 S0 D2                            ; Right Z physical drive 0.2 goes forwards
M569 P0.3 S1 D2                            ; Right physical drive 0.3 goes forwards
M569 P0.4 S1 D2                            ; Left physical drive 0.4 goes forwards
M569 P121.0 S1 D2                            ; Extruder physical drive 0.5 goes forwards
M584 X0.4 Y0.3 Z0.0:0.1:0.2 E121.0        ; set drive mapping
M350 X16 Y16 Z16 E16 I1                 ; configure microstepping with interpolation

M92 X80.00 Y80.00 Z800.00 E690 ;E400               ; set steps per mm
M906 X2000 Y2000 Z1800 E1000 I10 ;E700 I30              ; set motor currents (mA) and motor idle factor in per cent -- safe for Duet 3 mini 5+
M84 S30                                 ; Set idle timeout

M566 X1000.00 Y1000.00 Z6.00 E300 P1 ;E120.00 P1          ; set maximum instantaneous speed changes (mm/min)
M203 X30000.00 Y30000.00 Z1000.00 E7200 ;E3600.00     ; set maximum speeds (mm/min)
M201 X10000.00 Y10000.00 Z100.00 E10000 ;E3600.00        ; set accelerations (mm/s^2)

M207 S0.6 F7200 Z0.2						; firmware retraction orbiter 2.0

; Axis Limits
M208 X0 Y0 Z0 S1                               ; set axis minima
M208 X310 Y310 Z300 S0                         ; set axis maxima

; Endstops
M574 X1 S1 P"121.io2.in"                           ; configure active high endstops
M574 Y2 S1 P"io1.in"                           ; configure active high endstops

M671 X-4.5:150:304.5 Y-4.52:305:-4.52 S5       ; define positions of Z leadscrews or bed levelling screws
M557 X30:280 Y20:290 P5                        ; define 5x5 mesh grid

; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B3950 A"Keenevo 600W Bed"    ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out0" T0 Q10												; Define Heater0 as the heated bed, bind to Sensor0
M140 H0 P0															; Define Heated Bed
M307 H0 A303.1 C356.7 D1.4 S1.00 V24.0 B0
;M307 H0 R0.860 C439.9 D11.80 S1.00 B0							; PID Tuning for Heater0, Heated Bed (45C)
M143 H0 S110														; Set temperature limit for Heater0 to 120C

M308 S1 P"121.temp0" Y"thermistor" T100000 B4725 C7.060000e-8 A"Slice Hotend"  ;Slice Engineering 300C thermistor, settings are online
M950 H1 C"121.out0" T1 Q100													; Define Heater1 as Extruder0 heater, bind to Sensor1
M307 H1 R3.075 K0.558:0.000 D4.86 E1.35 S1.00 B0 V24.0
;M307 H1 R2.794 C119.4:105.8 D3.09 S1.00 V24.1 B0					; PID Tuning for Heater1, Extruder0 (200C)
;M307 H1 A751.5 C196.6 D4.7 S1.00 V23.9 B0
M143 H1 S285														; Set temperature limit for heater 1 to 285C
;M308 S2 P"temp2" Y"thermistor" A"Chamber" T100000 B4725 C7.060000e-8; Define Sensor2 as Chamber temperature (Semitec 104GT2)
M308 S3 Y"mcu-temp" A"MCU"											; Define Sensor3 as the integrated MCU temperature sensor
M308 S4 Y"drivers" A"TMC Drivers"									; Define Sensor4 as the TMC overheat sensor

; Fans
M308 S2 Y"drivers" A"4028 Power"    								; configure sensor 0 as thermistor on pin temp0
M950 H2 C"!out2" T2 Q10												; Define Heater2 as the 4028 fan power, bind to Sensor2
M143 H2 P2 S200
;M307 H2 I1 S1
;M106 P2 C"4028 Power" S0 H-1										; 4028 power using spare heater

;M950 F0 C"121.out1" Q500                   							; create fan 0 on pin out4 and set its frequency
M950 F0 C"!121.out1+out1.tach" Q25000
M106 P0 C"Layer Fan" S0 L0.0 X1.0 H-1
;M106 P0 C"Layer Fan" S0 H-1            							; set fan 0 name and value. Thermostatic control is turned off

;M950 F1 C"out3" Q500                   ; create fan 1 on pin out3 and set its frequency
M950 F1 C"121.out2+out2.tach" Q500 				; Fan 1 uses out3, and using out3.tach as a tacho input
M106 P1 C"Hotend Fan" S0 H1 T45        ; set fan 1 name and value. Thermostatic control turned on for Hotend

M950 F2 C"out5" Q500                   ; create fan 1 on pin out5 and set its frequency
M106 P2 C"Board Fan" S0 H3 T42        ; set fan 1 name and value. Thermostatic control turned on for Hotend

; Tools
M563 P0 D0 H1 F0 S"Mosquito Magnum"           										; define tool 0
G10 P0 X0 Y0 Z0 R0 S0            ; set tool 0 axis offsets, set initial tool 0 active 60C and standby temperatures to 0C

;M563 P0 H0 F0 S"Keenevo 600W Bed"
;G10 P0 X0 Y0 Z0
;G10 P0 R50 S0

; EVA 2 / BMG / E3D V6

;M92 E400          ; set extruder steps per mm, 0.9 angle/step (LDO Pancake)
;M906 E800         ; set extruder motor current (mA) and idle factor in per cent

;M308 S1 P"temp1" Y"thermistor" T100000 B4725 C7.060000e-8 A"Hotend"  
;; Run Heater PID Tune!! 
;; M307 H1 A751.5 C196.6 D4.7 S1.00 V23.9 B0

; Z-Probe
;; Inductive Probe
;M558 P5 C"io3.in" H5 F400 T5000       ; set Z probe type to unmodulated and the dive height + speeds
M558 P8 C"121.io0.in" H5 F400 T5000       ; set Z probe type to unmodulated and the dive height + speeds
G31 P1000 X-28 Y-15 Z1.02               ; set Z probe trigger value, offset and trigger height, more Z means closer to the bed
;G31 P500 X-30 Y-15 Z0					

;; BLTouch
; M950 S0 C"io7.out"                     ; Create a servo pin on io7
; M558 P9 C"io7.in" H5 F240 T10800 A5    ; set Z probe type to unmodulated and the dive height + speeds
; G31 P25 X-28.00 Y-13.00 Z0.78          ; set Z probe trigger value, offset and trigger height, more Z means closer to the bed

;Accelerometer
M955 P121.0 I16

;Input Shaper
M593 P"zvdd" F42.5		; for 10k acceleration
;M593 P"mzv" F42.5		; for 15k acceleration

;Filament Sensor0
M591 D0 P3 C"121.io1.in" S1
M591 D0 L27

;PanelDue 5i
M575 P1 S1 B57600

;NeoPixels x3
M150 X1 Q4000000 ;R128 U128 B128 P128 S2 F0
M150 X1 R128 U128 B128 P128 S2 F0      ; display led

; Custom settings are not configured
G29 S1
M572 D0 S0.06 ;S0.10; set Pressure Advance K-factor
M501

; init print time logging
if !exists(global.runtime)
  M98 P"runtime.g"

; Select default tool
M404 N1.75															; Define filament diameter for print monitor
T0

SD Card speed test looks pretty good. i dont have print issues and i print pretty fast 150-200 mm/s.

10/10/2022, 8:32:48 PM 	SD read speed for 10.0MByte file was 1.37MBytes/sec
10/10/2022, 8:32:41 PM 	SD write speed for 10.0MByte file was 2.38MBytes/sec
Testing SD card read speed...
10/10/2022, 8:32:37 PM 	M122 P104 S10
Testing SD card write speed...

M39

M39
SD card in slot 0: capacity 7.95GB, partition size 2.14GB, free space 1.96GB, speed 22.50MBytes/sec, cluster size 4kB

RogerPodacter

@rogerpodacter i just read the rest of the SD card link, and one thing i could relate to, my wifi almost always disconnects right when i try to upload a file. it breaks the connection within the first few % of the upload. so i think you are right i should get a faster SD card or change the cluster size.

Phaedrux

Can you check how much freespace your SD card has?

droftarts

@rogerpodacter said in Wifi Periodically Disconnects?:

SD card in slot 0: capacity 7.95GB, partition size 2.14GB, free space 1.96GB, speed 22.50MBytes/sec, cluster size 4kB

Odd that it is a 8GB card, but with only a 2GB partition. There is plenty of free space, but then the cluster size is 4kB; it should be 32kB. The small cluster size would put an extra load on the Duet, and is likely causing the drop out when uploading. I recommend copying your files off the SD card, reformatting the SD card with the SD formatting tool (use the full size), then copying the files back onto it. See https://docs.duet3d.com/User_manual/RepRapFirmware/SD_card#formatting

Have you reformatted the SD card before, or is this as it was supplied?

Ian

RogerPodacter

@droftarts this is how it was supplied, i never touched this card. just took it out of the box and inserted and of and running.

I'm doing the formatting now...

EDIT: i can copy over the boot partition with my macros, sys config.g, gcodes etc, but Windows 10 cannot see or access the other SDHC partition. I assume that is by design? it looks like 2gb are being used in that partition.

RogerPodacter

@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 0

M39

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

@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 0

M39

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

Phaedrux

Do you have a different SD card entirely to test with?

RogerPodacter

@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

@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.

Phaedrux

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

RogerPodacter

@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.

Phaedrux

@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?

RogerPodacter

@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.

Phaedrux

So if the tab is freshly opened are you able to upload reliably?

RogerPodacter

@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...

droftarts

@rogerpodacter did you see what errors the log was reporting?

Ian

RogerPodacter

@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.