Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OVP PCB Inductor in DCP405 up in smoke #114

Closed
xlfe opened this issue Jul 14, 2022 · 9 comments
Closed

OVP PCB Inductor in DCP405 up in smoke #114

xlfe opened this issue Jul 14, 2022 · 9 comments
Assignees

Comments

@xlfe
Copy link
Collaborator

xlfe commented Jul 14, 2022

Made the mistake of connecting a battery thinking I could charge it, noticed some smoke and disconnected everything.

image

Can't see any other damage. The module passes power on checks, but doesn't seem to provide any output - I tried a simple 10v 10ma into a multi-meter and it reads 10v 10uA but no the multi-meter shows no voltage.

image

image

Any tips on next steps? should I clean up the PCB Inductor traces and do a more thorough test of individual components?

@prasimix prasimix self-assigned this Jul 15, 2022
@prasimix
Copy link
Member

Could you please let me know what exactly you tried to do with battery.
As a first step, check if fuse F1 is OK.

@xlfe
Copy link
Collaborator Author

xlfe commented Jul 15, 2022

Battery voltage was about 26v and I connected it to the main output on the module (+ve to +ve, -ve to -ve), set the module output to 28v and 1A and then turned the output on. OVP tripped immediately. after a few seconds I noticed the smoke, and disconnected the battery.

Just checked - Fuse 1 is fine, Fuse 2 is blown.
Also checked R93 next to Q13, and getting less than 0.5 ohms resistance

@prasimix
Copy link
Member

Ok, replace F2 and check if you can get set voltage output. You did something that is not allowed and I have to add a notice about that in the User manual: Never change output enable to ON when battery is connected and HW OVP is enabled!
What is happened: The voltage on the output was 26 V, you turned on the output that started from about 0 V. HW OVP detected huge difference in output voltage and immediately tripped. Battery is obviously still charged enough that triac drawn tens of amps but F1 was too slow to protect PCB inductor. Sorry for that, feel free to replace existing F1 and F2 with fast acting 5 A fuses.

@prasimix
Copy link
Member

Also checked R93 next to Q13, and getting less than 0.5 ohms resistance

That's fine, you can try to somehow bypass damaged PCB inductor.

@xlfe
Copy link
Collaborator Author

xlfe commented Jul 15, 2022

ok thanks. Yes as soon as it happened I realized I should have thought more carefully about what I was trying to do!

What is the PCB inductor used for? Ie what's the effect of bypassing it?

@prasimix
Copy link
Member

What is the PCB inductor used for? Ie what's the effect of bypassing it?

It is intended to limit max. current to preserve triac. We're talking here about a couple of hundreds of amps in microseconds. In most of the cases it should works just fine with inductor shorted.

@prasimix
Copy link
Member

The following warning has been added to the User manual (Chapter 10.2):

image

@xlfe
Copy link
Collaborator Author

xlfe commented Jul 17, 2022

Thanks - bodge wire that replaces the PCB inductor seems to have brought it back to life! Phew. Thanks!

image

@xlfe xlfe closed this as completed Jul 17, 2022
@prasimix
Copy link
Member

prasimix commented Oct 6, 2022

Remedy for this is suggested by @brianbienvenu in #255 that is actually similar to #9 which is changed now to P1 priority.

@prasimix prasimix pinned this issue Jul 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants