Using te Duet Ecosystem
-
I am currently in the beginning stages of designing a custom large format 3d printer for my job (the goal is a cartesian style 1m^3 volume). I have been messing with 3d printers for a couple of years now but have not taken this deep of a dive just yet. I currently have a modified Reborn 2 that runs Klipper on an orange Pi and a stock Prusa minus Revo nozzles. I plan to replace the board on both of these printers to get more familiar with whatever style I go with. I am not familiar with rep-rap firmware at all, but I am open to switching to it instead of Klipper if the overall ecosystem is better or If I can run Klipper on these boards that would be fine too. I would like to have all of the printers on the same style Mainboard and firmware.
I also have a ton of plans for the future when I finish up engineering school next year. I have already gathered a bunch of components for a DIY CNC Knee Mill and Router. I have done some preliminary research, but not too much as my free time is pretty limited. I have seen Duet boards on a lot more of the larger format printers and CNC projects. Is there any information/ advice anyone would be willing to share that can convince me to go with these boards for each one of these projects? I do like the expansion capabilities of the duet ecosystem and would like to try and future proof all of my projects by using a module style of designing. I would like everything that to be CAN based if possible so I can swap out or add modules easily for whatever random thing I decide to build or next. I do this in the motorsports industry I work in, and this is a very solid design approach for projects that change a lot and get damaged a lot.
-
There are a lot of good reasons to choose a Duet and RepRapFirmware. The hardware is very capable and varied. CanBus expansion can be very useful on larger printers by simplifying wire runs. The firmware is very flexible and favours user control. Configuration is done in real time, so it's very nice to work with when building a new printer. Conditional gcode basically gives you a programming language to automate and customize your printer with as much complexity as you need. And you've got warranty and support.
Some links to get you started.
https://docs.duet3d.com/en/Duet3D_hardware/Hardware_overview
https://docs.duet3d.com/User_manual/RepRapFirmware/RepRapFirmware_overview
https://docs.duet3d.com/User_manual/Reference/Duet_Web_Control_Manual
https://docs.duet3d.com/en/User_manual/Machine_configuration/CAN_connection
https://docs.duet3d.com/en/User_manual/Reference/Gcode_meta_commands -
@Phaedrux Thank you for the response! From my understanding, the Duet Boards appear to be a good cross between a hobbyist level and industrial level controller. I really like the CAN FD communication available and will be doing a lot more research into incorporating these boards to my various projects. I am glad that there is Input shaping available on the RRF as I really do like that feature on my Klipper powered printer. It will be interesting to see the differences when I change the firmware (if there are any that are noticeable). I mostly decided to start looking at this firmware for the Duet Ecosystem and not really liking the other options from BTT and Mellow, I had previous printers and helped some co workers with their printers that used these boards and they appeared to be suited primarily for hobbyist level and support was not very good. Thanks again!
-
@Ktorty429, support for RRF and Duet is absolutely the best and that alone makes the Duet ecosystem the clear choice!
-
@jens55 said in Using te Duet Ecosystem:
@Ktorty429, support for RRF and Duet is absolutely the best and that alone makes the Duet ecosystem the clear choice!
Very much so. To the point that the hardware and software designers are accessible here.
