Dead Duet Wifi
-
Nope. I've tried the reset button (not the erase button), it seems to do absolutely nothing. It doesn't show up as a USB device and there is no sound when I plug it in.
-
You might have hit the "erase" button that cleared the firmware. Follow the instructions on installing the firmware using SAM-BA and it might come back to life (backup procedure #3).
https://duet3d.com/wiki/Updating_main_firmware
BTW. I think that erase button is the dumbest idea. It should use jumpers similar to clearing CMOS on a computer so people never accidentally hit that button. Putting that button next to the reset button is just asking for it to pressed by accident.
-
Thanks, I'll give it a try and report back.
-
Yeah, so this doesn't work since the USB device isn't being recognized. I've tried on two different machines.
-
Did you hit the "erase" button and then the "reset" button while its connected to the USB (to supply power to the board only).
-
Unfortunately, yes. This seems to have no effect.
I would love to know what happened to the board. I've checked and rechecked my wiring. The board has been running in this machine for several months with no real issues. This morning I installed a new extruder and stepper, but the machine was actually running fine afterward and was all closed up at when it died. I had run through a few calibration runs with the new extruder and was getting ready to try a test print when it died.
-
-
BTW. I think that erase button is the dumbest idea. It should use jumpers similar to clearing CMOS on a computer so people never accidentally hit that button. Putting that button next to the reset button is just asking for it to pressed by accident.
Indeed. I did the design when we still did not know how well the whole upload&flash over network would work and wanted to be able to get to it from the edge of the board in an installed position in case we needed to manually erase before each firmware reflash. #hindsight
-
Have you read https://duet3d.com/wiki/What_to_do_if_your_Duet_or_Duet_WiFi_won%27t_respond ?
Yes, I have gone through all of those steps. I will try the last step one more time this evening, but I'm fairly certain I did hold down the erase button for a few seconds followed by a reset at some point while I was troubleshooting yesterday.
-
Are the LEDs correctly lit? Is the microcontroller chip getting hot?
-
The LED's are correctly lit - the 3.3v and 5v are lit in addition to the two LEDs directly on either side of the USB connector. The only thing I noticed getting warm to the touch was the wifi module, but I'll be able to verify that again in a couple of hours.
-
Just to confirm, the micro is not getting warm. The wifi module does, however, get quite warm (I don't recall whether or not this was the case before). I also re-checked the Erase then Reset procedure, and that is a no-go. At this point I'm just going to get a new board on order tomorrow as I need to get the machine back up and running. Still, I'd feel a lot better about putting in the replacement if I knew exactly what happened to this one.
-
It's normal for the WiFi module to get warm.
I'm wondering whether the USB cable is faulty. Have you tried another one?
-
Yes I had the same thought last night so I tried another one, same result.
-
I think it's time for you to ask your supplier for a replacement under warranty.
-
I assume you guys will be doing autopsies on the dead Duet's to see what killed them ? Not a simple task that I know, but perhaps a pattern will emerge.
Jeff
-
Yes, they're all being returned to T3P3. Worth noting that the current failure rate is 3% - and some of those may have been caused by issues outside the Duet itself such as wiring or user error.
-
Yes, they're all being returned to T3P3. Worth noting that the current failure rate is 3% - and some of those may have been caused by issues outside the Duet itself such as wiring or user error.
Probably would have been nice to see some TVSS, MOV's, etc. in certain areas to try and keep problems down. I know the micro has some very limited protection against static and such, but it's not much. I think the biggest problem will be people with bad wiring on motors tossing hundreds or thousands of volt spikes around and perhaps inducing voltages into endstop wires, thermistors, etc. I killed my micro , I know how I did and I replaced the chip…no biggie, I've also seen some really stupid videos on You-Tube on how to crimp wires, if people follow some of these "tutorials" I can see failure rates increasing.
Edit: Not a reflection on the OP.
Jeff
-
The following is a subset of reported failure causes, selected randomly from the full set in order to not release sales volumes.
Duet Wifi Incomplete soldering
Duet Wifi Failed PS_ON functionality
Duet Wifi Flaky bootup
Duet Wifi Dead stepper driver
Duet Wifi FAN0 is dead
Duet Wifi Intermittently bad SPI comms - cannot update firmwareSome of these (incomplete soldering, SPI comms, flaky boot up) are manufacturing problems.
Some of them (dead stepper driver, fan 0 is dead) are user error, for example not understanding the thermostatic functionality of the fan channel - but that was not discovered until after the warranty exchange. Now we know to ask about that when troubleshooting
Failed PS_ON functionality - not sure what caused that.
Looking through the full set of failure data, I don't think any, with the possible exception of the dead stepper drivers, could be the result of a voltage spike. Protection is always a balance of cost vs predicted failure rate. If adding protection would increase board cost by $3 but only 0.5% of users would have experienced that damage, it doesn't make sense to implement on a ~$200 product.
With all that said, it would be nice to see Vin reverse polarity and overcurrect protection on the next revision, and I've requested as such to T3P3. Would also be nice to see input protection (inline resistor + diodes), space permitting.
-
Yeah, it's always a balancing act. I think that 0.5% could be mitigated through some education. Forums like this certainly help.
Jeff
