Linuxcnc and 3d Printing - Configs/comps/examples

Thanks for the tips guy's. I will see what I can come up with.

Who has this working end to end ? if so, please share, I'm on my 3rd bigtree motherboard, they keep dying, and I've been through this damn printer repeatedly. to my untrained eye, seems like back emf from the steppers is beating the drivers into oblivion, I have on hand

6 stepper drivers, 1 5i25 and 1 7i76d and the guts from a creality, yes my printer runs a lot, I am sick of putting parts in it all the time.

had no idea this was even a option till today.

I know that people have used LinuxCNC for 3D printing.

And I fully planned to when I bought my printer years ago, but then I just started printing things with the supplied Sailfish firmware....

Yeah, I did that too but after 4 motherboards in 3 yrs, I'm ready to build something beefy that will last a long time.

happily found Duet3 to be powerful enough to drive the steppers of my mill. As a Linux enthusiast I am very happy about LinuxCNC and would like to use this via the Duet board to control my motors, i.e. also with LinuxCNC-generated G-code. Already done?
What I had in mind was to tap into your communication with the RPi and find (preferred) or implement (if you allow) an interface in analogy to what LinuxCNC has with the MESA cards, or better, that mimics how you talk to the driver chip. Any such interface could then be used for arbitrary other projects, be it marble machines or some other person may think that MIDI is the ultimate language and then uses your board to drive his violin. For some initial benchmarking that I had in mind, comparing G-code of the current still original setup with your 15 years younger drivers, your board will be fine as it is, so I can start, but the summer I hope to bring a LinuxCNC-based solution.

The Duet3 might not be a good fit for LinuxCNC as-is. Though with different firmware it would offer a good selection of features at a decent price.

The issue is that LinuxCNC is a CNC controller. And the Reprap firmware that the Duet is intended to run is _also_ a CNC controller. So the Duet tries to do a _lot_ more than LinuxCNC expects.

Now, with a simplified firmware on the Duet that simply accepted stepper motor positions (and other IO commands) sent digitally every 1mS, it would probably work rather nicely.