My TinyHawk2 is unable to connect with the DJI RE goggles. I have only ever connected one time, and not since. The goggles have a scan mode and when I click on scan it looks like it is searching for a channel, because I see occasional green verticaI stripes and the feed is jittery like an old tv set. I have also tried setting it manually in the range of the goggles, which is 5650 to 5850. I connected the quad to Betaflight and set a manual channel, e.g. 5806 which corresponds with R5 on the unlocked configuration table. When I use the manual feature of the goggles and set it to 5806 I do not get a connection. I am pretty sure the VTX is unlocked on the TinyHawk2 because I have clicked on the VTX button at the same time the battery is plugged in, and led lights come on, as it is supposed to according to the quad manual and various youtube videos. Any ideas? I have been trying various things for several days now to no avail.
Unable to transmit video feed from TinyHawk2 to DJI RE goggles
- Thread starter dsmith76
- Start date
droneguy
Well-Known Member
Hey dsmith76,
If I understand you correctly, you are going into the goggles menu and going to the racing drone (analog) option then selecting scan for frequencies? Then it does not actually lock onto the frequency on which the drone is transmitting?
If I understand you correctly, you are going into the goggles menu and going to the racing drone (analog) option then selecting scan for frequencies? Then it does not actually lock onto the frequency on which the drone is transmitting?
droneguy
Well-Known Member
can you provide the "diff all" from the CLI in betaflight for your TH2? I can review it and look for any potential config problems.
Entering CLI Mode, type 'exit' to return
# diff all
# version
# Betaflight / STM32F411 (S411) 4.2.8 Feb 15 2021 / 12:09:04 (101738d8e) MSP API: 1.43
# config: manufacturer_id: MTKS, board_name: MATEKF411RX, version: ee671311, date: 2019-10-16T11:49:37Z
# start the command batch
batch start
# reset configuration to default settings
defaults nosave
board_name MATEKF411RX
manufacturer_id MTKS
mcu_id 005000493539511534363532
signature
# name: TinyHawk II
# beeper
beeper -GYRO_CALIBRATED
beeper -RX_LOST
beeper -RX_LOST_LANDING
beeper -DISARMING
beeper -ARMING
beeper -ARMING_GPS_FIX
beeper -BAT_CRIT_LOW
beeper -BAT_LOW
beeper -GPS_STATUS
beeper -RX_SET
beeper -ACC_CALIBRATION
beeper -ACC_CALIBRATION_FAIL
beeper -READY_BEEP
beeper -DISARM_REPEAT
beeper -ARMED
beeper -SYSTEM_INIT
beeper -ON_USB
beeper -BLACKBOX_ERASE
beeper -CRASH_FLIP
beeper -CAM_CONNECTION_OPEN
beeper -CAM_CONNECTION_CLOSE
beeper -RC_SMOOTHING_INIT_FAIL
# beacon
beacon RX_SET
# map
map TAER1234
# serial
serial 1 2048 115200 57600 0 115200
# aux
aux 0 0 0 1700 2100 0 0
aux 1 1 1 900 1300 0 0
aux 2 2 1 1300 1700 0 0
aux 3 13 2 1700 2100 0 0
aux 4 35 3 1700 2100 0 0
# vtxtable
vtxtable bands 5
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 0 5885 5905 0 0
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 powerlevels 3
vtxtable powervalues 0 1 2
vtxtable powerlabels 25 100 200
# master
set acc_calibration = -30,-67,0,1
set mag_hardware = NONE
set baro_hardware = NONE
set min_check = 1010
set max_check = 1990
set rssi_offset = 20
set rx_spi_protocol = FRSKY_D
set motor_pwm_protocol = DSHOT600
set motor_poles = 12
set vbat_max_cell_voltage = 440
set vbat_min_cell_voltage = 320
set vbat_warning_cell_voltage = 330
set current_meter = NONE
set small_angle = 180
set deadband = 2
set pid_process_denom = 1
set osd_warn_batt_not_full = OFF
set osd_warn_visual_beeper = OFF
set osd_warn_core_temp = OFF
set osd_warn_rc_smoothing = OFF
set osd_warn_no_gps_rescue = OFF
set osd_warn_gps_rescue_disabled = OFF
set osd_warn_rssi = ON
set osd_cap_alarm = 450
set osd_vbat_pos = 2412
set osd_rssi_pos = 2138
set osd_tim_2_pos = 2423
set osd_flymode_pos = 2113
set osd_vtx_channel_pos = 2401
set osd_craft_name_pos = 2121
set osd_display_name_pos = 394
set osd_pid_roll_pos = 353
set osd_pid_pitch_pos = 34
set osd_pidrate_profile_pos = 186
set osd_warnings_pos = 2345
set osd_avg_cell_voltage_pos = 374
set osd_flip_arrow_pos = 310
set osd_rate_profile_name_pos = 23
set osd_pid_profile_name_pos = 2
set osd_stat_max_spd = OFF
set osd_stat_battery = ON
set osd_stat_max_curr = OFF
set osd_stat_used_mah = OFF
set osd_stat_bbox = OFF
set osd_stat_bb_no = OFF
set osd_stat_total_time = ON
set vtx_power = 2
set vtx_low_power_disarm = UNTIL_FIRST_ARM
set vtx_freq = 5806
set vcd_video_system = NTSC
set frsky_spi_tx_id = 204,51
set frsky_spi_offset = -18
set frsky_spi_bind_hop_data = 0,65,130,195,25,92,155,222,50,115,180,10,75,140,205,35,100,165,230,60,125,190,20,85,150,215,45,110,175,5,70,135,200,30,95,160,225,55,120,185,15,80,145,210,40,105,170,0,0,0
set gyro_1_align_yaw = 1800
set name = TinyHawk II
profile 0
# profile 0
set dyn_lpf_dterm_min_hz = 0
set dyn_lpf_dterm_max_hz = 250
set dterm_lowpass_hz = 100
set dterm_lowpass2_hz = 200
set feedforward_transition = 25
set acc_limit_yaw = 100
set crash_recovery = ON
set iterm_relax = RPY
set iterm_relax_type = GYRO
set iterm_relax_cutoff = 11
set iterm_windup = 40
set iterm_limit = 150
set throttle_boost = 4
set p_pitch = 105
set i_pitch = 125
set d_pitch = 95
set f_pitch = 100
set p_roll = 105
set i_roll = 125
set d_roll = 95
set f_roll = 100
set p_yaw = 95
set i_yaw = 95
set d_yaw = 45
set angle_level_strength = 60
set horizon_transition = 80
set level_limit = 30
set horizon_tilt_effect = 80
set horizon_tilt_expert_mode = ON
set d_min_roll = 0
set d_min_pitch = 0
set auto_profile_cell_count = 1
set launch_control_mode = PITCHONLY
profile 1
# profile 1
set dyn_lpf_dterm_min_hz = 0
set dyn_lpf_dterm_max_hz = 250
set dterm_lowpass_hz = 100
set dterm_lowpass2_hz = 200
set feedforward_transition = 25
set acc_limit_yaw = 100
set iterm_rotation = ON
set iterm_relax = RPY
set iterm_relax_type = GYRO
set iterm_relax_cutoff = 11
set iterm_windup = 40
set iterm_limit = 150
set throttle_boost = 4
set p_pitch = 70
set d_pitch = 55
set f_pitch = 70
set p_roll = 70
set i_roll = 90
set d_roll = 55
set f_roll = 70
set p_yaw = 75
set d_yaw = 13
set f_yaw = 80
set angle_level_strength = 60
set horizon_level_strength = 30
set horizon_transition = 80
set level_limit = 30
set d_min_roll = 0
set d_min_pitch = 0
set auto_profile_cell_count = 2
profile 2
# restore original profile selection
profile 0
rateprofile 0
# rateprofile 0
set thr_expo = 50
set roll_rc_rate = 80
set pitch_rc_rate = 80
set yaw_rc_rate = 80
set roll_expo = 60
set pitch_expo = 60
set yaw_expo = 20
set roll_srate = 60
set pitch_srate = 60
set yaw_srate = 60
set tpa_rate = 25
set tpa_breakpoint = 1650
rateprofile 1
# rateprofile 1
set thr_mid = 20
set thr_expo = 50
set roll_rc_rate = 80
set pitch_rc_rate = 80
set yaw_rc_rate = 80
set roll_expo = 60
set pitch_expo = 60
set yaw_expo = 20
set roll_srate = 60
set pitch_srate = 60
set yaw_srate = 60
set tpa_rate = 45
set tpa_breakpoint = 1450
set throttle_limit_type = SCALE
set throttle_limit_percent = 75
rateprofile 2
# rateprofile 2
set thr_mid = 0
rateprofile 3
rateprofile 4
rateprofile 5
# restore original rateprofile selection
rateprofile 0
# save configuration
save
#
# diff all
# version
# Betaflight / STM32F411 (S411) 4.2.8 Feb 15 2021 / 12:09:04 (101738d8e) MSP API: 1.43
# config: manufacturer_id: MTKS, board_name: MATEKF411RX, version: ee671311, date: 2019-10-16T11:49:37Z
# start the command batch
batch start
# reset configuration to default settings
defaults nosave
board_name MATEKF411RX
manufacturer_id MTKS
mcu_id 005000493539511534363532
signature
# name: TinyHawk II
# beeper
beeper -GYRO_CALIBRATED
beeper -RX_LOST
beeper -RX_LOST_LANDING
beeper -DISARMING
beeper -ARMING
beeper -ARMING_GPS_FIX
beeper -BAT_CRIT_LOW
beeper -BAT_LOW
beeper -GPS_STATUS
beeper -RX_SET
beeper -ACC_CALIBRATION
beeper -ACC_CALIBRATION_FAIL
beeper -READY_BEEP
beeper -DISARM_REPEAT
beeper -ARMED
beeper -SYSTEM_INIT
beeper -ON_USB
beeper -BLACKBOX_ERASE
beeper -CRASH_FLIP
beeper -CAM_CONNECTION_OPEN
beeper -CAM_CONNECTION_CLOSE
beeper -RC_SMOOTHING_INIT_FAIL
# beacon
beacon RX_SET
# map
map TAER1234
# serial
serial 1 2048 115200 57600 0 115200
# aux
aux 0 0 0 1700 2100 0 0
aux 1 1 1 900 1300 0 0
aux 2 2 1 1300 1700 0 0
aux 3 13 2 1700 2100 0 0
aux 4 35 3 1700 2100 0 0
# vtxtable
vtxtable bands 5
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 0 5885 5905 0 0
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 powerlevels 3
vtxtable powervalues 0 1 2
vtxtable powerlabels 25 100 200
# master
set acc_calibration = -30,-67,0,1
set mag_hardware = NONE
set baro_hardware = NONE
set min_check = 1010
set max_check = 1990
set rssi_offset = 20
set rx_spi_protocol = FRSKY_D
set motor_pwm_protocol = DSHOT600
set motor_poles = 12
set vbat_max_cell_voltage = 440
set vbat_min_cell_voltage = 320
set vbat_warning_cell_voltage = 330
set current_meter = NONE
set small_angle = 180
set deadband = 2
set pid_process_denom = 1
set osd_warn_batt_not_full = OFF
set osd_warn_visual_beeper = OFF
set osd_warn_core_temp = OFF
set osd_warn_rc_smoothing = OFF
set osd_warn_no_gps_rescue = OFF
set osd_warn_gps_rescue_disabled = OFF
set osd_warn_rssi = ON
set osd_cap_alarm = 450
set osd_vbat_pos = 2412
set osd_rssi_pos = 2138
set osd_tim_2_pos = 2423
set osd_flymode_pos = 2113
set osd_vtx_channel_pos = 2401
set osd_craft_name_pos = 2121
set osd_display_name_pos = 394
set osd_pid_roll_pos = 353
set osd_pid_pitch_pos = 34
set osd_pidrate_profile_pos = 186
set osd_warnings_pos = 2345
set osd_avg_cell_voltage_pos = 374
set osd_flip_arrow_pos = 310
set osd_rate_profile_name_pos = 23
set osd_pid_profile_name_pos = 2
set osd_stat_max_spd = OFF
set osd_stat_battery = ON
set osd_stat_max_curr = OFF
set osd_stat_used_mah = OFF
set osd_stat_bbox = OFF
set osd_stat_bb_no = OFF
set osd_stat_total_time = ON
set vtx_power = 2
set vtx_low_power_disarm = UNTIL_FIRST_ARM
set vtx_freq = 5806
set vcd_video_system = NTSC
set frsky_spi_tx_id = 204,51
set frsky_spi_offset = -18
set frsky_spi_bind_hop_data = 0,65,130,195,25,92,155,222,50,115,180,10,75,140,205,35,100,165,230,60,125,190,20,85,150,215,45,110,175,5,70,135,200,30,95,160,225,55,120,185,15,80,145,210,40,105,170,0,0,0
set gyro_1_align_yaw = 1800
set name = TinyHawk II
profile 0
# profile 0
set dyn_lpf_dterm_min_hz = 0
set dyn_lpf_dterm_max_hz = 250
set dterm_lowpass_hz = 100
set dterm_lowpass2_hz = 200
set feedforward_transition = 25
set acc_limit_yaw = 100
set crash_recovery = ON
set iterm_relax = RPY
set iterm_relax_type = GYRO
set iterm_relax_cutoff = 11
set iterm_windup = 40
set iterm_limit = 150
set throttle_boost = 4
set p_pitch = 105
set i_pitch = 125
set d_pitch = 95
set f_pitch = 100
set p_roll = 105
set i_roll = 125
set d_roll = 95
set f_roll = 100
set p_yaw = 95
set i_yaw = 95
set d_yaw = 45
set angle_level_strength = 60
set horizon_transition = 80
set level_limit = 30
set horizon_tilt_effect = 80
set horizon_tilt_expert_mode = ON
set d_min_roll = 0
set d_min_pitch = 0
set auto_profile_cell_count = 1
set launch_control_mode = PITCHONLY
profile 1
# profile 1
set dyn_lpf_dterm_min_hz = 0
set dyn_lpf_dterm_max_hz = 250
set dterm_lowpass_hz = 100
set dterm_lowpass2_hz = 200
set feedforward_transition = 25
set acc_limit_yaw = 100
set iterm_rotation = ON
set iterm_relax = RPY
set iterm_relax_type = GYRO
set iterm_relax_cutoff = 11
set iterm_windup = 40
set iterm_limit = 150
set throttle_boost = 4
set p_pitch = 70
set d_pitch = 55
set f_pitch = 70
set p_roll = 70
set i_roll = 90
set d_roll = 55
set f_roll = 70
set p_yaw = 75
set d_yaw = 13
set f_yaw = 80
set angle_level_strength = 60
set horizon_level_strength = 30
set horizon_transition = 80
set level_limit = 30
set d_min_roll = 0
set d_min_pitch = 0
set auto_profile_cell_count = 2
profile 2
# restore original profile selection
profile 0
rateprofile 0
# rateprofile 0
set thr_expo = 50
set roll_rc_rate = 80
set pitch_rc_rate = 80
set yaw_rc_rate = 80
set roll_expo = 60
set pitch_expo = 60
set yaw_expo = 20
set roll_srate = 60
set pitch_srate = 60
set yaw_srate = 60
set tpa_rate = 25
set tpa_breakpoint = 1650
rateprofile 1
# rateprofile 1
set thr_mid = 20
set thr_expo = 50
set roll_rc_rate = 80
set pitch_rc_rate = 80
set yaw_rc_rate = 80
set roll_expo = 60
set pitch_expo = 60
set yaw_expo = 20
set roll_srate = 60
set pitch_srate = 60
set yaw_srate = 60
set tpa_rate = 45
set tpa_breakpoint = 1450
set throttle_limit_type = SCALE
set throttle_limit_percent = 75
rateprofile 2
# rateprofile 2
set thr_mid = 0
rateprofile 3
rateprofile 4
rateprofile 5
# restore original rateprofile selection
rateprofile 0
# save configuration
save
#
droneguy
Well-Known Member
So a couple things.. Your VTX table looks good. You can disable the "enter frequency directly" which then lets you choose a band and channel from the VTX table instead.
The option to stay in low power until first arm means your VTX is in low power until you arm. This may make it hard for the goggles to find the channel. To provide a stronger signal for the goggles to lock onto, you can either disable this menu option for now or arm your quad (with props off) to get the vtx pumping out a stronger signal. Then try scanning again.
Ok, I'll disable that menu often. In the VTX table, should I click Boscam_a and b and c and Raceband, select just one of them, or just leave them unchecked?
droneguy
Well-Known Member
You need to do a couple things. Click on disable the "enter frequency directly" then enable the factory switch on all your bands in the VTX table. This will allow betaflight to use the VTX table and only send channel number and band to the VTX. (EG R1)
Then in the upper portion of the screen you will end up with pre-populated pull downs that you can choose the band, channel and power output.
This is the best way to run the VTX table since it simplifies everything.
I actually powered on the quad (on the floor) and let the props spin. I noticed that when I click to scan the frequency, the number 5806 was on the screen. Even when I click on "continue" to scan it sticks on 5806. I clicked continue several times but the number always stays on the screen. I have noticed on Youtube videos where pilots are showing people how to use the analog feature of the RE goggles, that I can see the numbers changing in the background until it connects to a frequency. When I have set mine to a specific frequency in Betaflight, such as 5806 or some other number, when I then fire up the goggles it always seem to be stuck on that number, eventhough I can see vertical and horizontal lines in the fuzzy background.
droneguy
Well-Known Member
Ok, we are getting somewhere. It seems as though your goggles are locking onto the VTX frequency. The fact you have vertical lines and a fuzzy background may be related to another issue. once you complete the steps I outlined above, set the pulldown to R1 then try a scan on the goggles before you power up the quad. Then power up the quad during the scan.
Okay, before I ran my test, I disabled the "Enter Frequency directly" button and clicked all but the Fatshark buttons. I am going to try again.
droneguy
Well-Known Member
It kind of sounds like your goggles see the signal since it does show the channel, but the signal is messed up at the goggles.
Why aren't you clicking the fatshark button? All the factory button does is enable the VTX to send the channel and band instead of the raw frequency. It just ensures compatibility.
Have you crashed this drone recently? is there a chance your camera wires came loose?
droneguy
Well-Known Member
I'll give my buddy a call that has these goggles and see if he has had any similar issues. I'll get back to you shortly.
I went back and clicked the fatshark button and tried it again, but still no image. I have crashed a few times flying around in my living room, but they were not "bad" crashes, but I suppose bad enough to loosen some camera wires.
BTW, just to make sure the goggles are working I fired up the Mavic2 Pro and they were working fine.
droneguy
Well-Known Member
The Mavic 2 uses occusync so that is a different thing all together. These goggles use occusync for DJI drones and also have an analog receiver for FPV drones.
