@Veti Yes currently running 3.2. The beg.g was created by the configurator.
m112 output
m122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.2 running on Duet 3 Mini5plus WiFi (SBC mode)
Board ID: MDHLF-5296U-D65J0-40KM0-2G03Z-RL674
Used output buffers: 1 of 40 (16 max)
=== RTOS ===
Static ram: 98732
Dynamic ram: 95016 of which 36 recycled
Never used RAM 51432, free system stack 192 words
Tasks: Linux(blocked,120) HEAT(blocked,316) CanReceiv(blocked,947) CanSender(blocked,372) CanClock(blocked,363) TMC(blocked,104) MAIN(running,489) IDLE(ready,20) AIN(blocked,267)
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:01:20 ago, cause: power up
Last software reset at 2021-01-12 22:17, reason: User, GCodes spinning, available RAM 51224, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task Linu Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
Supply voltage: min 0.0, current 23.8, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position 64133, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 11, reads 11547, writes 11, timeouts 0, DMA errors 0
Driver 1: position 64133, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 11, reads 11547, writes 11, timeouts 0, DMA errors 0
Driver 2: position 64133, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 11, reads 11547, writes 11, timeouts 0, DMA errors 0
Driver 3: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 11, reads 11546, writes 11, timeouts 0, DMA errors 0
Driver 4: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 9, reads 11549, writes 9, timeouts 0, DMA errors 0
Driver 5: position 0, assumed not present
Driver 6: position 0, assumed not present
Date/time: 2021-01-13 06:08:06
Cache data hit count 207678856
Slowest loop: 3.30ms; fastest: 0.10ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 0.0MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP* is doing "M122" in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle 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
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== CAN ===
Messages queued 653, send timeouts 651, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 16
=== SBC interface ===
State: 4, failed transfers: 0
Last transfer: 4ms ago
RX/TX seq numbers: 2215/2215
SPI underruns 0, overruns 0
Number of disconnects: 0, IAP RAM available 0x10eec
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.2.0
Code buffer space: 4096
Configured SPI speed: 8000000 Hz
Full transfers per second: 0.08
Maximum length of RX/TX data transfers: 2952/952
This from a fresh power on. Not sure if that makes any difference.
Thanks again for the assistance.