I should have changed hardware then upgraded firmware, but I wasn't concerned as I've done both pretty easily in the past. This hardware config has only been tested in 3.4.
m122
=== Diagnostics ===
RepRapFirmware for Duet 2 Maestro version 3.4.0rc1 (2022-02-09 10:28:41) running on Duet Maestro 1.0
Board ID: 08DAM-9F9GA-J24TD-6JKD0-3S86R-KP3UT
Used output buffers: 3 of 24 (24 max)
=== RTOS ===
Static ram: 23628
Dynamic ram: 65660 of which 216 recycled
Never used RAM 24840, free system stack 156 words
Tasks: NETWORK(ready,28.4%,263) HEAT(notifyWait,0.1%,300) Move(notifyWait,0.0%,326) TMC(notifyWait,1.3%,116) MAIN(running,70.2%,494) IDLE(ready,0.0%,31), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 21:38:29 ago, cause: software
Last software reset at 2022-02-21 17:58, reason: User, GCodes spinning, available RAM 25188, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x04
Aux0 errors 0,0,0
Step timer max interval 940
MCU temperature: min 27.9, current 28.8, max 29.4
Supply voltage: min 14.0, current 14.1, max 14.1, 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: 1 queued, 1 completed
Driver 0: pos 21170, standstill, read errors 0, write errors 0, ifcnt 69, reads 2845, writes 5, timeouts 0, DMA errors 0, CC errors 0
Driver 1: pos 21170, standstill, read errors 0, write errors 0, ifcnt 69, reads 2845, writes 5, timeouts 0, DMA errors 0, CC errors 0
Driver 2: pos 21170, standstill, read errors 0, write errors 0, ifcnt 69, reads 2845, writes 5, timeouts 0, DMA errors 0, CC errors 0
Driver 3: pos 0, standstill, read errors 0, write errors 0, ifcnt 61, reads 2850, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 4: pos 0, standstill, read errors 0, write errors 0, ifcnt 55, reads 2850, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 5: pos 0, not present
Driver 6: pos 0, not present
Date/time: 2022-02-22 15:37:17
Slowest loop: 11.28ms; fastest: 0.15ms
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: 15.0MBytes/sec
SD card longest read time 0.7ms, write time 1.1ms, max retries 0
=== Move ===
DMs created 83, segments created 6, maxWait 77518183ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 10, completed 10, hiccups 2, 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 0 -1, chamber heaters -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 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== Network ===
Slowest loop: 24.80ms; fastest: 0.05ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8
Interface state active, link 100Mbps full duplex
2/22/2022, 3:39:58 PM M98 P"config.g"
HTTP is enabled on port 80
FTP is enabled on port 21
TELNET is enabled on port 23
Warning: Heater 0 predicted maximum temperature at full power is 265°C
Ran the M98 after system was idle all day, thermistor hit 65°, then 90° within two refreshes, then output the error below. Five minutes later, it's dropping below 35° and will probably normalize at room temp
2/22/2022, 3:40:12 PM Error: Heater 0 fault: exceeded allowed temperature excursion: target 125.0°C actual 69.0°C