@diy-o-sphere Huh, yeah that ain't right

@fcwilt I'm currently re-running the autotuning with the removed T, B, and C values from the config

@fcwilt it included M307 commands that were generated from the autotuning and saved using M500

@fcwilt Affirmative

@fcwilt Yes, all 3 faulted (nearly) simultaneously, when heating is initiated simultaneously

@fcwilt "Print will be terminated if a heater fault is not reset within 10 minutes"

The thing that keeps confusing me is that this is a very standard-issue setup. Running all standard E3D + Duet hardware, and running a stable release of the firmware.

@fcwilt Yes, toolboards are at the addresses assigned

@phaedrux Ask and you shall receive

@fcwilt It's a printer with 4 tools, just so happened that the 4th tool continued heating to ~120C before faulting (different M307 parameters). All 4 tools have the issue

@dc42 Yep! That did it!
Silly me

@dc42 I have provided more detailed information above

@gloomyandy I cannot access the machine immediately after the incident, but now that I've changed the config and booted it back up, here's the output

=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.0beta7+7 (2022-01-14 08:57:59) running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-9P63L-DJ3T8-6JKDD-3SD6M-9V4Z9
Used output buffers: 1 of 40 (18 max)
=== RTOS ===
Static ram: 150968
Dynamic ram: 66704 of which 0 recycled
Never used RAM 133000, free system stack 200 words
Tasks: SBC(ready,0.9%,468) HEAT(notifyWait,0.0%,341) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.1%,797) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,351) TMC(notifyWait,7.6%,92) MAIN(running,91.4%,923) IDLE(ready,0.0%,30), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:00:10 ago, cause: software
Last software reset at 2022-01-16 13:49, reason: User, GCodes spinning, available RAM 133000, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
Step timer max interval 182
MCU temperature: min 31.6, current 31.8, max 31.8
Supply voltage: min 24.0, current 24.0, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.1, max 12.1, under voltage events: 0
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: pos 0, standstill, SG min n/a, mspos 8, reads 5698, writes 0 timeouts 0
Driver 1: pos 0, standstill, SG min n/a, mspos 8, reads 5698, writes 0 timeouts 0
Driver 2: pos 0, standstill, SG min n/a, mspos 8, reads 5698, writes 0 timeouts 0
Driver 3: pos 0, standstill, SG min n/a, mspos 8, reads 5698, writes 0 timeouts 0
Driver 4: pos 0, standstill, SG min n/a, mspos 8, reads 5697, writes 0 timeouts 0
Driver 5: pos 0, standstill, SG min n/a, mspos 8, reads 5698, writes 0 timeouts 0
Date/time: 2022-01-16 13:49:37
Slowest loop: 1.63ms; fastest: 0.06ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, 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 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== 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 9, received 80, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 173, free buffers 50 (min 50), ts 5/5/0
Tx timeouts 0,0,0,0,0,0
=== SBC interface ===
Transfer state: 4, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 1016/1016
SPI underruns 0, overruns 0
State: 5, disconnects: 0, timeouts: 0, IAP RAM available 0x2bd70
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.4-b5
Code buffer space: 4096
Configured SPI speed: 8000000Hz
Full transfers per second: 40.84, max wait times: 33.8ms/0.1ms
Codes per second: 1.00
Maximum length of RX/TX data transfers: 4526/1248```

@pcr also, P"type" Type of input shaping to use, not case sensitive.

@pcr it was lowercase when I ran it lol
just made it uppercase when I rewrote it for the forum

@kevinmar I was able to revert the config.g

attached is the problematic config.g
config - MZV problem.g

Being ran on a Duet 6HC with a Pi 4b SBC

@dc42 I put "M593 P"zvd"" at the end of my config.g and now my printer cannot be accessed via DWC

@kevinmar Downgraded to 3.4.0Beta6 and the same behavior was noticed

MZV and ZVDDD input shaping commands cause my Duet 6HC to crash.

I'm attempting to use MZV input shaping on my 6HC, but any command containing "M593 P"mzv"" causes DWC to go offline, and the printer becomes unresponsive.
I have tried using 3.4.0Beta7 and 3.4.0RC1 and the problem persists between the 2.

Other input shaping methods work just fine.

Why would an Emergency Stop yield different results than a config save or a power on startup?