[3.4.0Beta7/RC1] MZV and ZVDDD Causing Firmware Crash

KevinMar

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.

KevinMar

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

gloomyandy

@kevinmar I don't think RC1 has been released yet, so I assume you are using the various beta7+ test builds? Posting the following would probably help to work out what is going on...

Your config.g file
A step by step guide to what you do to cause the problem
The output from M122 after your system has become unresponsive and you have restarted it.

oliof

I used ZVDDD and MZV on 3.4beta7+6 successfully on a duet 3 mini 5+ yesterday

dc42

@kevinmar please provide your config.g file and tell us which h Duet you have.

KevinMar

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

KevinMar

@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

PCR

@kevinmar hmm in the config it's upper case... Has to be lower

KevinMar

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

KevinMar

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

gloomyandy

@kevinmar Can you post the output from m122 if the firmware is crashing this should provide some clues as to what is happening.

KevinMar

@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```

KevinMar

@dc42 I have provided more detailed information above

droftarts

@kevinmar are you using an F parameter in your M593 command, for the frequency you want to cancel? Input shaping won’t work without it. See https://duet3d.dozuki.com/Wiki/M593

Ian

sebkritikel

@droftarts May not apply here, looking at Kevin's troublesome config.g, 'M593 P"mzv" F36' is used.

dc42

@KevinMar it looks like you are using Duet Control Server 3.4b5 instead of 3.4b7. Please upgrade it via the package server.

KevinMar

@dc42 Yep! That did it!
Silly me