Duet 2, Duet3, RRF future
-
Still in the process of designing a fresh high-temperature capable cartesian IDEX printer with 2 extruders. Not too much in a hurry. At a certain moment the question 'what control board to choose?' also comes up, especially because I need something to run test setups (I plan to build parts, test them in the climate chamber, and evalueate) also and I have no spare control electronics.
I want to stay with Duet; I like the quality and performance of my Duet2, I like the RRF+DWC combination and I like the quick response to issues, not seldom from dc42 himself.
I need 7 or 8 nothing-special stepper channels to drive the axes and extruders, 2 extruder heaters, SSD control of the bed heater, 2x Pt100 for the hotends, the usual I/O for limit switches and probes and chamber heater; either SSR controlled by Duet or a control signal to an external solution.
I would like to have the connection to an SBC; I cannot put my current setup in a car and put the printer to work elsewhere; RPi talks to Duet2 over Wifi and both are dependant on the Wifi AP and DNS/DHCP server of my 'garage IT infrastructure'. Also, I like the Sindarius 3D G-code viewer plugin to make sure recurring prints are actually the correct one and a higher download speed to the browser would be welcome.
For what I don't want: electronics in the build chamber are a no-go.
Now, Duet 2 seems the best matching candidate. There is simply nothing wrong with that board. I can have my 8 stepper channels if that proves to be required, plenty of I/O capabilities, SBC connection can be done, and Duet2+DueX5 is approximately 100 euros cheaper than Duet3 6HC+3HC. It is not a dealbreaker, but I don't see the advantages of Duet3 6HC yet.
The new kid Duet3 Mini 5 seems useable too if I can keep it at 7 stepper channels, but it seems more limited in I/O than Duet2 and the price difference is not enough to make that a deciding factor..
But then there is firmware. RRF has evolved nicely lately, which I like. I do use conditional G-code and the daemon task, for example. But all those extra bells and whistles take extra flash space and CPU cycles.
How far are we from the point where the RRF feature set for Duet2 is going to differ from the newer boards? -
RPi talks to Duet2 over Wifi and both are dependant on the Wifi AP and DNS/DHCP server of my 'garage IT infrastructure'.
you could make the pi a client of the duet wifi, or the other way around, and also have the pi connet to your garage wifi if available with some tinkering.
How far are we from the point where the RRF feature set for Duet2 is going to differ from the newer boards?
thats an interesting question, I've been on the fence weather or not to employ a maestro board thats on the shelf for the same reason, and i think the maestro will be the first to be dropped from future features or even builds at some point in the future as it has the lowest specs.
-
you could make the pi a client of the duet wifi, or the other way around, and also have the pi connet to your garage wifi if available with some tinkering.
I know, and also have the Duet connect to the Pi over Wifi and route traffic from the Ethernet to the Duet. Or spend a few bucks on a simple wifi router (If you are not already given a truckload of used ones when asking around) and integrate that into the printer.
But a SPI-bus between Duet and SBC with the G-code storage and webserver running on the Pi is a much nicer solution imho.
I am capable to do the modification on a Duet2, so the SBC<->Duet connection not being available as delivered is not really an issue.
-
Mini 5+ also supports CAN bus expansion... From your perspective, how does the Mini 5+ plus a 3HC expansion board compare?
-
@DaBit said in Duet 2, Duet3, RRF future:
I am capable to do the modification on a Duet2, so the SBC<->Duet connection not being available as delivered is not really an issue.
Tbh I'd hold off on that for anything but "i love tinkering" type of use. Or at least keep the WiFi module on the board to easily revert if you stumble onto an issue. I believe wilriker implemented keeping the WiFi module in reset when SBC mode is enabled so it can coexist with the SBC on the SPI bus.
-
@DaBit said in Duet 2, Duet3, RRF future:
How far are we from the point where the RRF feature set for Duet2 is going to differ from the newer boards?
Hard to say, but flash memory and RAM are already getting tight on Duet 2. That's why the SBC build of RRF for Duet 2 is separate from the WiFi and Ethernet build.
-
@whopping-pochard said in Duet 2, Duet3, RRF future:
Mini 5+ also supports CAN bus expansion... From your perspective, how does the Mini 5+ plus a 3HC expansion board compare?
That would be a nice fit actually!
That combo is ~40ukp cheaper than Duet2+duex5, and I have the option to use stronger motors for X1, X2 and Y.
(the moving stuff is going to be heavy, although back-of-napkin calculations show that the average NEMA17 motor should be powerful enough)@bearer said in Duet 2, Duet3, RRF future:
Tbh I'd hold off on that for anything but "i love tinkering" type of use. Or at least keep the WiFi module on the board to easily revert if you stumble onto an issue.
Keeping the wifi module in reset is the current method of doing the modification so reverting is not difficult.
And I thought that the SBC connection was stable with the latest RRF3.2 beta's?@dc42 said in Duet 2, Duet3, RRF future:
Hard to say, but flash memory and RAM are already getting tight on Duet 2. That's why the SBC build of RRF for Duet 2 is separate from the WiFi and Ethernet build.
So basically that makes the Duet2 somewhat not recommended for new designs for the people that like to tinker with the latest software.
-
What hardware changes are required in order to run SBC build of RRF for Duet 2
-
@percar said in Duet 2, Duet3, RRF future:
What hardware changes are required in order to run SBC build of RRF for Duet 2
There is a whole and lengthy thread on here. Basically replace ethernet module with a cable to the pi, or wire sbc cable in parallel with WiFi module
-
@bearer Thanks
I will look it over and see if makes sense to do the changes
