@Phaedrux I think I got it. Sometimes a change in the weather will accelerate oxidation between connections. I went through the screw connections, loosened them then tightened them. Boom, it connected and is reading everything. I will test it tomorrow.

@Phaedrux I discovered a problem with my PC reading the card. It was intermittently reading/not reading. I think I have solved the problem and will try again. Please disregard my last message. I will get back with you, once I know what is going on. Thank you

@Phaedrux It is working fine.

@droftarts I don't see the configuration tool, wth?

@droftarts No, my old card crapped out on me, so I'm starting fresh.

@droftarts
The reset must have been the answer. It is currently burning to the board.

@droftarts
Every time I formatted an SD card with the SD Card Formatter, My main PC said Windows wouldn't open it. So, I used Windows Formatter, not Quick.

@droftarts

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.6 (2023-07-21 14:08:28) running on Duet WiFi 1.02 or later
Board ID: 0JD2M-9F8TA-GJ4TJ-6JTD4-3S46T-16UL6
Used output buffers: 1 of 26 (1 max)
=== RTOS ===
Static ram: 23896
Dynamic ram: 73392 of which 0 recycled
Never used RAM 14792, free system stack 184 words
Tasks: NETWORK(ready,6.8%,513) HEAT(notifyWait,0.0%,388) Move(notifyWait,0.0%,363) MAIN(running,93.0%,602) IDLE(ready,0.2%,30), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:08:47 ago, cause: reset button or watchdog
Last software reset at 2023-10-17 18:21, reason: User, GCodes spinning, available RAM 12876, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Step timer max interval 0
MCU temperature: min 22.1, current 22.7, max 23.7
Supply voltage: min 24.3, current 24.3, max 24.4, 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 n/a
Driver 1: standstill, SG min n/a
Driver 2: standstill, SG min n/a
Driver 3: standstill, SG min n/a
Driver 4: standstill, 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: 4.44ms; fastest: 0.19ms
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.5ms, 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.29ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 0 of 8
= WiFi =
Interface state: disabled
Module is disabled
Failed messages: pending 0, notready 0, noresp 0
Socket states: 0 0 0 0 0 0 0 0
ok

@Phaedrux
M39
Error: M39: No SD card mounted in slot 0
ok

@Phaedrux
SD card 0 not detected, interface speed: 30.0MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0

@Phaedrux Please advise.

@Phaedrux

@Phaedrux I discovered a problem with my PC reading the card. It was intermittently reading/not reading. I think I have solved the problem and will try again. Please disregard my last message. I will get back with you, once I know what is going on. Thank you