Burned Pixhawk? Want to fix it

There you have it, I have done it!
While I was exploring options with backup power for pixhawk I might have connected BEC to RC IN port in this autopilot. I didn't realize anything at first but later on I have discovered it was not booting correctly, solid red LED (not because of sdcard problem).

Output from terminal when running rc.APM
[QUOTE]

nsh> sh rc.APM
binfs already mounted
removed old boot.log
Detected FMUv2 board
uorb: already loaded
uorb started OK
Trying PX4IO board
PX4: param_find(SYS_RESTART_TYPE)
telem> Failed to communicate with IO, abort.
px4io: driver init failed
Loading /etc/px4io/px4io.bin
[PX4IO] using firmware from /etc/px4io/px4io.bin
[PX4IO] bootloader not responding
px4io: error updating PX4IO - check that bootloader mode is enabled
Failed to upgrade PX4IO firmware
PX4: param_find(SYS_RESTART_TYPE)
telem> Failed to communicate with IO, abort.
px4io: driver init failed
No PX4IO board found
Error in startup
nshterm [26:70]

[/QUOTE]

Pixhawk is also getting very hot in area marked on the photo. I know that area is something of the power supply for receiver which supposed to be connected to RC IN port and has something to do with px4io. Also checked biggest capacitor in that area and I have found out that it has continuity where same one on good pixhawk does not.

I have already bought a new pixhawk however it is a shame to throw this one away, especially that I know this one could be fixed (replacing voltage regulator or something).
Do any of you guys can point me to the right direction to fix it? How to identify faulty component?

Edit 1: found continuity between negative and positive pins on RC IN port. Rest of servo rail is ok

635768357882055105.jpg

You need to be a member of diydrones to add comments!

Join diydrones

Email me when people reply –

Activity

Neville Rodrigues liked Neville Rodrigues's profile
Jun 30
Santiago Perez liked Santiago Perez's profile
Jun 21
More…