Setup this JHEMCU GF16 stack, but the video out gives a black screen. When power cycled a few times, it did show the BF OSD and image twice, but it faded to black after a few seconds, and can't seem to get it at all anymore. Changing  PAL/NTSC settings didn't make any difference. The soldering looks clean and the pads are widely spaced. Is there some OSD component to diagnose, is there some common OSD caps or diodes that fail?

I did test fly without the OSD, and the gyro on this board does seem to perform normally. Despite the ridiculous filter/pid values it ships with, resetting it to BF defaults seems to fly without any odd behavior. This seems to be a very nice sub $40 stack, F405, nice layout, easy soldering, includes baro/blackbox, too bad qc is not great.

Are you getting video back to goggles?
 Can you by pass the FC altogether and rule out whether the vtx or camera is working?

Yes I flew it without OSD by connecting camera direct to VTX, so both those components are working.

(30-Mar-2023, 02:52 AM)mstc Wrote: Yes I flew it without OSD by connecting camera direct to VTX, so both those components are working.

  Sometimes powering and grounding the camera and vtx with the same power pads on the FC will help OSD issues or using a redundant ground will help a finicky OSD circuit.
 Is the OSD setting turned on in betaflight on the configuration page?
  
    
  Unfortunately other than scrubbing with alcohol and a toothbrush in case the vtx or camera video pads are somehow bridged to another pad I have no ideas.
I’m assuming it has a capacitor on battery pads?


  Hopefully someone will chime in and find a solution.

Yes cap is on, and the OSD did come on twice, but lasted less than 10 seconds. The pads on this FC are very widely spaced and easy to solder to, so no bridging and board was cleaned.

(30-Mar-2023, 04:00 AM)mstc Wrote: Yes cap is on, and the OSD did come on twice, but lasted less than 10 seconds. The pads on this FC are very widely spaced and easy to solder to, so no bridging and board was cleaned.

 Sounds like a defective FC.
 Hopefully the vendor will send a replacement.

Yes, this is the symptom of a faulty OSD chip or a short circuit for that chip. It's JHEMCU. Crappy electronics and poor QC.

Use a magnifying glass to check for any stray solder balls, splatters of solder, or stray whiskers of wire on the FC that might be causing a short, especially between the pins on the OSD chip (it's the large rectangular chip with 28 pins).

If that all looks OK then try to get a replacement or get a complete refund and buy a stack from a different manufacturer.