Any chance to save my 5.8 TX ?

Hi Guys,

 

3690955569?profile=original

As you can see on the picture, one component has burnt on the tx (at the bottom near ts330 writing). However I can always transmit the signal with the sound, but no image. And when the tx is on, the TV screen is going black without frying. I mean there is no BSOD.

Do you think guys, it's possible to fix it? If you have an idea I'm interested.

 

Thanks

Alex

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

Join diydrones

Email me when people reply –

Replies

  • my also burned today, someone already tested this fix, can confirm if it works?

    IMG_20150102_095914.jpg

    https://storage.ning.com/topology/rest/1.0/file/get/3701904818?profile=original
  • Admin

    Beware of the fact that many of Chinese made stuff follow no color coding,  for some funny reason they use Red as  negative  in my cases. Many of their wiring harness has wrong color wire used in polarity, so do not assume red to be positive.

  • Thanks everybody :0)
    Sometimes I see someone have repaired this boscam it's so good and I'm happy to ear that

    Have a good day....
    My boscam works always...
    • I been using my repaired one since last year with no issues, but I use them as relay for my ground stations

  • Hi, I have 2 Boscam 200mw Txs with same (burnt fuse!) problem. I followed the method suggested my LordGotham, but it then led to melting of 12V power cable coming from 3S Lipo. Fortunately the JST plug at battery end melted immediately and that disconnected the battery from Tx. Some melting is also seen at Tx end of the power cable.

    Can anyone suggest me what did I do wrong? Here is the picture of my soldering and bypassing work done on one of the Txs. Now I am afraid to do the same on the other one! Please help...

    fr_134.jpg

    • Hi, later on I realized that the 5P Molex connector that I used had reversed positive and negative output wires! Black Negative should be the last outer one and positive next to it inside, but here on connector last wire was red and one inside was black leading to all short-circuits! Beware of such Molex connectors. This connector also fried my Mobius camera to death :-(.

      But fortunately both my Tx got working again. Thanks to LordGotham for showing the technique.
  • If it's of any help now, this is what I've learned about this subject.

    Referring to the image I attached.

    L1 is an inductor (AKA 'choke') and is around 10uH and has a resistance of around 0.5ohms.

    R1 is a 'link' resistor of close to 0ohms. Swapping the link resistor to the vacant pads marked with an arrow will connect the DC output to the 5V regulator of the TS330 (giving 5V for a CMOS camera).

    D1 is a Schottky diode, probably about 1 Amp size.

    C1 is a vacant pad for a filter capacitor if required.

    I accidentally shorted my 12V output to ground and burned the L1 inductor too like you guys, hence I found this thread.

    I replaced it with a same sized SMD inductor scavenged from an old defunct PC network card, a smaller L value but good enough for now (R value was lower than original too).

    I added a 10uF 16V SMD capacitor on C1 pads for the hell of it too. R1 was still OK when measured.

    Cheers,

    Martin

    3701743866?profile=original

    • Thanks!!

  • 3692750715?profile=original

    two cable

    the red is for 12v for the camera

    and the other cable is to repared the burst component

    so i try mine is ok

    but now there are no protection......  :o(  be carrefull

    mine work prefectly

    i hope you understand me

    • 3702492907?profile=originalI fried my Boscam 5.8g 200mW (from HobbyKing) today when trying to wire it to a crappy OSD that came with no instruction. A capacitor/resistor/inductor smoked, destroyed a pad, and it now sends no video. I hope it can be fixed with @lordgotham 's method.

      Could you confirm the following is the right wiring? Thanks!

      3702492785?profile=original

This reply was deleted.

Activity

DIY Robocars via Twitter
Apr 27
DIY Robocars via Twitter
Apr 27
DIY Robocars via Twitter
RT @f1tenth: Sliding (autonomously) into the weekend like ... 🤖😎 #f1tenth #robots #AutonomousVehicles @OpenRoboticsOrg @NVIDIAEmbedded @Aut…
Apr 25
DIY Robocars via Twitter
RT @chr1sa: One of the problems with autonomous car racing is that watching software drive is not a very exciting spectator sport. To help…
Apr 25
DIY Robocars via Twitter
RT @SmallpixelCar: Replaced AGX Xavier with @NVIDIAEmbedded Jetson Xavier NX. Now both cars look fast and clean https://t.co/jlcoY2EjZf
Apr 25
DIY Robocars via Twitter
RT @chr1sa: Yesterday we had a record number of competitors (36) in our monthly @DIYRobocars virtual autonomous car race. We kept it going…
Apr 25
DIY Robocars via Twitter
Apr 16
DIY Drones via Twitter
RT @chr1sa: After more than a year of only virtual races, @DIYRobocars returns to the newly renovated @circuitlaunch on May 22 for the resu…
Apr 11
DIY Robocars via Twitter
RT @DAVGtech: And now available with LiDAR 🔥 https://twitter.com/Heavy02011/status/1381137016381964293
Apr 11
DIY Robocars via Twitter
RT @Heavy02011: #VirtualRaceLeague: @DIYRobocars Race #9 - #ParkingLotNerds #thunderhillracetrack, CA Join us for the next race April 24th,…
Apr 11
DIY Robocars via Twitter
RT @DWalmroth: Weather's finally cooperating, looking forward to racing 1:10 scale autonomous cars outdoors again! @diyrobocars, @NVIDIAEm…
Apr 7
DIY Robocars via Twitter
RT @AIDRI_: I finally succeeded in optimizing the trajectory and speed of a car on a #racetrack. Next step: implement a 2d controller and…
Apr 7
DIY Robocars via Twitter
@jetdillo @circuitlaunch Actually the second *in person* event in a year. We do virtual races every month
Apr 2
DIY Robocars via Twitter
Update: we're moving it back one day to Sunday (the 4th) at 11:00am instead
Apr 2
DIY Robocars via Twitter
@GrantEMoe @circuitlaunch Update: we're doing it on Sunday (4th) at 11:00am instead
Apr 2
DIY Robocars via Twitter
RT @chr1sa: Maybe we should have a mini @DIYRobocars race in our lower school's playground https://t.co/xLFeua1R6X
Mar 29
More…