Possibly fried duet with an in spec power supply

Phaedrux

Hi please try to get a better close up of the board itself.

Luckypriest

@Phaedrux Please see attached photos, stole wife's phone. Any troubleshooting you would like me to do? I know theres no way in heck I qualify for warranty but this is killing me since I was so careful. I wish I had test hooked it up back then.

A Former User

Thats better, but still can't make out much besides the obvious burned sticker on the cpu.

Could just be lighting but with nothing else sticking out maybe this is slightly off coloured?

and was usb still connected when you turned on the 12v?

Luckypriest

USB wasnt connected when it came on, but was shortly after. Could that cause something similar? Not sure I've heard of that being an issue before. Looked at that pin and it looks fine, and the USB is currently working.

A Former User

@Luckypriest said in Possibly fried duet with an in spec power supply:

Could that cause something similar?

maybe, ref https://duet3d.dozuki.com/Wiki/USB_ground_loops but still a little odd set of symptoms.

Luckypriest

Found a similar case to mine and walked through the erasing / rewriting the firmware steps which succeeded, followed by:

Luckypriest

@bearer said in Possibly fried duet with an in spec power supply:

@Luckypriest said in Possibly fried duet with an in spec power supply:

Could that cause something similar?

maybe, ref https://duet3d.dozuki.com/Wiki/USB_ground_loops but still a little odd set of symptoms.

Fascinating read actually, did not know that. Don't think it applies here as it was a laptop anyway.

A Former User

@Luckypriest said in Possibly fried duet with an in spec power supply:

followed by:

you also put an up to date DuetWiFiServer.bin on the SD card (in /sys) and ran M997 S1 to update the wifi firmware?

Luckypriest

Dont believe I did, the guide I glanced at didnt have that step. Is the server you linked the newest one?

A Former User

@Luckypriest yes, its v1.23 which is the newest one (its not been changed since 2.05(?) so the one in the 3.0 release is fine to use)

Luckypriest

It cycled through all the baud rates with me connected and then says installation failed due to comm write error. Was there anything else I needed to do with this?

A Former User

@Luckypriest said in Possibly fried duet with an in spec power supply:

Was there anything else I needed to do with this?

don't think so, you could review https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware#Section_Updating_WiFi_firmware to see if I spaced out on something though.

but tbh i didn't expect it to work, somehting have had to give when the sticker almost caught fire.

Luckypriest

Interestingly enough, however, after running that the wifi module is disabled, trying to add my SSID gives the message failed to add SSID to remembered list. After that the wireless module is back to always stating that it is being started.

A Former User

@Luckypriest you could restart the board, enable wifi debug with M111 P14 S1 and repeat the upgrade and connection attempt but #longshot

Luckypriest

Also when USB is plugged in both the lights for 3.3v and 5v are on.

A Former User

@Luckypriest said in Possibly fried duet with an in spec power supply:

Also when USB is plugged in both the lights for 3.3v and 5v are on.

thats normal. it gets 5v from usb and 3.3v is derived from the 5v supply

Luckypriest

Right but other shorted issues always reference one of those being out, so I just wanted to clarify. When you say try reinstalling after turning on debugging(which succeeded btw), do you mean M997 S1?

Luckypriest

If that is the case the output was identical, not sure what debugging added to the mix.

Luckypriest

Infrared thermometer reads ~38c on the cpu chip with just USB power.

I'm willing to take the blame, but I really dont see what I did. Is it possible I got a lemon?

A Former User

@Luckypriest said in Possibly fried duet with an in spec power supply:

If that is the case the output was identical, not sure what debugging added to the mix.

if nothing then we know the uart from the cpu or the wifi module is damaged as the update should at the very least print the bootloader from the wifi module afaik.

Is it possible I got a lemon?

afaik the boards are automatically tested during production, so while possible, its unlikely - but this is where I take a step to the side and let the Duet people deal with it.

while you wait you might want to look into if you have any consumer protection rights that goes beyond 6 month warranty if the board was purchased september '19