@Phaedrux

Culprit found. Power input voltage was set to 230V, switched to 115V. Heaters can carry full PWM now.

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

@siam @T3P3Tony

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.

@t3p3tony

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

@siam
@T3P3Tony

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.