Trouble Connecting Duet 2 Wifi

Purgatorium

I’ve followed all setup procedures at "Getting connected to your Duet | Duet3D Documentation". I can connect and communicate through the USB connection using YAT; however, the M522 S1 always returns an Error: Wifi module reported: no known networks found ...Wifi module idle.

I purchased this new Duet2 wifi from Filastruder. to replace my old one that died recently. I’ve established a 2.4Ghz local and guest network, and used no special characters in the network SSID or password. Both 2.4Ghz networks will not connect to the Duet2 wifi, but will connect with all my other devices

The wifi led on the Duet 2 wifi board does blink green when I first power it up using the USB cable, and again using M552 SO

Filastruder asked that I request help here before I return the board to them.

M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.4.4 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2022-10-20 16:17:41
ok

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.4 (2022-10-20 16:17:41) running on Duet WiFi 1.02 or later
Board ID: 0JD2M-9F8TA-GJ4TD-6JTD2-3SJ6Q-KQQY5
Used output buffers: 1 of 26 (3 max)
=== RTOS ===
Static ram: 23860
Dynamic ram: 73592 of which 0 recycled
Never used RAM 14628, free system stack 193 words
Tasks: NETWORK(ready,8.0%,340) HEAT(notifyWait,0.0%,388) Move(notifyWait,0.0%,363) MAIN(running,91.8%,452) IDLE(ready,0.2%,30), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:08:09 ago, cause: power up
Last software reset details not available
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 18.2, current 23.9, max 24.4
Supply voltage: min 0.0, current 0.0, max 0.1, 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
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: 1970-01-01 00:00:00
Cache data hit count 4294967295
Slowest loop: 99.75ms; fastest: 0.13ms
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 3.1ms, 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 -1 -1 -1 -1, chamber heaters -1 -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 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
=== Network ===
Slowest loop: 0.77ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 0 of 8
= WiFi =
Network state is active
WiFi module is idle
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 2.2.0
WiFi MAC address 00:00:00:00:00:00
WiFi Vcc 3.39, reset reason Power up
WiFi flash size 2097152, free heap 53932
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
ok

PC SETUP:

Device name DESKTOP-T0EP8SU
Processor AMD Ryzen 9 7950X 16-Core Processor 4.50 GHz
Installed RAM 64.0 GB (63.2 GB usable)
Device ID 47EAEE84-7E7E-43D7-A939-99B17CFCDFBC
Product ID 00330-80030-14886-AA621
System type 64-bit operating system, x64-based processor
Pen and touch No pen or touch input is available for this display

Edition Windows 11 Pro
Version 24H2
Installed on ‎12/‎22/‎2024
OS build 26100.2605
Experience Windows Feature Experience Pack 1000.26100.36.0

ROUTER:

TP-Link AX3000

Standards
Wi-Fi 6
IEEE 802.11ax/ac/n/a 5 GHz
IEEE 802.11ax/n/b/g 2.4 GHz
WiFi Speeds
AX3000
5 GHz: 2402 Mbps (802.11ax, HE160)
2.4 GHz: 574 Mbps (802.11ax)

WiFi Reception Sensitivity
5 GHz:
11a 6Mbps:-97dBm, 11a 54Mbps:-79dBm
11ac VHT20_MCS0:-96dBm, 11ac VHT20_MCS11:-66dBm
11ac VHT40_MCS0:-94dBm, 11ac VHT40_MCS11:-63dBm
11ac VHT80_MCS0:-91dBm, 11ac VHT80_MCS11:-60dBm
11ac VHT160_MCS0:-88dBm, 11ac VHT160_MCS11:-55dBm
11ax HE20_MCS0:-95dBm, 11ax HE20_MCS11:-63dBm
11ax HE40_MCS0:-92dBm, 11ax HE40_MCS11:-60dBm
11ax HE80_MCS0:-89dBm, 11ax HE80_MCS11:-58dBm
11ax HE160_MCS0:-85dBm, 11ax HE160_MCS11:-55dBm

2.4 GHz:
11g 6Mbps:-97dBm, 11a 54Mbps:-79dBm
11n HT20_MCS0:-97dBm, 11n HT20_MCS7:-78dBm
11n HT40_MCS0:-95dBm, 11n HT40_MCS7:-75dBm
11ac VHT20_MCS0:-96dBm, 11ac VHT20_MCS11:-67dBm
11ac VHT40_MCS0:-94dBm, 11ac VHT40_MCS11:-64dBm
11ax HE20_MCS0:-96dBm, 11ax HE20_MCS11:-64dBm
11ax HE40_MCS0:-93dBm, 11ax HE40_MCS11:-61dBm

WiFi Transmission Power
CE:
<20dBm(2.4GHz)
<23dBm(5.15GHz~5.35GHz)
<30dBm(5.47GHz~5.725GHz)
FCC:
<30dBm(2.4GHz & 5.15GHz~5.825GHz)

droftarts

@Purgatorium Have you sent an M587 ... command to add your WiFi SSID to the list of known networks? If so, try deleting any existing networks with M587 S"*" then send M587 with your network SSID and password again. See https://docs.duet3d.com/en/How_to_guides/Getting_connected/Getting_connected_to_your_Duet#h-5-connect-duet-to-network

There's no obvious error in the M122 report saying that the WiFi module isn't working, just that it hasn't found anything to connect to. However, you are on the latest WiFi firmware, 2.2.0, while using an older version of RRF, 3.4.4. This should be okay, but we haven't tested backward compatibility of the WiFi firmware with old versions of RRF. I'd suggest updating the mainboard firmware to 3.5.4 https://github.com/Duet3D/RepRapFirmware/releases/tag/3.5.4
Copy "Duet2CombinedFirmware.bin" to the firmware folder of the SD card, then send M997 to the Duet to update.
This will also allow you to run a WiFi network scan, using M587.1 and M587.2, see https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m5871-start-network-scan, which should show if the WiFi module is working.

Setting up the WiFi as an access point is also another way to check the functionality of the WiFi module: https://docs.duet3d.com/en/User_manual/Machine_configuration/Networking#configuring-duet-in-wifi-access-point-mode

If the WiFi module has an external aerial, make sure it's plugged in properly.

Ian