@SIam
The only protocols available on this router range from Open System, WPA-WPA3 both personal and enterprise.
Should I look for specific events during the time frame I was trying to connect to my network?
@T3P3Tony
My router is the RT-AX82U. Running WPA2 under AES.
801.11ax is turned off for my 2.4GHZ network.
Wireless mode is set to auto (Not legacy or N), with b/g protection.
20/40Mhz channel.
Any other settings that would helpful for the SDK let me know.
I can confirm that I am using the correct password for "WuTangLan24". All my other devices accept no issue, but the duet likes to report a wrong password. I tried pinging but no luck; router shows having a max access time of 9 seconds but I don't think a connection is ever made.
I can turn off WPS for my "WuTangLan24", this changes the Duet response from "wrong password" to "failed connection".
I am using WPA2 personal for my networks.
Also, thank you for taking your time out to trouble shoot madness with me. I appreciate it.
Edit
Went ahead and connected my printer to my old router, just running it locally. Maybe a temporary fix, or will turn into a permanent fix since everything works this way. Lol.
No idea why my new router was so high, seemed a little questionable at 192.168.50.167. The new IP is 192.168.0.3
@t3p3tony
Connecting from IP 192.168.50.177
I connected to my old router's network, just couldn't complete a connection to the web interface. The Duet's IP at that time was 192.168.0.3.
@siam
I am using the RT-AX82U, I have tried auto channeling as well as trying out 5.
Thought I would get away with putting my old router in bridge mode but that has proven difficult.
This was while connected to my guest network.
Pinging 192.168.50.167 with 32 bytes of data:
Reply from 192.168.50.177: Destination host unreachable.
Reply from 192.168.50.177: Destination host unreachable.
Reply from 192.168.50.177: Destination host unreachable.
Reply from 192.168.50.177: Destination host unreachable.
Ping statistics for 192.168.50.167:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Pinging 192.168.50.167 with 32 bytes of data:
Also
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Awh no luck with this method of reflash of M588. Even reinstalled firmware. Interesting enough I changed my main 2.4 network to enable WPS. I no longer get "Failed while trying to connect to WuTangLan24", it is now "Wrong password while trying to connect to WuTangLan24".
I am not to sure what is meant by pinging?
@siam I don't see any major differences. Intranet access is disabled on my guest network. But changing it doesn't seem to have effect.
@t3p3tony Looks like all the IPs im using are 192.168.50.nnn or .nn
Here is the terminal after connecting to my guest network. IP Address does not pull up the web interface.
WiFi: sleep enable,type: 2
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 20
WiFi: cnt
WiFi:
WiFi: connected with WuTangGuest, channel 9
WiFi: dhcp client start...
WiFi: wifi evt: 0
WiFi: ip:192.168.50.167,mask:255.255.255.0,gw:192.168.50.1
WiFi module is connected to access point WuTangGuest, IP add
ress 192.168.50.167
WiFi: wifi evt: 3
WiFi: pm open,type:2 0
WiFi: sleep enable,type: 2
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 20
WiFi: cnt
WiFi:
WiFi: connected with WuTangGuest, channel 9
WiFi: dhcp client start...
WiFi: wifi evt: 0
WiFi: ip:192.168.50.167,mask:255.255.255.0,gw:192.168.50.1
WiFi module is connected to access point WuTangGuest, IP add
ress 192.168.50.167
WiFi: wifi evt: 3
WiFi: pm open,type:2 0
@siam Yeah I changed it all to WPA2 after issues with WPA3.
@siam 100%. Even changed it briefly to something simple.
Connections to my guest network have no issue, however. Just cannot connect to the web interface after that.
=== Diagnostics ===<LF>RepRapFirmware for Duet 2 WiFi/Ethernet
version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02
or later<LF>Board ID: 08DJM-9178L-L2MS8-6JKDA-3S86K-K8G2N<LF>Used
output buffers: 1 of 24 (13 max)<LF>=== RTOS ===<LF>Static ram: 23
876<LF>Dynamic ram: 75352 of which 0 recycled<LF>Never used RAM 15
188, free system stack 185 words<LF>Tasks: NETWORK(ready,6.7%,3
40) HEAT(delaying,0.0%,330) Move(notifyWait,0.1%,364) MAIN(r
unning,93.2%,439) IDLE(ready,0.0%,29), total 100.0%<LF>Owned mu
texes: USB(MAIN)<LF>=== Platform ===<LF>Last reset 00:02:32 ago, c
ause: power up<LF>Last software reset at 2021-09-19 13:42, reas
on: User, GCodes spinning, available RAM 12332, slot 1<LF>Softw
are reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0
x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0
n/a<LF>Error status: 0x00<LF>Aux0 errors 0,0,0<LF>Step timer max inte
rval 0<LF>MCU temperature: min 31.4, current 32.2, max 34.7<LF>Sup
ply voltage: min 0.4, current 0.5, max 0.6, under voltage ev
ents: 0, over voltage events: 0, power good: no<LF>Heap OK, han
dles allocated/used 0/0, heap memory allocated/used/recyclab
le 0/0/0, gc cycles 0<LF>Driver 0: position 0, ok, SG min/max n
ot available<LF>Driver 1: position 0, ok, SG min/max not availa
ble<LF>Driver 2: position 0, ok, SG min/max not available<LF>Drive
r 3: position 0, ok, SG min/max not available<LF>Driver 4: posi
tion 0, ok, SG min/max not available<LF>Driver 5: position 0<LF>Dr
iver 6: position 0<LF>Driver 7: position 0<LF>Driver 8: position 0
<LF>Driver 9: position 0<LF>Driver 10: position 0<LF>Driver 11: posit
ion 0<LF>Date/time: 1970-01-01 00:00:00<LF>Cache data hit count 42
94967295<LF>Slowest loop: 3.00ms; fastest: 0.12ms<LF>I2C nak error
s 0, send timeouts 0, receive timeouts 0, finishTimeouts 0,
resets 0<LF>=== Storage ===<LF>Free file entries: 10<LF>SD card 0 det
ected, interface speed: 20.0MBytes/sec<LF>SD card longest read
time 0.4ms, write time 0.0ms, max retries 0<LF>=== Move ===<LF>DMs
created 83, maxWait 0ms, bed compensation in use: none, com
p offset 0.000<LF>=== MainDDARing ===<LF>Scheduled moves 0, comple
ted moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns
[0, 0, 0], CDDA state -1<LF>=== AuxDDARing ===<LF>Scheduled moves
0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, U
nderruns [0, 0, 0], CDDA state -1<LF>=== Heat ===<LF>Bed heaters =
0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1<LF>=== GCodes ===<LF>Seg
ments left: 0<LF>Movement lock held by null<LF>HTTP is idle in sta
te(s) 0<LF>Telnet is idle in state(s) 0<LF>File is idle in state(s
) 0<LF>USB is ready with "m122" in state(s) 0<LF>Aux is idle in st
ate(s) 0<LF>Trigger is idle in state(s) 0<LF>Queue is idle in stat
e(s) 0<LF>LCD is idle in state(s) 0<LF>Daemon is idle in state(s)
0<LF>Autopause is idle in state(s) 0<LF>Code queue is empty.<LF>=== N
etwork ===<LF>Slowest loop: 0.61ms; fastest: 0.00ms<LF>Responder s
tates: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 s
essions<LF>HTTP sessions: 0 of 8<LF>- WiFi -<LF>Network state is chan
gingMode<LF>WiFi module is trying to connect<LF>Failed messages: p
ending 0, notready 0, noresp 0<LF>WiFi firmware version 1.26<LF>Wi
Fi MAC address ec:fa:bc:5b:42:ca<LF>WiFi Vcc 3.35, reset reason
Turned on by main processor<LF>WiFi flash size 4194304, free h
eap 28776<LF>Clock register 00002002<LF>Socket states: 0 0 0 0 0 0
0 0<LF>ok<LF>WiFi reported error: Wrong password while trying to
connect to WuTangLan24<LF>WiFi module is idle<LF>WiFi reported err
or: Wrong password while trying to connect to WuTangLan24<LF>Wi
Fi module is idle<LF>WiFi reported error: Wrong password while
trying to connect to WuTangLan24<LF>WiFi module is idle<LF>WiFi re
ported error: Wrong password while trying to connect to WuTa
ngLan24<LF>WiFi module is idle<LF>WiFi reported error: Wrong passw
ord while trying to connect to WuTangLan24<LF>WiFi module is id
le<LF>WiFi reported error: Wrong password while trying to conne
ct to WuTangLan24<LF>WiFi module is idle<LF>WiFi reported error: W
rong password while trying to connect to WuTangLan24<LF>WiFi mo
dule is idle<LF>WiFi reported error: Wrong password while tryin
g to connect to WuTangLan24<LF>WiFi module is idle<LF>WiFi reporte
d error: Wrong password while trying to connect to WuTangLan
24<LF>WiFi module is idle<LF>
@siam I'd like to make it easy! 
I believe there are no restrictions. Other devices can connect with ease.
@siam I have followed that documentation. I've cleared all remembered networks, so that M587 only shows the 2.4 GHZ network that my duet cannot establish a connection with. Under my router interface "Espressif Inc" will make a connection for about 3 seconds before reattempting.
I recently made hardware changes for my network and now having issues getting to my web interface. There isn't any issue connecting my Duet to a guest network, but it will not allow me to connect to the web interface via IP. Is this because local network access is restricted on guest networks?
Additionally, no connection can be established to my main 2.4GHZ network. Changing password/ssid still yields "Wrong Password" on YAT. I've disabled WiFi 6 on this network but no luck.
Any ideas?
Culprit found. Power input voltage was set to 230V, switched to 115V. Heaters can carry full PWM now.
@Phaedrux That I do not know. I am using a Meanwell 24V, 18.8A PSU.
@Phaedrux Yup, thats it! The console mentioned it could reach 365 something.
There seems to be an issue running both heaters. Back to getting hard shutdowns. Will double check all my connections just to be sure...
Thank you! Both the PID tuning for the bed and hotend are complete.
The bed is running at 40% PWM to avoid the soft shutdown. Also has some electrical noise during heating.
I've read about thermal coupling to prevent runaway. In regarding to the warning in the console messages about potential temperature increase. How serious is this?
Right, my bed heater is connected correctly same as my bed temp. Went to run bed PID tune next. Not a complete shutdown like the hotend, but as if e-stop was pressed.
M303 H0 S70 using values
M308 S0 P"bedtemp" Y"thermistor" T100000 B3988 C0 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
M307 H0 B0 S0.20 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0