I use a glass bed so I can pull the bed after a print and use my 8x8 aluminum plate that is 10mm thick to act as a heat sink and suck the heat right out of the plate. After setting the glass bed on the plate, it only takes a minute or two before you hear the print pop free.

The glass is borosilicate and I generally don't run the bed any hotter than 50 - 60c, so I've never had the glass bed shatter or break. YMMV, but this has been a great way to pop off prints for me.

Additionally, the plate is a nice work surface on my table when not sucking up heat.

Got it off of Aliexpress for $20 I think.

Having a discussion outside the forum on how Duet should handle card/file corruption during a print. I had the issue a few years ago and came back to a printer where the head was sitting on the print, idle and I believe the heaters were all humming along. Scrapped the print, replaced the card and all was well.

The discussion centers around is an idle printer, due to file corruption, a fire hazard if no heaters are out of spec?

After reviewing some of the posts here, I just wanted to find out if the file corruption scenario is one where the Duet would fall through to the stop.g if it was detected. I'm not exactly sure how that could be done without running the risk of a false positive, but there are much bigger brains than mine here.

Thanks.

Yes please! Miss this not being there.

@claustro Great! Thanks!

@claustro said in D-bot reworked, very happy with results achieved:

deckingam

I'm planning on doing much the same thing to my D-Bot this spring/summer (if I can wait that long). Do you have links to the lead screw mod that you did?

The Keenovo heat bed was in my original build. Really focusing on the 3 lead screw implementation as well as incorporating a BLTouch (potentially).

Thanks!

Great! Thanks! I'm looking at moving to a mesh system as well (Netgear Orbi). My current Asus router allows separate naming of the 2.4 and 5, which I've taken advantage of to date.

There was a post on the Railcore facebook page from someone stating that their DuetWiFi wouldn't connect due to their router using the same SSID for both the 2.4 and 5.0 band. My current setup doesn't have that issue, but I'm thinking of moving to a mesh network for the house and would like to know if this would be an issue.

@phaedrux Thanks! One simple question that I just wanted to confirm. Is the microSD card just a simple storage area, or does the card have a boot sector that I need to be aware of? In looking at the online doc about the SD card, it just mentions sizing and structure, so I'm thinking that it is just a simple storage area.

I can't recall if I did anything special with dumping a bootable image to the card when I first did my build.

If there is the potential that the SD card is having or on the way to having issues, would it be better just to build a new SD card and copy config files over from the old card? It didn't seem difficult to create a fresh card when I build the DBot a year ago.

@dc42 Thanks! I've had that on the to-do list for a while. Given where I'm at with regards to firmware, is there anything special I need to do or be aware of with the jump to 2.02 with respect to how the upgrade plays out?

Here is a dropbox link - DB-DI-Cards Set-x2

Let me know if this doesn't work for some reason.

Thanks!