Best posts made by LeonMF

Posted in a separate comment for clarity.

Some time ago, I used to run my home automation system on Raspberry Pi. Then, after that, I ran my home audio on Raspberry Pis. They did work pretty well but were more prone to corruption than I'd like.

The beauty of an embedded board like the Duet 2 is that powering it down and back up meant that it was still going to come back up fine.

My experience with Raspberry Pis were that they are a full OS and don't particularly love being shut down without going through a clean shutdown. Something that a device with an off-switch isn't all that great for. Perhaps my early experiences with Raspberry Pis reflect a fear about dirty shutdown corruption that isn't a reality any more. Do I have any reason to be concerned on this or are my fears several years out of date?

@oliof said in Weird extrusion issue:

@LeonMF These artefacts look like Bang-Bang induced bed displacement artefacts. I guess you are using an SSR with an AC bed. If its not a zero crossing SSR, get a better SSR, and try to reduce the SSR frequency (I had luck with 1Hz in the past, but it depends on your SSR).

I'm embarrassed to admit that I defaulted to bang-bang after my last printer caused problems. I never considered it an issue as I wasn't aware that bed stability of a degree or two would be that much of a big deal. I PID tuned this printer and do not have flickering lights. It also seems to have solved my problems.

Ignore the first layer, I was a bit far away.

I have more testing to do but the preliminary results here look good.

Thank you!

Here are some videos highlighting the issue:

Duet Power off free-fall:
https://youtu.be/WCvHGXi6jxs

Duet Power On Free-Fall
https://youtu.be/7uG-6czPOVY

Duet Bed Stall crash
https://youtu.be/QH9c-w1Nbgg

Defining U in config.g before then combining worked for me. Thanks for the help!

@dc42 The information that the macros revert to previous mode was key.

I just added an extra M83 in my slicer start script after my macro call and removed all the superfluous M83s that I had added to the startcode. That does mean an M83 followed by an M83 but it seems to work.

If you need I can do some extra testing but, for now I seem to be working fine.

Thanks!

@dc42 said in Duet Maestro Freefall:

M569 P2 D2

Also, thank you everyone for the help. You've helped a whole community of users who were struggling with this issue!