Help! Im a total newbie to drones, or RC stuff in general. What i have is an Armattan Tadpole frame. It has,
Diatone Mamba F411 16x16 stack, V1.2.
FRSKY XM+ receiver
TBS unify pro32 nano u.fl vtx
Luminier rhcp antenna
Caddx eos 2 cam
Running a 3s batt. And fatshark domv3 goggles
The issue im having is, with this setup, ive been able to set the quad up in betaflight, and im also able to bind and fly, line of sight. But i get no video. I mean black screen and no osd. What i also find odd, is the vtx is unlocked. I can go into betaflight, set it for raceband channel 4, (same channel as my tinyhawk) and it will get no signal on that channel. But then on band E channel 7 or something random, it will pick up 100% signal on the goggles, but only with black screen and no osd. A buddy got me started into this hobby. I took it to him. He allegedly has also tried a different vtx, a different cam, and i have tried 2 different f411 stacks. Same result everytime. There has to be some sort of betaflight setting or some silly wiring im getting off. Thanks in advance im really hoping to get this thing going this week
Edit, currently trying to add more pics.

First of all it might sound like a silly question but check that you don't have a cap on the lens of the camera. It has happened before, more than once.

Next, make sure you set the camera format in the OSD tab in Betaflight Configurator to the same type as the camera is outputting (PAL or NTSC). Don't rely on the AUTO setting because it doesn't always work.

If that doesn't work, temporarily wire the camera directly to the VTX instead of through the FC. That will then tell you if the camera itself has an issue or not.

The other issue will be SmartAudio wiring or configuration problem. Can you please run both the "dump" and "diff all" commands in the Betaflight Configurator CLI tab and copy/paste the results back here.

Thanks for such a quick reply.

I would agree it is very easily overlooked, however, Ive double checked there is no cap on the lens.

I believe my cam has support for both ntsc and pal. Either way, in betaflight I've tried auto, pal, and ntsc. no change.


I will wire my cam wires together and bypass the FC and test that asap.


I believe I added the cli dump below

#
# Building AutoComplete Cache ... Done!
#
# diff all# 

# Building AutoComplete Cache ... Done!

# 

# diff all



# version

# Betaflight / STM32F411 (S411) 4.1.6 Apr 25 2020 / 05:11:39 (283bda8bf) MSP API: 1.42

# manufacturer_id: DIAT   board_name: MAMBAF411   custom defaults: YES



# start the command batch

batch start



# reset configuration to default settings

defaults nosave



board_name MAMBAF411

manufacturer_id DIAT

mcu_id 004c002a3339510439373831

signature 



# map

map TAER1234



# serial

serial 1 2048 115200 57600 0 115200



# aux

aux 0 0 0 1300 2100 0 0

aux 1 1 1 1300 1700 0 0

aux 2 2 1 900 1175 0 0

aux 3 13 2 1800 2100 0 0



# master

set acc_calibration = -19,24,6

set rssi_channel = 16

set gyro_1_align_yaw = 1800



profile 0



profile 1



profile 2



# restore original profile selection

profile 0



rateprofile 0



rateprofile 1



rateprofile 2



rateprofile 3



rateprofile 4



rateprofile 5



# restore original rateprofile selection

rateprofile 2



# save configuration
save



# version
# Betaflight / STM32F411 (S411) 4.1.6 Apr 25 2020 / 05:11:39 (283bda8bf) MSP API: 1.42
# manufacturer_id: DIAT   board_name: MAMBAF411   custom defaults: YES

# start the command batch
batch start

# reset configuration to default settings
defaults
board_name MAMBAF411
manufacturer_id DIAT
mcu_id 004c002a3339510439373831
signature

# map
map TAER1234

# serial
serial 1 2048 115200 57600 0 115200

# aux
aux 0 0 0 1300 2100 0 0
aux 1 1 1 1300 1700 0 0
aux 2 2 1 900 1175 0 0
aux 3 13 2 1800 2100 0 0

# master
set acc_calibration = -19,24,6
set rssi_channel = 16
set gyro_1_align_yaw = 1800

profile 0

profile 1

profile 2

# restore original profile selection
profile 0

rateprofile
rateprofil

r
rate 5

#

Some questions i have,
1 do i need to ground both ground tabs on my vtx? Currently only using 1 as shown in diatone wiring diagram

2 ive read my vtx is a 3.3-5.5v input. On the wiring diagrams, shows 5v in. However, ive read specifications on the tbs unify pro32 on the websites that sell it, they say 3-13 volt inputs. Could this be my issue since im running it off 5v? It seems to work fine otherwise. The l.e.ds light up on the vtx as they should. I would hate to wire it up vcc and burn it up

The Caddx EOS2 camera only comes in either PAL or NTSC and it's not switchable so you need to decide which type you want when you order it. So yours will be one or the other. There aren't really any Betaflight settings for video other than the OSD on/off settings and the PAL/NTSC format.

You don't need to connect both GND pads on the VTX. One is for a camera if you connect the camera directly to the VTX. A 5V supply to the Unify Pro32 Nano is fine.

When you get a black screen it is generally either a faulty camera or a faulty OSD chip on the flight contoller. If the VTX was sending a signal to the goggles you would just get snow/static rather than a black screen. This is what wiring direct to the VTX will prove. If you still get a black screen it will be a problem with the camera. If you get a picture then the problem will be with the OSD chip on the FC.

Regarding your SmartAudio configuration, for that to work you will need to set up Betaflight VTX tables. Copy/paste the following block of commands into the CLI text box and press <ENTER>. That will configure the VTX settings correctly for SmartAudio 2.1 which is the version that the Unify Pro32 Nano uses.

Thanks for the clarification on the cam.
Just to make sure the cam was working, i took a known working camera, a runcam nano 2 from my tinyhawk 2. Wired it to the fc. Kept the vtx wired to the fc as it was before. Used the tbs antenna that came with the vtx instead of the luminier pro antenna, just for giggles. I also got the vtx tables entered.

So as mentioned before, i have the vtx unlocked, set to raceband channel 4, 5769 frequency. I get no signal to the fpv goggles on this channel. However, on every channel from the chart that has a frequency value of 0, i can pick up some sort of heavily static video, that comes and goes depending on antenna movement.

Im kind of wondering if i have a faulty vtx? I dont think its ever been powered on with no antenna, but i also knew alot less about this hobby when i started this build so im not going to say its not possible..

You will still need to wire the Caddx EOS2 direct to the VTX to determine whether the camera or FC OSD chip is at fault. Wiring another camera through the FC isn't eliminating the FC from the equation which is what we need to try and do first.

Confirmed. I hooked my caddx eos2 signal wire directly to my vtx. Only on the channels where the frequency is 0, it will pick up 100% signal A and B on my fatshark goggles, then give me a black screen, or sometimes i will get video but is very static, sometimes red, and the image constantly moves

I tried this with my runcam nano 2 as well. Same results.

My friend who introduced me to this hobby, says he tried a rush brand vtx in replace of this tbs unify pro32 and he got the same result. We also tried a second mamba f411 fc with the same exact results.

Wait, so you've swapped out the VTX, FC, and camera and nothing has changed?

Do you know that the receiver in your goggles is good?

I have not tried a new vtx or fc myself. My friend said he did along with the 2 fc's, and he knows more about all of this than me so im taking his word on that one. But me personally, ive tried 2 cameras, and bypassed fc on cam signal wire. Same results. No signal on the channel the vtx is programmed for. But some crappy video on all the channels that have a 0 value.

Yes im sure the goggles work. I also have a tinyhawk 2 that i fly indoor/outdoor.

It sounds stupid but at this point, it would seems as if there has to be some kind of programming that is off in betaflight?