I am pretty sure the network was 2.4GHz. I’ll double check with the admin when they change the password. Because of Covid restrictions, it may be a while before I am actually able to test anything out.

I was sending the gcode commands using YAT, which I believe can send lowercase characters.

@Phaedrux
It worked! Not a permanent solution, but it’s good to see some progress. I’ll stil try to get that password changed. Thanks for your help

@Phaedrux
I am trying access point mode currently
I input: M589 S"NetworkName" P"Password" lnnn.nn.nn
It returns: M589: Bad or missing parameter
The WiFi module is Idle. I think that the part I am messing up on is the IP. I am pretty new to this, can the IP be just any random numbers, or is there a format it has to follow?

Alright, I'll try that. It's not my personal network so I'll have to contact someone to change it, which may take a while. I'll post back here if it does (or doesn't) work

Looks like I was mistaken. The WiFi Firmware is actually 1.23

@bearer
The output for M587 is:

Remembered networks:
Diabase IP=0.0.0.0 GW=0.0.0.0 NM=0.0.0.0
ok

The password does have the ! $ @ sybols in it

M122<CR>
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1-diabase running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DGM-917NK-F23T0-6JKF8-3SJ6P-TZ8NG
Used output buffers: 1 of 24 (24 max)
=== RTOS ===
Static ram: 26128
Dynamic ram: 95004 of which 0 recycled
Exception stack ram used: 352
Never used ram: 9588
Tasks: NETWORK(ready,1100) HEAT(blocked,1232) DUEX(suspended,144) MAIN(running,4120) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:05:22 ago, cause: power up
Last software reset time unknown, reason: Heat task stuck, spinning module Platform, available RAM 9280 bytes (slot 3)
Software reset code 0x00a0 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0040080f BFAR 0xe000ed38 SP 0x20004954 Task 0x4e49414d
Stack: 0044f997 0044f778 61000000 3f800000 3fdb4e81 00000000 00000000 3331bb4c 41880000 3e178897 3e1cd04f bda02214 3e3a3498 3e638fa9 3e924a09 3bc8553b c0a00000 3f800000 3f800000 20000010 ffffffff 20009354 00000000
Error status: 4
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 28.7, current 32.5, max 32.8
Supply voltage: min 0.6, current 0.7, max 0.7, under voltage events: 0, over voltage events: 0, power good: no
Driver 0: ok, SG min/max not available
Driver 1: ok, SG min/max not available
Driver 2: ok, SG min/max not available
Driver 3: ok, SG min/max not available
Driver 4: ok, SG min/max not available
Driver 5: ok, SG min/max not available
Driver 6: ok, SG min/max not available
Driver 7: ok, SG min/max not available
Driver 8: ok, SG min/max not available
Driver 9: ok, SG min/max not available
Date/time: 1970-01-01 00:00:00
Cache data hit count 533347494
Slowest loop: 100.12ms; fastest: 0.05ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = -1 -1 -1 -1, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Stack records: 2 allocated, 0 in use
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
serial is ready with "M122" in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 1.25ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 0 of 8

• WiFi -
  Network state is running
  WiFi module is idle
  Failed messages: pending 0, notready 0, noresp 0
  WiFi firmware version 1.23
  WiFi MAC address ec:fa:bc:02:18:54
  WiFi Vcc 3.45, reset reason Turned on by main processor
  WiFi flash size 4194304, free heap 30176
  Socket states: 0 0 0 0 0 0 0 0
  ok

=== Diagnostics ===<LF>RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1-diabase running on Duet WiFi 1.02 or later + DueX5<LF>Board ID: 08DGM-917NK-F23T0-6JKF8-3SJ6P-TZ8NG<LF>Used output buffers: 1 of 24 (24 max)<LF>=== RTOS ===<LF>Static ram: 26128<LF>Dynamic ram: 95004 of which 0 recycled<LF>Exception stack ram used: 352<LF>Never used ram: 9588<LF>Tasks: NETWORK(ready,1100) HEAT(blocked,1232) DUEX(suspended,144) MAIN(running,4120) IDLE(ready,160)<LF>Owned mutexes:<LF>=== Platform ===<LF>Last reset 00:05:22 ago, cause: power up<LF>Last software reset time unknown, reason: Heat task stuck, spinning module Platform, available RAM 9280 bytes (slot 3)<LF>Software reset code 0x00a0 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0040080f BFAR 0xe000ed38 SP 0x20004954 Task 0x4e49414d<LF>Stack: 0044f997 0044f778 61000000 3f800000 3fdb4e81 00000000 00000000 3331bb4c 41880000 3e178897 3e1cd04f bda02214 3e3a3498 3e638fa9 3e924a09 3bc8553b c0a00000 3f800000 3f800000 20000010 ffffffff 20009354 00000000<LF>Error status: 4<LF>Free file entries: 10<LF>SD card 0 detected, interface speed: 20.0MBytes/sec<LF>SD card longest block write time: 0.0ms, max retries 0<LF>MCU temperature: min 28.7, current 32.5, max 32.8<LF>Supply voltage: min 0.6, current 0.7, max 0.7, under voltage events: 0, over voltage events: 0, power good: no<LF>Driver 0: ok, SG min/max not available<LF>Driver 1: ok, SG min/max not available<LF>Driver 2: ok, SG min/max not available<LF>Driver 3: ok, SG min/max not available<LF>Driver 4: ok, SG min/max not available<LF>Driver 5: ok, SG min/max not available<LF>Driver 6: ok, SG min/max not available<LF>Driver 7: ok, SG min/max not available<LF>Driver 8: ok, SG min/max not available<LF>Driver 9: ok, SG min/max not available<LF>Date/time: 1970-01-01 00:00:00<LF>Cache data hit count 533347494<LF>Slowest loop: 100.12ms; fastest: 0.05ms<LF>I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0<LF>=== Move ===<LF>Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms<LF>Bed compensation in use: none, comp offset 0.000<LF>=== DDARing ===<LF>Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0<LF>=== Heat ===<LF>Bed heaters = -1 -1 -1 -1, chamberHeaters = -1 -1<LF>=== GCodes ===<LF>Segments left: 0<LF>Stack records: 2 allocated, 0 in use<LF>Movement lock held by null<LF>http is idle in state(s) 0<LF>telnet is idle in state(s) 0<LF>file is idle in state(s) 0<LF>serial is ready with "M122" in state(s) 0<LF>aux is idle in state(s) 0<LF>daemon is idle in state(s) 0<LF>queue is idle in state(s) 0<LF>autopause is idle in state(s) 0<LF>Code queue is empty.<LF>=== Network ===<LF>Slowest loop: 1.25ms; fastest: 0.00ms<LF>Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)<LF>HTTP sessions: 0 of 8<LF>- WiFi -<LF>Network state is running<LF>WiFi module is idle<LF>Failed messages: pending 0, notready 0, noresp 0<LF>WiFi firmware version 1.23<LF>WiFi MAC address ec:fa:bc:02:18:54<LF>WiFi Vcc 3.45, reset reason Turned on by main processor<LF>WiFi flash size 4194304, free heap 30176<LF>Socket states: 0 0 0 0 0 0 0 0<LF>ok<LF>

Hi, this is first time trying to connect to a Duet boards, but I have been trying for several hours and I feel like I am running out of ideas. For context, the board is a Duet Wifi 2 and it is already connected to a printer. I have seen the printer running before, but I have no experience running it and the printer has just been sitting on a shelf during quarantine. I am connected to the printer over USB. I am using YAT. I can toggle the Wifi module with M552 S0 and M552 S-1. Running M552 reveals the wifi module is idle. I can run M587 S"Network" P"Password" and it responds "ok". Earlier I cleared all the networks and was able to add this one back on successfully. When I input M552 S1, I get:

ok<LF>WiFi reported error: no known networks found<LF>WiFi module is idle<LF>

I am not really sure where to go from here. My network is at 2.4 GHz. My firmware is version 2.05.1 and my WiFiServer is version 1.25. I do not think the board itself is faulty, but it has not been used in a few months. Any help is appreciated.