Upgrade from Duet 2 to Duet 3
-
@Diamondback
Yes for the first question
you can get M122 outputs from the mini in expansion board mode
you'll need an SD card in the mini with a config containing a single line of M954.... -
@Diamondback said in Upgrade from Duet 2 to Duet 3:
Can I enable ethernet on the extension board (Mini 5) and simply leave it unplugged in order to quickly spin up DWC on that board if needed for any debugging purposes?
The ethernet port will be disabled as you will have a config with M954 in it and nothing else as @jay_s_uk says. AFAIK you can have the M552 commands in the config as well. One work around might be to have a switch connected to a spare IO and have the config check the state of the switch on startup, if the switch triggered then branch to a normal startup with ethernet etc, if its not then just run the M954 command. Not sure if that would work because it would mean some commands to define and check the switch before the M954 ran...
-
@T3P3Tony i'm pretty sure ethernet/wifi works even if the board is set using M954, so you can just have M552 commands and DWC files as normal
-
@jay_s_uk ahh ok, I will need to test that, pleasantly surprised if it does!
-
what is "expansion mode" and can i run the Duet 3 Mini 5+ in expansion mode? Lets say i added a 6HC, would that provide benefit if i were expanding my hardware?
-
@RogerPodacter you can run the mini 5+, 6HC or 6XD as an expansion board to another Duet 3 to expand the number of drives etc
-
Happy to report that things went better than expected! Didn't really run into any bigger issues, I very much like the much nicer pin names of the modern hardware
Have some pictures:
Pre-Upgrade state with Duet 2 + Duex 5:
Stripping the old boards out:
Duet 3 Hardware all connected up:
-
Talk about "hardware porn" ..... impressive if that was built by you!
-
@jens55 Thank you
-
@Diamondback, may I inquire about the port labeling? It looks like the labels are adhesive ... are they from some sort of label maker? Most DIY labels don't seem to adhere for me that well and I can't think of a way to generate white text on transparent backing (I would use a laser printer to generate labels but of course they can't print white ....
-
@jens55 Sure, there's 3 different label types used here, all printed with a Brother E550W (even though there are MUCH cheaper versions from Brother that print the same labels).
- The labels on the actual cables inside the box are heatshrink tubing that is being printed on, no-name clone
- The labels on the cables outside the box are original Brother "strong adhesive" labels in 9mm that are printed as wire wraps, these mostly adhere to themselves where they overlap and not so much to the nylon cable sleeve
- The labels on the printed lid of the box are no-name white-on-clear 12mm ones, so far they seem to hold fine. I'm not entirely convinced that they will hold forever, given that the lid has a textured (powdercoated PEI printbed) surface. They don't immediately fall off either though. They are printed as "blocks", which is a specific function of that label printer (usually used for fuse boxes and such)
-
@Diamondback ... nice !
-
@Diamondback said in Upgrade from Duet 2 to Duet 3:
Can I enable ethernet on the extension board (Mini 5) and simply leave it unplugged in order to quickly spin up DWC on that board if needed for any debugging purposes?
I've not tested that. Let me know if it works!
Is there any way to run gcode from the master board DWC via CAN on the extension board? (for example M122 or so)
You can use M122 B# from the main board to get a M122 report from the expansion board. Similarly for M115. You can't send general commands to the expansion board over CAN.
Is there anything else I should know about this adventure? Any tips from other people that upgraded?
In RRF 3.5beta1, updating the expansion board from the main board doesn't work. It works in RRF 3.4.4 and 3.4.5.
-
@dc42 said in Upgrade from Duet 2 to Duet 3:
I've not tested that. Let me know if it works!
Yup, that works. I just connected to my Duet 5 Mini in expansion mode via its own ethernet interface.
Downgraded firmware to 3.4.5 (since the current 3.5b1 makes it impossible for me to print).
However, it only successfully applied the firmware once I turned off expansion mode, previously it would pretend to install but still came up with 3.5 afterwards. (Not sure if related to the CAN upgade bug in 3.5b1 or not, but turning CAN off was easy enough obviously)I did notice however, that when I upgraded to 3.5b1 previously, DWC on the slave board DID NOT update. I guess that's expected?
-
@Diamondback said in Upgrade from Duet 2 to Duet 3:
I did notice however, that when I upgraded to 3.5b1 previously, DWC on the slave board DID NOT update. I guess that's expected?
Yes, that's expected.