Tyro 79 + f405 mini mk2 Problems with Video and AUX switches

benet

New Member
Hello fellow humans!

After flying a Phantom 2 for some time i got myself a Tyro 79 kit a year ago or so. Which was a bad idea, because my knowledge on betaflight and RC components in general is quite limited. So now i hope, you can give me hints on how to solve the problems i ran into.

Hardware:

Copter:
- Tyro 79 kit exept for:
- Mamba f405 mini mk2 FC + ESC Combo
- Reciever FS A8S
- Runcam (Swift mini?)

Remote:
-Flysky FS-i6 (Firmware 2.0)

Betaflight:
-Version configurator: 10.6.0 firmware: BTFL 3.5.7


Problem 1:

I dont get my AUX-Channels to work.
The main Channels 1-6 work just fine but the switches dont do anything.
I have reset my remote multiple times, tried a ton of stuff in betaflight yet i can not even find out where the problem lies.
You can see te current state in the images below (its in german, sry for that)


Problem 2:
I dont get video/image to my goggles. And my video transmitter gets quite hot.
I can see a black screen with the batteryinfo and model name as customized in betaflight, but i dont get actual video.
Guess: faulty wiring between FC and transmitter possible as i had to solder the connector to the FC board.
I have measured the resistance between the connectors pins and marked solderpads at the back.
Could that be it? And does anyone have a wiring plan for the Tyro 79 transmitter?


Thanks a lot for helping noobs like me out!

Greetings from germany
Benedikt
 

Attachments

  • betaflight 4.jpg
    betaflight 4.jpg
    147.6 KB · Views: 2
  • betaflight 3.jpg
    betaflight 3.jpg
    187.8 KB · Views: 2
  • betaflight 2.jpg
    betaflight 2.jpg
    151.1 KB · Views: 2
  • betaflight 1.jpg
    betaflight 1.jpg
    235 KB · Views: 2
Since you see the OSD in your goggles the video signal the VTX is transmitting is fine but the cam signal isn't making it to the FC or the cam isn't getting powered (or has lense cover on, I have done that countless times and been bewildered for a few minutes at least). Would check cam vid signal line to the FC and power to the cam to make sure it is getting enough voltage from the pads or whatever it is hooked up to.

Regarding aux channels you usually do have to set that up on the transmitter/controller to map a particular switch to a channel that gets sent to the receiver (check out mixer settings if an option on your controller usually the mixer takes inputs from various controls on the transmitter and "mixes" them then outputs to some channel but it also needs to be setup for the receiver to get the data to pass along to the FC. In betaflight you typically just use the modes tab to pick the appropriate aux channel (based on what you see change in the receiver tab when flipping switches)
 
nope, its not the lenscover ;)
I will check if the cam has power, didnt think of this yet. Is there an easy way to check the vid signal from the cam to the VTX?

Well thats the point, i dont see anything changing in betaflight when flipping the switches. I will check the mixer thing tough....
I noticed that my FS i6 does not have the option "AUX Channels" other (newer) ones do. Maybe its a firmware thing.
Thanks a lot for your help!
 
Last edited:
For the cam power can just use a multimeter and steady hands to check that the line that is supposed to be suppling voltage has power, if you can check it cam side that's ideal but if not checking it on the FC at least tells you the voltage is good on that pad powering it (if not going direct off battery). For the video signal it is hard to diagnose/debug really without an oscilloscope and even then need to know what an analog video signal should look like vs just noise, really though I usually just redo any camera related solder connections if I run into similar issues and usually just redoing the solder job fixes whatever the issue was (something with my previous soldering attempt I guess :D )
 
Also you can try bypass the FC entirely and just tie the video out from the cam to the VTX and it will usually transmit that analog vid signal along no problem, the FC just gets involved for adding the OSD info (very nice to have but just for testing purposes can bypass that)
 
Back
Top