phil-barrett / PicoCNC

Raspberry Pi Pico based grblHAL Controller
133 stars 23 forks source link

U11 magic smoke and fire, Pi Pico W dead #5

Closed iLoveAndyBaker closed 1 year ago

iLoveAndyBaker commented 1 year ago

U11 smoked, quite dramatically. There is not and never was anything on the vac or dust collector.

Had steppers on X,Y,Z (with current limiting resistors on the step and direction pins) and only microswitches on X,Y,Z limits and a wire across reset.

Clean desk.

This is the second Pi Pico that this PicoCNC killed.

image

I suspect power issues on the board - , I haven't looked at the schematic however. There was power cycling, I think it was probably my 12V (checked to 12.1V) supply resetting for an over-current situation until the chip got hot enough to go incandescent and stink up the whole room. Thank god for the FR in FR4.

Things have been a little odd with powering it (can't really nail it down now that it's blowed up) but having to do weird power cycles here and there.

Please double check your power. Are we powering the Pico with the PicoCNC AND USB? Is Q1 working right? Did Tindie put the right part down?

phil-barrett commented 1 year ago

Wow. That's pretty dramatic. I've been testing a number of these boards running on 12V power for a lot of hours and never had anything blow at all. That device (74LVC1G32) runs on +5V and the pin that is burnt is the +5V pin. Bad chip? Maybe 12V got onto the 5V rail? Could you show me a picture of the entire board?

Please return the board and we will refund your purchase.

iLoveAndyBaker commented 1 year ago

PXL_20230821_204432130 PXL_20230821_204335580 PXL_20230821_204403988

Let me know where to mail it and I'll get it out soon.

phil-barrett commented 1 year ago

Address deleted. If you still need it, let me know. I didn't want it to be seen by everyone.

On Mon, Aug 21, 2023 at 2:00 PM Andy Baker @.***> wrote:

[image: PXL_20230821_204432130] https://user-images.githubusercontent.com/101837270/262150857-8ddeb3d7-407a-4043-a354-8cc1c7a85bd0.jpg [image: PXL_20230821_204335580] https://user-images.githubusercontent.com/101837270/262150862-1e37e641-ce38-4a5e-a743-86eff42e1fa4.jpg [image: PXL_20230821_204403988] https://user-images.githubusercontent.com/101837270/262150866-ecceefda-8a9a-4288-af1d-d8aff6ae8924.jpg

Let me know where to mail it and I'll get it out soon.

— Reply to this email directly, view it on GitHub https://github.com/phil-barrett/PicoCNC/issues/5#issuecomment-1687035822, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD6NUTXPAFRBJDWIQWYJQ6DXWPD5HANCNFSM6AAAAAA3YZY2MU . You are receiving this because you commented.Message ID: @.***>

phil-barrett commented 1 year ago

I have been looking at the design for how this could happen and I really can't see anyway for that part to go short unless it was a bad part. This circuit is in two designs with over 1100 units in the field and no reports of a problem. I see several possibilities - 1) bad chip with an internal short (very rare), 2) shorting across the output (not obvious from the photos) or 3) chip damaged due to 12V across the 5V rail (hard to do accidentally).

Looking forward to getting the board to investigate further.

iLoveAndyBaker commented 1 year ago

Nothing, huh? Yeah I don't know either. Maybe something etched weird. Maybe a part was just bad, or wrong, or just randomly latched up. Either way, it's in the mail, I've thrown in the blown Pico as a bonus. I hope you can learn something from it, it looks like a nice little board. I would have liked to have put the FLIR camera on it, but as luck would have it, I've lent it out.

Thanks,

Andy

From: phil-barrett @.> Sent: Tuesday, August 22, 2023 3:08 PM To: phil-barrett/PicoCNC @.> Cc: Andy Baker @.>; Author @.> Subject: Re: [phil-barrett/PicoCNC] U11 magic smoke and fire, Pi Pico W dead (Issue #5)

I have been looking at the design for how this could happen and I really can't see anyway for that part to go short unless it was a bad part. This circuit is in two designs with over 1100 units in the field and no reports of a problem. I see several possibilities - 1) bad chip with an internal short (very rare), 2) shorting across the output (not obvious from the photos) or 3) chip damaged due to 12V across the 5V rail (hard to do accidentally).

- Reply to this email directly, view it on GitHubhttps://github.com/phil-barrett/PicoCNC/issues/5#issuecomment-1688993028, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AYI6TVU26LPGWQMXKWN636DXWUUUNANCNFSM6AAAAAA3YZY2MU. You are receiving this because you authored the thread.Message ID: @.**@.>>

phil-barrett commented 1 year ago

I got the board and did some poking. Powered it up with 12V. The first thing that became clear is there was 11V on the 5V rail. That pretty much blew all the 5V logic chips and the Pico. I'd guess U11 being so small, it went first. Looking at the 5V regulator U1 (AMS1117-5), I could see some damage to it. See the photo. (I made the scratch probing at it.) It failed with a direct short which is unusual - they usually die open. Maybe it took too much current and blew. Maybe too high voltage was applied - 24V would have killed it. Maybe reversed polarity? I looked at all the boards I have in stock (55) and none of them showed any damage to the regulator. I desoldered the dead regulator and soldered a new one in place. It happily produced 5V and did not overheat. I did not see any evidence of over current any other place than U1 and U11. So, it's hard to say what damaged U1. I desoldered U11 and inspected the traces under it. They appear to be ok so it wasn't a board short. I also looked at the pin headers used to join the 2 12V sections to see if the shorting plugs had been installed wrong but did not see any damage.

dead board

So what did I learn from this? To be honest, not a lot. A lot of this circuitry is the same as on the Teensy board. And the circuit is pretty straightforward. There is no obvious design flaw. I am thinking of adding an in line rectifier before the 12V input of the AMS1117 to at least protect it from reverse polarity though that has implications on the 0-10V circuit. I had already separated the headers for joining the 2 12V sections to prevent accidental shorting (that's in V1.52, the currently shipping board). I am adding warnings to the User Manual about reverse polarity and power sources above 12V.

Anyway, I believe this is an isolated case. There have been no other reports of a similar nature and in all the testing I never saw any significant overheating (I do a lot of thermal measurement on the boards during testing). In general, the worst case temperature increase is 15C over ambient, well within expectations.

Anyway, I have requested Tindie issue a full refund. Sorry this happened. Phil Barrett

iLoveAndyBaker commented 1 year ago

I'd be happy to take a new one to be honest. It makes my wiring a lot cleaner too.

The power supply was a nice switching wall wart putting out clean 12.1V. It was running well, I connected it when I started the project and never looked back. As to why I was thinking those LEDs too bright, maybe it was that regulator after all. At any rate, I can use a different PSU.

I've seen people put big fat diodes across the input.. blows the fuse in the PSU if you go backwards, and no voltage drop that way. Provided it's got a fuse that is.

Thanks for looking into this.

Andy Baker Red 6


From: phil-barrett @.> Sent: Tuesday, August 29, 2023 11:16:23 PM To: phil-barrett/PicoCNC @.> Cc: Andy Baker @.>; Author @.> Subject: Re: [phil-barrett/PicoCNC] U11 magic smoke and fire, Pi Pico W dead (Issue #5)

I got the board and did some poking. Powered it up with 12V. The first thing that became clear is there was 11V on the 5V rail. That pretty much blew all the 5V logic chips and the Pico. I'd guess U11 being so small, it went first. Looking at the 5V regulator U1 (AMS1117-5), I could see some damage to it. See the photo. (I made the scratch probing at it.) It failed with a direct short which is unusual - they usually die open. Maybe it took too much current and blew. Maybe too high voltage was applied - 24V would have killed it. Maybe reversed polarity? I looked at all the boards I have in stock (55) and none of them showed any damage to the regulator. I desoldered the dead regulator and soldered a new one in place. It happily produced 5V and did not overheat. I did not see any evidence of over current any other place than U1 and U11. So, it's hard to say what damaged U1. I desoldered U11 and inspected the traces under it. They appear to be ok so it wasn't a board short. I also looked at the pin headers used to join the 2 12V sections to see if the shorting plugs had been installed wrong but did not see any damage.

[dead board]https://user-images.githubusercontent.com/16570958/264234208-1ab6f625-d3bf-439e-bbfd-191e6f0cb7cf.jpg

So what did I learn from this? To be honest, not a lot. A lot of this circuitry is the same as on the Teensy board. And the circuit is pretty straightforward. There is no obvious design flaw. I am thinking of adding an in line rectifier before the 12V input of the AMS1117 to at least protect it from reverse polarity though that has implications on the 0-10V circuit. I had already separated the headers for joining the 2 12V sections to prevent accidental shorting (that's in V1.51, the currently shipping board). I am adding warnings to the User Manual about reverse polarity and power sources above 12V.

Anyway, I believe this is an isolated case. There have been no other reports of a similar nature and in all the testing I never saw any significant overheating (I do a lot of thermal measurement on the boards during testing). In general, the worst case temperature increase is 15C over ambient, well within expectations.

Anyway, I have issued a full refund. Sorry this happened. Phil Barrett

— Reply to this email directly, view it on GitHubhttps://github.com/phil-barrett/PicoCNC/issues/5#issuecomment-1698555163, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AYI6TVQJUWXTTJ2DQVYOO3LXX3LDPANCNFSM6AAAAAA3YZY2MU. You are receiving this because you authored the thread.Message ID: @.***>

phil-barrett commented 1 year ago

With the refund, you could place another order. Tindie is prompt about refunds.

phil-barrett commented 1 year ago

I'm closing this. There have been no more reports of anything similar so I am calling it a one-off problem. If anything comes up I will reopen.