DUET 3 mini 5 wifi unstable
-
I have found a problem where the wireless module will not reconnect to the wireless network, after a restart or power off / on cycle. The console throws a continuous loop of:
Error: WiFi module reported: network scan failedI have tried reinstalling the firmware multiple times and am on the latest firmware. This is an error report rather than a request for help as I have bought the wired version to replace it with.
-
@JabawokJayUK what do you class as the latest firmware?
please post an output of M122Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is
-
@jay_s_uk said in DUET 3 mini 5 wifi unstable:
what do you class as the latest firmware?
3.4.5 Stable.
-
@jay_s_uk M122 Output:
M122 === Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.4.5 (2022-11-30 19:41:16) running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: 7MHB6-B296U-D65J0-40KM0-3103Z-H23WT Used output buffers: 3 of 40 (21 max) === RTOS === Static ram: 103652 Dynamic ram: 111168 of which 0 recycled Never used RAM 26892, free system stack 194 words Tasks: NETWORK(notifyWait,11.6%,215) HEAT(notifyWait,0.0%,342) Move(notifyWait,0.0%,363) CanReceiv(notifyWait,0.0%,797) CanSender(notifyWait,0.0%,336) CanClock(delaying,0.0%,348) TMC(notifyWait,1.2%,115) MAIN(running,86.1%,425) IDLE(ready,0.3%,30) AIN(delaying,0.8%,263), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:01:39 ago, cause: power up Last software reset at 2023-03-24 09:38, reason: User, GCodes spinning, available RAM 26892, slot 0 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Aux0 errors 0,0,0 MCU revision 3, ADC conversions started 99432, completed 99432, timed out 0, errs 0 Step timer max interval 1470 MCU temperature: min 18.9, current 23.7, max 23.9 Supply voltage: min 24.0, current 24.1, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0, read errors 0, write errors 0, ifcnt 9, reads 8994, writes 9, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 0, read errors 0, write errors 0, ifcnt 9, reads 8993, writes 9, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 0, read errors 0, write errors 0, ifcnt 9, reads 8993, writes 9, timeouts 0, DMA errors 0, CC errors 0 Driver 3: standstill, SG min 0, read errors 0, write errors 0, ifcnt 9, reads 8993, writes 9, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 0, read errors 0, write errors 0, ifcnt 9, reads 8993, writes 9, timeouts 0, DMA errors 0, CC errors 0 Driver 5: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 8992, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 6: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 8992, writes 10, timeouts 0, DMA errors 0, CC errors 0 Date/time: 2023-03-24 12:03:27 Cache data hit count 189075977 Slowest loop: 11.45ms; fastest: 0.13ms === Storage === Free file entries: 10 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 0.7ms, write time 0.0ms, max retries 0 === Move === DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 0, completed 0, 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 3 -1 -1 -1, ordering errs 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 === CAN === Messages queued 901, received 1989, lost 0, boc 0 Longest wait 3ms for reply type 6053, peak Tx sync delay 6, free buffers 18 (min 17), ts 497/496/0 Tx timeouts 0,0,0,0,0,0 === Network === Slowest loop: 12.65ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 1 of 8 = WiFi = Network state is active WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 0 WiFi firmware version 1.27 WiFi MAC address f0:08:d1:03:7f:b0 WiFi Vcc 3.40, reset reason Power up WiFi flash size 2097152, free heap 25208 WiFi IP address 192.168.100.165 WiFi signal strength -42dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0 -
If you send M552 S0 and then M552 S1 from the PanelDue does it manage to connect?
-
@Phaedrux Unfortunately, this does not fix it. Today, I booted the machine after being off all night. It came up and connected to the SSID, acquired its IP without issue and I successfully connected to the web GUI. Within 30s it dropped the wifi and was unable to connect again with the panelDue showing it no longer had a connection to the wifi:
I ran M552 S0/1 as requested from the Panel Due and that leaves it in the following state:
ERROR: WiFi module reported Unexpected WiFi state 'idle' while trying to connectAs you can see from the image below, the ariel is in plenty of space and the closest access point is <1m away offering coverage for a/c/b/g/n/ specifications.
-
Can you show some photos of the antenna connection at the duet? Can you try reseating the connection?
Do you have a dedicated 2.4ghz SSID to connect to?
-
@Phaedrux I have previously tried all of those options. Dedicated 2.4ghz SSID, and multiple tails / multiple antennas (2-10 dBi) both directly connected or with extensions to locate the antenna in better air. Its not a physical issue.
Its either a bad board or a firmware issue, and the solution to both is to move to wired. I didn't want it to be connected over wifi initially, as I intended to use it in SBC mode, so it wasn't an issue, and I had this wifi version spare. Still, now I intend not to use the SBC so replacing it with a wired version is the logical option.
