<p>Since you confirmed that the protocol+vtx table is correct I'd focus on the physical connection. One explaination would be that the signal is disturbed and the vtx has a hard time decoding it.</p>

<p>Try to disconnect all other components and focus just on the fc+vtx. Try to isolate the SMA connector of the vtx from any carbon parts/metal parts of the frame. Another option is to twist the cables going from the fc to the vtx. You could also add capacitors to the power supply.</p>

<p>If nothing works I'd try a different vtx and check if the problems carry over the new vtx. Adding a phono of your wiring could also help to identify the issue.</p>

CC BY-SA 4.0
2020-06-10T13:48:46.053Z
Sound advice, but I had already made sure that everything is isolated. The SMA connector is only touching my TPU mount and I have a 470uF 37V capacitor on my power supply.

Using a different VTX did the trick.
lukad
CC BY-SA 4.0
2020-06-08T21:45:40.397Z
2020-06-08T21:45:40.397Z
bingo-fuel
<p>I received my new VTX (Rush Tank) today and I plugged it straight into the same connector that I had used for the other VTX, changed my ports and VTX table accordingly and it just works.</p>

<p>My best guess is that the old VTX is simply defective, although I couldn't see any damaged parts on the board.</p>

CC BY-SA 4.0
2020-06-10T13:43:30.910Z
2020-06-10T13:43:30.910Z
lukad
<p>I have a Diatione Mamba F405 MK2 and a <a href="https://www.hglrc.com/products/hglrc-forward-vtx-5-8g-48ch-25-50-100-200-400mw-fpv-transmitter" rel="nofollow noreferrer">HGLRC Forward VTX</a> on my 6s race quad and I can't control the vtx using betaflight. The video transmission itself works fine, I just have to use the button on the board.</p>

<p>It says "Device Ready: No" in the betaflight configurator vtx tab and any parameters that I set there are ignored. In the OSD vtx menu the status line reads <code>* UF ---- ----</code>.</p>

<p>Here is my wiring and my ports configuration. It looks fine to me.</p>

<p><a href="https://i.sstatic.net/b6l2m.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/b6l2m.png" alt="wiring diagram"></a>
<a href="https://i.sstatic.net/399XV.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/399XV.png" alt="ports tab screenshot"></a></p>

<p>And here is my full diff.</p>

<pre><code># version
# Betaflight / STM32F405 (S405) 4.2.0 Apr 29 2020 / 08:08:49 (b480103d4) MSP API: 1.43
# config: manufacturer_id: DIAT, board_name: FURYF4OSD, version: 3a35e73b, date: 2019-09-30T05:46:12Z

# start the command batch
batch start

board_name FURYF4OSD
manufacturer_id DIAT

# name: Sea Breeze

# beeper
beeper -ON_USB

# beacon
beacon RX_SET

# serial
serial 0 64 115200 57600 0 115200

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

# vtxtable
vtxtable bands 6
vtxtable channels 8
vtxtable band 1 BOSCAM_A A CUSTOM  5865 5845 5825 5805 5785 5765 5745 5725
vtxtable band 2 BOSCAM_B B CUSTOM  5733 5752 5771 5790 5809 5828 5847 5866
vtxtable band 3 BOSCAM_E E CUSTOM  5705 5685 5665 5645 5885 5905 5925 5945
vtxtable band 4 FATSHARK F CUSTOM  5740 5760 5780 5800 5820 5840 5860 5880
vtxtable band 5 RACEBAND R CUSTOM  5658 5695 5732 5769 5806 5843 5880 5917
vtxtable band 6 IMD6     I CUSTOM  5362 5399 5436 5473 5510 5547 5584 5621
vtxtable powerlevels 5
vtxtable powervalues 25 50 100 200 400
vtxtable powerlabels 25 50 100 200 400

# master
set dyn_notch_width_percent = 0
set dyn_notch_q = 250
set dyn_notch_min_hz = 70
set dyn_notch_max_hz = 350
set acc_calibration = 62,-10,158,1
set min_check = 1005
set max_check = 1995
set rssi_channel = 16
set rssi_src_frame_errors = OFF
set rc_smoothing_derivative_type = PT1
set fpv_mix_degrees = 25
set dshot_bidir = ON
set ibata_scale = 115
set beeper_dshot_beacon_tone = 3
set small_angle = 180
set pid_process_denom = 2
set osd_vbat_pos = 450
set osd_rssi_pos = 2106
set osd_tim_2_pos = 2519
set osd_flymode_pos = 2082
set osd_throttle_pos = 2466
set osd_current_pos = 2505
set osd_mah_drawn_pos = 2512
set osd_warnings_pos = 14729
set osd_avg_cell_voltage_pos = 2498
set vtx_band = 1
set vtx_channel = 1
set vtx_power = 3
set vtx_freq = 5865
set gyro_1_align_yaw = 1800
set name = Sea Breeze

profile 0

# profile 0
set dyn_lpf_dterm_curve_expo = 6
set vbat_sag_compensation = 100
set anti_gravity_gain = 5000
set iterm_relax = RPY
set p_pitch = 32
set d_pitch = 27
set p_roll = 29
set d_roll = 25
set p_yaw = 31
set d_min_roll = 16
set d_min_pitch = 18

rateprofile 0

# rateprofile 0
set rates_type = QUICK
set roll_rc_rate = 120
set pitch_rc_rate = 120
set yaw_rc_rate = 120
set roll_srate = 90
set pitch_srate = 90
set yaw_srate = 90

# end the command batch
batch end
</code></pre>

<p>I have redone all solder joints and checked for continuity with my multimeter.
Is my wiring maybe just wrong? Or is my vtx broken?</p>

<p>(I'm using a betaflight 4.2 rc version, but I've also had this issue with 4.1)</p>

<p>Edit: I contacted the HGLRC support and they told me that IRC Tramp is indeed the correct protocol and they gave me a vtx table which was identical with mine.</p>

CC BY-SA 4.0
2020-06-06T19:16:14.593Z
I don't think `IRC Tramp` is the right setting in the Ports tab. I believe the HGLRC Forward VTX uses SmartAudio and not the Tramp protocol.
ifconfig
CC BY-SA 4.0
2020-06-06T19:28:37.927Z
Thanks for your reply. Unfortunately the manual doesn't say which protocol the VTX is using... And when I enable the SmartAudio blackbox debug mode, all 4 debug channels are at 0. That's why I assumed it must be `IRC Tramp`.

In case it uses SmartAudio, what could be the reason that it doesn't work either?
lukad
CC BY-SA 4.0
2020-06-06T19:48:41.400Z
Well, BF 4.1 introduced `vtxtables` that need to be manually configured before using SmartAudio, which could be the issue. See Joshua Bardwell's video on the topic here: https://www.youtube.com/watch?v=VRQJJTyHNJw
ifconfig
CC BY-SA 4.0
2020-06-06T20:10:36.793Z
I know how to set up vtx tables for SmartAudio. Before you can load the right vtx table you need to know which SmartAudio version the vtx uses. But like I said the SmartAudio debug mode shows nothing at all. I just tried using the SmartAudio vtx tables from the Betaflight wiki anyway. But still nothing.
lukad
CC BY-SA 4.0
2020-06-06T21:51:58.810Z
Huh, well I'm sorry to say that I'm stumped. I don't have much experience debugging FC→VTX communications.
ifconfig
CC BY-SA 4.0
2020-06-08T13:10:00.763Z
Did you already try to use a different tx pad or soft serial?
bingo-fuel
CC BY-SA 4.0
2020-06-08T14:17:03.300Z
Hadn't tried that. But I just tried with TX6, PPM mapped to softserial 1 and led 1 mapped to softserial. Made no difference. However I noticed that the Tramp Telemetry starts working _sometimes_ after I leave the quad on for about a minute (this happend with all pads that I used). One time it even set the frequency to the one that was configured in betaflight. But after that I wasn't able to change it again.The status line in the OSD one time even read the actual band/channel and frequency. But it's totally unreliable. I guess this piece of crap vtx is just broken.
lukad
<betaflight><video-transmitters>
How do I set up IRC Tramp for my HGLRC Forward VTX?
lukad
# How do I set up IRC Tramp for my HGLRC Forward VTX?

(Asked by: username_0 on 2020-06-06)

I have a Diatione Mamba F405 MK2 and a HGLRC Forward VTX on my 6s race quad and I can't control the vtx using betaflight. The video transmission itself works fine, I just have to use the button on the board.
It says "Device Ready: No" in the betaflight configurator vtx tab and any parameters that I set there are ignored. In the OSD vtx menu the status line reads * UF ---- ----.
Here is my wiring and my ports configuration. It looks fine to me.


And here is my full diff.
# version
# Betaflight / STM32F405 (S405) 4.2.0 Apr 29 2020 / 08:08:49 (b480103d4) MSP API: 1.43
# config: manufacturer_id: DIAT, board_name: FURYF4OSD, version: 3a35e73b, date: 2019-09-30T05:46:12Z

# start the command batch
batch start

board_name FURYF4OSD
manufacturer_id DIAT

# name: Sea Breeze

# beeper
beeper -ON_USB

# beacon
beacon RX_SET

# serial
serial 0 64 115200 57600 0 115200

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

# vtxtable
vtxtable bands 6
vtxtable channels 8
vtxtable band 1 BOSCAM_A A CUSTOM  5865 5845 5825 5805 5785 5765 5745 5725
vtxtable band 2 BOSCAM_B B CUSTOM  5733 5752 5771 5790 5809 5828 5847 5866
vtxtable band 3 BOSCAM_E E CUSTOM  5705 5685 5665 5645 5885 5905 5925 5945
vtxtable band 4 FATSHARK F CUSTOM  5740 5760 5780 5800 5820 5840 5860 5880
vtxtable band 5 RACEBAND R CUSTOM  5658 5695 5732 5769 5806 5843 5880 5917
vtxtable band 6 IMD6     I CUSTOM  5362 5399 5436 5473 5510 5547 5584 5621
vtxtable powerlevels 5
vtxtable powervalues 25 50 100 200 400
vtxtable powerlabels 25 50 100 200 400

# master
set dyn_notch_width_percent = 0
set dyn_notch_q = 250
set dyn_notch_min_hz = 70
set dyn_notch_max_hz = 350
set acc_calibration = 62,-10,158,1
set min_check = 1005
set max_check = 1995
set rssi_channel = 16
set rssi_src_frame_errors = OFF
set rc_smoothing_derivative_type = PT1
set fpv_mix_degrees = 25
set dshot_bidir = ON
set ibata_scale = 115
set beeper_dshot_beacon_tone = 3
set small_angle = 180
set pid_process_denom = 2
set osd_vbat_pos = 450
set osd_rssi_pos = 2106
set osd_tim_2_pos = 2519
set osd_flymode_pos = 2082
set osd_throttle_pos = 2466
set osd_current_pos = 2505
set osd_mah_drawn_pos = 2512
set osd_warnings_pos = 14729
set osd_avg_cell_voltage_pos = 2498
set vtx_band = 1
set vtx_channel = 1
set vtx_power = 3
set vtx_freq = 5865
set gyro_1_align_yaw = 1800
set name = Sea Breeze

profile 0

# profile 0
set dyn_lpf_dterm_curve_expo = 6
set vbat_sag_compensation = 100
set anti_gravity_gain = 5000
set iterm_relax = RPY
set p_pitch = 32
set d_pitch = 27
set p_roll = 29
set d_roll = 25
set p_yaw = 31
set d_min_roll = 16
set d_min_pitch = 18

rateprofile 0

# rateprofile 0
set rates_type = QUICK
set roll_rc_rate = 120
set pitch_rc_rate = 120
set yaw_rc_rate = 120
set roll_srate = 90
set pitch_srate = 90
set yaw_srate = 90

# end the command batch
batch end

I have redone all solder joints and checked for continuity with my multimeter.
Is my wiring maybe just wrong? Or is my vtx broken?
(I'm using a betaflight 4.2 rc version, but I've also had this issue with 4.1)
Edit: I contacted the HGLRC support and they told me that IRC Tramp is indeed the correct protocol and they gave me a vtx table which was identical with mine.

**Tags:** betaflight, video-transmitters
> **Comments:**
> **username_1**: I don't think `IRC Tramp` is the right setting in the Ports tab. I believe the HGLRC Forward VTX uses SmartAudio and not the Tramp protocol.  
> **username_0**: Thanks for your reply. Unfortunately the manual doesn't say which protocol the VTX is using... And when I enable the SmartAudio blackbox debug mode, all 4 debug channels are at 0. That's why I assumed it must be `IRC Tramp`.  In case it uses SmartAudio, what could be the reason that it doesn't work either?  
> **username_1**: Well, BF 4.1 introduced `vtxtables` that need to be manually configured before using SmartAudio, which could be the issue. See Joshua Bardwell's video on the topic here: https://www.youtube.com/watch?v=VRQJJTyHNJw  
> **username_0**: I know how to set up vtx tables for SmartAudio. Before you can load the right vtx table you need to know which SmartAudio version the vtx uses. But like I said the SmartAudio debug mode shows nothing at all. I just tried using the SmartAudio vtx tables from the Betaflight wiki anyway. But still nothing.  
> **username_1**: Huh, well I'm sorry to say that I'm stumped. I don't have much experience debugging FC→VTX communications.  
> **username_2**: Did you already try to use a different tx pad or soft serial?  
> **username_0**: Hadn't tried that. But I just tried with TX6, PPM mapped to softserial 1 and led 1 mapped to softserial. Made no difference. However I noticed that the Tramp Telemetry starts working _sometimes_ after I leave the quad on for about a minute (this happend with all pads that I used). One time it even set the frequency to the one that was configured in betaflight. But after that I wasn't able to change it again.The status line in the OSD one time even read the actual band/channel and frequency. But it's totally unreliable. I guess this piece of crap vtx is just broken.  

---

## 2 answers

### Answer by username_2 on 2020-06-08. Score: 1

Since you confirmed that the protocol+vtx table is correct I'd focus on the physical connection. One explaination would be that the signal is disturbed and the vtx has a hard time decoding it.

Try to disconnect all other components and focus just on the fc+vtx. Try to isolate the SMA connector of the vtx from any carbon parts/metal parts of the frame. Another option is to twist the cables going from the fc to the vtx. You could also add capacitors to the power supply.

If nothing works I'd try a different vtx and check if the problems carry over the new vtx. Adding a phono of your wiring could also help to identify the issue.

> **Comments:**
> **username_0**: Sound advice, but I had already made sure that everything is isolated. The SMA connector is only touching my TPU mount and I have a 470uF 37V capacitor on my power supply.  Using a different VTX did the trick.  

---

### Answer by username_0 on 2020-06-10. Score: 0

I received my new VTX (Rush Tank) today and I plugged it straight into the same connector that I had used for the other VTX, changed my ports and VTX table accordingly and it just works.

My best guess is that the old VTX is simply defective, although I couldn't see any damaged parts on the board.


---

