-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Due to a bad cable, the U15 LXES1TBCC2-004 burned out. Help me. #710
Comments
I'm in the same boat. The LXES1TBCC2-004 was discontinued, as I'm sure you know by now. The only substitute I could find was a DRTR5V0U4LP16. You should check the datasheets yourself, and please let us know if it works. |
As I read through all of this I start to wonder since I use a magnetic micro usb cable for the hackrf to avoid damaging the socket. It works fine still even with the portapack even though the usb cable is thin. 🙂
Get Outlook for Android<https://aka.ms/ghei36>
…________________________________
From: RChadwick7 <notifications@github.com>
Sent: Monday, March 23, 2020 8:38:20 PM
To: mossmann/hackrf <hackrf@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: Re: [mossmann/hackrf] Due to a bad cable, the U15 LXES1TBCC2-004 burned out. Help me. (#710)
I'm in the same boat. The LXES1TBCC2-004 was discontinued, as I'm sure you know by now. The only substitute I could find was a DRTR5V0U4LP16. You should check the datasheets yourself, and please let us know if it works.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmossmann%2Fhackrf%2Fissues%2F710%23issuecomment-602813542&data=02%7C01%7C%7C562222bdd14f4b42595a08d7cf61beaf%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637205891017988584&sdata=maMl5iOPcTdL1qk80lGrOlGfZLTqkENk%2FjOw9LJKpoU%3D&reserved=0>, or unsubscribe<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAF6E3DI3NO35CBC4JK6VYYTRI63CZANCNFSM4LBIKWVQ&data=02%7C01%7C%7C562222bdd14f4b42595a08d7cf61beaf%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637205891017998589&sdata=vgpZ4%2FesYOy43kvdYxoneo8YOmpHcDo9XkGiZG33EyQ%3D&reserved=0>.
|
We use Vishay part number VBUS54CV-HSF-G4-08 for U15. This has been documented in the KiCad source since 2018. |
Your HackRF One should operate normally (but lacks ESD protection) with U15 removed. Testing in that configuration would be a good first step to determine if everything else is working correctly. |
Could you give a bit more info about how you were powering the HackRF when it went wrong? Make/model of any battery packs or power supplies would be helpful. |
It looked like there was a hidden mechanical damage inside the cable, and at some point a short circuit occurred. The cable was high-quality, but it worked for many years. |
You can apply 5 V to P20 pin 22 and ground to P20 pin 19. |
The parts you have circled are resistors. One of them is a 0 ohm resistor, so it is really a short. |
I'm going to close this as there hasn't been a response in a while, but please re-open this issue or open a new one if you still need assistance. |
Due to a bad cable, the U15 LXES1TBCC2-004 burned out. Help me.
For earlier I apologize for English google translator is to blame for everything))
The story is this, I connected the device with a bad cable and after a few seconds smoke came out of it.
I know for sure that the U15 LXES1TBCC2-004 burned out because it had a hole.
the question is, what else could suffer?
a local mobile phone repairman, got drunk and said should earn without this detail (of course this did not happen)
I have a portapack without battery.
Could I supply power to the contacts to test the functionality of these devices without USB?
if so, what contacts and how many volts?
With great pleasure I will accept any advice on the diagnosis and restoration of these devices.
PS
Be careful with the cables, have a nice day everyone.
The text was updated successfully, but these errors were encountered: