#my fc started smoking after installing ImpulseRC Driver Fixer

1 messages · Page 1 of 1 (latest)

long peak
#

Send some pictures of the fc

#

It was probably dead/dying before you plugged it into usb, that's why you didn't have osd

slim parrot
#

@tender belfry

How did ImpulseRC Driver Fixer make a 5v regulator smoke??
it didn't. You're just making a completely random conjecture based on things that didn't even happen at the same time.

#

I thought maybe the battery has to be plugged in for it to detect my fc, so I plugged it in
this is the last thing that happened which is in any way relevant to the 5V regulator

tender belfry
#

so I fried something?

#

but i plugged it in before installing ImpulseRC Driver Fixer, and it worked perfectly well.

#

there wasn't any smoke

slim parrot
#

there wasn't any smoke yet

#

time is the factor

#

not IRC Driver fixer

#

the driver fixed shoves stuff around on your PC, it doesn't do anything to the FC aside from telling it to go into Bootloader mode, which is a betaflight function.

#

After putting everything together, I plugged in my 6s battery, nothing went wrong
the drone started up and the beeper beeped like normal, but there was a small problem when I looked into my DJI goggles.
this is the smoking gun

#

you plugged in your 6S battery and you didn't see anything go wrong at first glance

#

yet something did go wrong, killing your FC in that moment already

#

the FC was already dead from that moment on

tender belfry
#

so it's just come to it's deadline after installing ImpulseRC Driver Fixer, even thought ImpulseRC Driver Fixer had nothing to do ith it

slim parrot
#

the FC released the smoke the 2nd time you plugged the battery in

#

not "after IRC driver fixer", but "after plugging the battery in for the 2nd time"

tender belfry
#

so why did the 5v regulator smoke then?

slim parrot
#

because you messed up something during the rewire

#

it died on the 1st battery plug in, and then it went up in smoke because it was dead on the 2nd battery plugin

#

the fact that the FC was not recognised BEFORE you ran IRC driver fixer is smoking gun #2

tender belfry
#

there was nothing messed up. No short circuit, no loose cables touching other contacts, no strands of tiny sillicon wire laying around or solder blobs

slim parrot
#

if the FC worked with the PC before, that wouldn't change all of a sudden

#

also, IRC driver fixer is necessary for firmware update. Basic connection works without fixing drivers on the vast majority of FC's.

#

No short circuit
that's what you think, the FC may have a different opinion

tender belfry
#

I used compressed air can as well

#

on both sides on both boards

slim parrot
#

bent connector pin, solder blob, current running through the frame (CF is conductive you know), a component dying and taking the FC with it....

#

either way it doesn't matter

#

all I came here to do is to tell you that your blaming IRC Driver fixer for a clearly hardware issue that was present well before it was even ran is stupid

tender belfry
#

What could I do to fix it?

slim parrot
#

disconnect stuff from the FC

#

check every single component that's powered by 5V for a short circuit on the power wires

slim parrot
#

check the ESC to FC cable and connectors (the on-board ones) for damage - bent pins are not unusual and they can fry a FC

tender belfry
slim parrot
#

check for anything that's directly contacting the frame

#

correlation is not causation

#

just because two things appear to have happened at a similar time, it doesn't mean that they're responsible for one another

tender belfry
slim parrot
#

Your thinking that you need to use IRC Driver fixer is actually a symptom of the FC already being dead.

tender belfry
#

may I ask something

slim parrot
#

well, dead is an exaggeration - the 5V regulator could've just been overloaded to such a low voltage that the FC wasn't booting

#

it blew up on the n-th plug in because that's just what happens with overloaded components

#

they work until they don't

slim parrot
tender belfry
#

can the fc 5v regulator die because of one of the resistors (or diodes) on the ESC board is damaged?

slim parrot
#

certainly

#

if you short or damage the wrong [capacitor, resistor, diode], all kinds of things can blow up

#

things can cascade even

tender belfry
#

there's 2 of them quite physsically damaged

slim parrot
#

¯_(ツ)_/¯

#

hard to say after it's already blown up

tender belfry
#

so.. buy a new stack?

slim parrot
#

whether they were the culprits or the victims

#

the ESC might still be alive

#

I would be concerned about anything that takes 5V power however.

#

What are you running from 5V?

tender belfry
#

DJI Air Unit

slim parrot
#

wait

#

DJI Air Unit doesn't run from 5V

tender belfry
#

oh right...

#

forgot haha

slim parrot
#

might be wise to check the wiring there

tender belfry
#

Crossfire Receiver

slim parrot
#

buzzer, leds, ...?

tender belfry
#

yeah a buzzer

#

and that's it from 5v pads

#

all of those things are working properly

slim parrot
#

*were

#

now you don't know

tender belfry
#

no they are

slim parrot
#

?

tender belfry
#

the gps works

slim parrot
#

did you try them with something else?

tender belfry
#

and the crossfire receiver works too

#

the beeper..

#

it never beeped when I plugged my drone in for the 2nd time

#

hmm honestly I'm thinking that this may be the 2 damaged resistors on the ESC board

slim parrot
#

if you messed something up on the ESC, that could have caused a problematic voltage to make its way to the FC on its data wires
blowing the main FC chip
which would then blow the 3.3V regulator
which would then blow the 5V regulator

#

cascading

#

seen that before

tender belfry
#

new stack then 🙃

#

but what if my method of using compressed air or looking around the board to check for short circuit is inneficcient?

slim parrot
#

compressed air doesn't do much

tender belfry
#

I should learn how to check with multimeter or something.

slim parrot
#

if there was water or something like that, it can hide under chips for a long while unless you use heat to coax it out

tender belfry
slim parrot
#

isopropyl

#

it is conductive if you don't dry it out properly

tender belfry
#

that dries in only a few seconds

#

I only use it with q tip

slim parrot
#

¯_(ツ)_/¯

#

idk, all of this is guessing

tender belfry
#

and get all the areas with excess flux or dirt laying around

slim parrot
#

my guess is a soldering issue of some kind

tender belfry
#

so I guess I'm gonna have to buy a new stack then

slim parrot
#

to be fully honest, sometimes you just run out of luck

#

and stuff blows up because f* you that's why

tender belfry
#

and make sure that NOTHING GOES WRONG

#

I mean like.. to be extra careful

#

maybe look for some advice that I don't have the knowledge of to how to properly wire up a new stack

slim parrot
#

you can always ask for a wiring diagram

tender belfry
#

I'm good with wiring/soldering things to where they go

#

I mean

#

stuff like

#

how to make sure nothing is being shorted

slim parrot
tender belfry
#

maybe with a multimeter

slim parrot
#

never had an issue with it personally

tender belfry
slim parrot
#

kapton tape, heck, even paper

tender belfry
#

would double sided foam tape work well too?

#

or gorilla tape?

long peak
#

I'd love to see some pictures of your fc

slim parrot
#

neither of those are tolerant of high temperatures

#

they just melt

tender belfry
#

ah right