Also, perhaps notably, I have been driving the motor current set at M906 Y4400 for this motor which drives a NEMA 34 moving a fairly hefty gantry.

Hello,

I have been running a 1HCL for about 6 months without issue.

Today, I made a change to the driver setup going from M569 P50.0 S1 D2 V5 to M569 P50.0 S1 D3 V1000. I also increased the microstepping to x64 for this motor.

Upon the first test print I noticed that it sounded "clunky" when it went to travel moves, and then I noticed the motor associated with this board was no longer moving. Paused print and saw that the indication on the board LEDs was the fast flashing as if the CAN connection failed.

I then power cycled and got "CAN Response Timeout". Then I tried jumping the CAN_RST, power on, wait 5 min, power down, remove jumper, and power up. Same issue: with timeout on communication. The blue "Fused" LED is on, but I have no red Status nor green LED. The red 12V LED is blinking very fast and dimly.

Any ideas on what else I can do? I am worried I am toast now, and also don't want to fry a replacement board if this config change caused the board to go bad somehow.

I have also replicated this issue with firmware version 3.5.4 using Orcaslicer GCODE. I was able to recover operation by toggling off "Exclude Objects"

Oddly, this was working fine for slicing normal STL files but occurred when I was running Orcaslicer's built-in pressure advance calibration tests.

@dc42 I hadn't taken a measurement from the bed previously. I just tried that out and you are correct, the EI3 shaper was able to cover the relevant frequencies for me on both the X/Y axes in addition to the Z resonance. There is some trade-off, but I will run some test prints next to see if the magnitude of the remaining vibration is worth worrying about.

Just adding for the record that this would be helpful for printers with large area beds. On my printer which is roughly 1x1x1m, I get a Z resonance that is similar to how a drum vibrates.

My solution now is go slow with Z motions, stiffen it up, etc.... But it would be nice to have a software firmware solution to help address this from the input side.

Hello,

I just experienced a mid-print failure associated with the message:

"Connection interrupted, attempting to reconnect...
DCS has been stopped"

My print was ~30% complete when this occurred, but the printer state was as if the print completed successfully: on the Job > Status page it had the option for Print Again, and the heaters were turned off. I checked the GCODE file and it looks fine, i.e. there is a full file worth of GCODE.

For context, I am running:

• Duet 3 MB6HC on SBC mode with Raspberry Pi 5
• Duet 3 Expansion Board 3HC
• Version 3.5.3 (stable) for each of the DWC, DSF, and MB6HC & EXP3HC boards

There is another thread from 4 years ago with the same issue but it seems it was marked as resolved with a new firmware revision.

I am now trying the print again now to see if I can replicate the behavior.