Naze32 Full / Taranis Plus / D4R-II / Telemetry

Post Reply
User avatar
DirtCreature
Posts: 3
Joined: Sat Nov 22, 2014 7:42 pm

Naze32 Full / Taranis Plus / D4R-II / Telemetry

Post by DirtCreature »

Update: if you read this and are looking for the answers, as well, please add a reply asking for the same help!

Hi Everyone,

First, I've tried to read every possible post using every possible combination of keywords and have also tried and learned a lot about the different transmission protocols and how I can try and diagnose the problem before posting here. I even figured out how to connect the board to a CP2102 board through Putty to look at what's coming through to see if I could figure something out. I think I have read so much and tried so many things that I am now utterly confused. So, here I am, begging for some help before I pull all of my hair out and run screaming through the streets.

My config:
Naze32 Full
Taranis Plus w/ opentx-taranis-plus-2.0.15 (no added modules, etc - out of the box hardware)
FrySky D4R-II (latest firmware)
UBLOX NEO 6 GPS
Telemetry
This is all working happily on the Naze32. Flies well, GPS works, all good when connected to Cleanflight (I tried everything with Baseflight, too).

Settings Overview (dump is below):
PPM
SoftSerial
FrySky Rx > Pin 1
GPS > pin 3/4 (5700 baud)
FrySky Telemtry > pin 6 (soft serial inverted)

The problem, phrased as a few questions:
1. What, exactly, is sent from the Naze32 that defines "telemetry"? Is there a specific list?
Strangley, from what I've seen in videos, I get voltage information on my Taranis without having telemetry plugged in. Is it possible that people think they're using the telemetry port on the D4R-II when they're not? I have turned logs on and tested this and I think I'm right here.

2. If no one knows, can you tell me how to figure this out? I tried connecting a CP202 serial port (Tx naze to Rx in) to the green wire Rx on the D4R-II and am able to see unreadable data in Putty. How can I interpret what data is being sent? My dread is that the D4R is actually broken and simply not sending data (and what I'm looking at is something else, entirely)!

3. Is it possible to configure a Taranis Plus to show GPS data? I saw Dominic's video [youtube]https://www.youtube.com/watch?v=dahGlc3Tf40[/youtube] here in which he is using what I presume is basically my setup, with the exception of the Turnigy. I understand that it's a different radio, but with OpenTx I assumed there were enough similarities that it is possible.

Note: again, I tried a thousand different configurations and ran logging on the Taranis and no GPS, etc, data.

4. Does anyone specifically know if, perhaps, it is FrySky's version of openTx that prevents it from capturing the data sent by the D4R?

5. I've tried different baud rates, etc. From what I can tell, many people ask these questions and only get some of the results. Can it be something silly like baud rates?

Thanks for any help! The favor I ask we keep the responses to very specific, complete configurations that have worked, or specific references to complete information. I know how that sounds, but these threads tend to get off track and it would be great to have a definitive resource thread for this configuration (I think more and more people seem to be getting this exact config, from what I've read). Hope that makes sense!

Here's the dump of board as it is (I left MOTOR_STOP and a couple other features disabled to keep it simple, removed LED since I'm not using it). I have highlighted what I think is important (which might be wrong - please correct it where you see fit and let me know if something is missing). Oh, baud rates are currently set to 19200 (this was the last thing I tried). Thanks again, everyone.


# version
Cleanflight/NAZE 1.7.1 Feb 4 2015 / 11:35:37 (8aee0b2)
# dump master

# mixer
mixer QUADX


# feature
feature -RX_PPM
feature -VBAT
feature -INFLIGHT_ACC_CAL
feature -RX_SERIAL
feature -MOTOR_STOP
feature -SERVO_TILT
feature -SOFTSERIAL
feature -GPS
feature -FAILSAFE
feature -SONAR
feature -TELEMETRY
feature -CURRENT_METER
feature -3D
feature -RX_PARALLEL_PWM
feature -RX_MSP
feature -RSSI_ADC
feature -LED_STRIP
feature -DISPLAY
feature -ONESHOT125
feature -BLACKBOX
feature RX_PPM
feature VBAT
feature MOTOR_STOP
feature SOFTSERIAL
feature GPS
feature TELEMETRY



# map
map TAER1234


# led
[REMOVED - not used]
# color
[REMOVED - not used]

set looptime = 3500
set emf_avoidance = 0
set mid_rc = 1500
set min_check = 1100
set max_check = 1900
set rssi_channel = 0
set rssi_scale = 30
set input_filtering_mode = 0
set min_throttle = 1150
set max_throttle = 1850
set min_command = 1000
set servo_center_pulse = 1500
set 3d_deadband_low = 1406
set 3d_deadband_high = 1514
set 3d_neutral = 1460
set 3d_deadband_throttle = 50
set motor_pwm_rate = 400
set servo_pwm_rate = 50
set retarded_arm = 0
set disarm_kill_switch = 1
set auto_disarm_delay = 5
set small_angle = 25
set flaps_speed = 0
set fixedwing_althold_dir = 1
set serial_port_1_scenario = 5
set serial_port_2_scenario = 2
set serial_port_3_scenario = 4
set serial_port_4_scenario = 0

set reboot_character = 82
set msp_baudrate = 19200
set cli_baudrate = 19200
set gps_baudrate = 57600
set gps_passthrough_baudrate = 19200
set gps_provider = 1
set gps_sbas_mode = 2
set gps_auto_config = 1
set gps_auto_baud = 0
set serialrx_provider = 0
set spektrum_sat_bind = 0
set telemetry_provider = 0
set telemetry_switch = 0
set telemetry_inversion = 1
set frsky_default_lattitude = 0.000
set frsky_default_longitude = 0.000
set frsky_coordinates_format = 0
set frsky_unit = 0

set battery_capacity = 0
set vbat_scale = 110
set vbat_max_cell_voltage = 43
set vbat_min_cell_voltage = 33
set vbat_warning_cell_voltage = 35
set current_meter_scale = 400
set current_meter_offset = 0
set multiwii_current_meter_output = 0
set current_meter_type = 1
set align_gyro = 0
set align_acc = 0
set align_mag = 0
set align_board_roll = 0
set align_board_pitch = 0
set align_board_yaw = 0
set max_angle_inclination = 500
set gyro_lpf = 42
set moron_threshold = 32
set gyro_cmpf_factor = 600
set gyro_cmpfm_factor = 250
set yaw_control_direction = 1
set acc_hardware = 0
set mag_hardware = 0
set blackbox_rate_num = 1
set blackbox_rate_denom = 1

# dump profile

# profile
profile 0

# aux
aux 0 0 1 1375 1700
aux 1 0 0 900 900
aux 2 0 0 900 900
aux 3 0 0 900 900
aux 4 0 0 900 900
aux 5 0 0 900 900
aux 6 0 0 900 900
aux 7 0 0 900 900
aux 8 0 0 900 900
aux 9 0 0 900 900
aux 10 0 0 900 900
aux 11 0 0 900 900
aux 12 0 0 900 900
aux 13 0 0 900 900
aux 14 0 0 900 900
aux 15 0 0 900 900
aux 16 0 0 900 900
aux 17 0 0 900 900
aux 18 0 0 900 900
aux 19 0 0 900 900
aux 20 0 0 900 900
aux 21 0 0 900 900
aux 22 0 0 900 900
aux 23 0 0 900 900
aux 24 0 0 900 900
aux 25 0 0 900 900
aux 26 0 0 900 900
aux 27 0 0 900 900
aux 28 0 0 900 900
aux 29 0 0 900 900
aux 30 0 0 900 900
aux 31 0 0 900 900
aux 32 0 0 900 900
aux 33 0 0 900 900
aux 34 0 0 900 900
aux 35 0 0 900 900
aux 36 0 0 900 900
aux 37 0 0 900 900
aux 38 0 0 900 900
aux 39 0 0 900 900

# adjrange
adjrange 0 0 0 900 900 0 0
adjrange 1 0 0 900 900 0 0
adjrange 2 0 0 900 900 0 0
adjrange 3 0 0 900 900 0 0
adjrange 4 0 0 900 900 0 0
adjrange 5 0 0 900 900 0 0
adjrange 6 0 0 900 900 0 0
adjrange 7 0 0 900 900 0 0
adjrange 8 0 0 900 900 0 0
adjrange 9 0 0 900 900 0 0
adjrange 10 0 0 900 900 0 0
adjrange 11 0 0 900 900 0 0

set gps_pos_p = 15
set gps_pos_i = 0
set gps_pos_d = 0
set gps_posr_p = 34
set gps_posr_i = 14
set gps_posr_d = 53
set gps_nav_p = 25
set gps_nav_i = 33
set gps_nav_d = 83
set gps_wp_radius = 200
set nav_controls_heading = 1
set nav_speed_min = 100
set nav_speed_max = 300
set nav_slew_rate = 30
set alt_hold_deadband = 40
set alt_hold_fast_change = 1
set deadband = 0
set yaw_deadband = 0
set throttle_correction_value = 0
set throttle_correction_angle = 800
set yaw_direction = 1
set tri_unarmed_servo = 1
set default_rate_profile = 0
set failsafe_delay = 10
set failsafe_off_delay = 200
set failsafe_throttle = 1200
set failsafe_min_usec = 985
set failsafe_max_usec = 2115
set gimbal_flags = 1
set acc_lpf_factor = 4
set accxy_deadband = 40
set accz_deadband = 40
set accz_lpf_cutoff = 5.000
set acc_unarmedcal = 1
set acc_trim_pitch = 0
set acc_trim_roll = 0
set baro_tab_size = 21
set baro_noise_lpf = 0.600
set baro_cf_vel = 0.985
set baro_cf_alt = 0.965
set mag_declination = 0
set pid_controller = 0
set p_pitch = 40
set i_pitch = 30
set d_pitch = 23
set p_roll = 40
set i_roll = 30
set d_roll = 23
set p_yaw = 85
set i_yaw = 45
set d_yaw = 0
set p_pitchf = 2.500
set i_pitchf = 0.600
set d_pitchf = 0.060
set p_rollf = 2.500
set i_rollf = 0.600
set d_rollf = 0.060
set p_yawf = 8.000
set i_yawf = 0.500
set d_yawf = 0.050
set level_horizon = 3.000
set level_angle = 5.000
set sensitivity_horizon = 75
set p_alt = 50
set i_alt = 0
set d_alt = 0
set p_level = 90
set i_level = 10
set d_level = 100
set p_vel = 120
set i_vel = 45
set d_vel = 1

# dump rates

# rateprofile
rateprofile 0

set rc_rate = 90
set rc_expo = 65
set thr_mid = 50
set thr_expo = 0
set roll_pitch_rate = 0
set yaw_rate = 0
set tpa_rate = 0
set tpa_breakpoint = 1500

Thanks, again everyone!

Special shout out to everyone contributing to these amazing products. Please keep going. We know it's a labor of love much more than it is money and we truly appreciate it! :D

Cheers!
DC

WellCrafted
Posts: 3
Joined: Thu Jul 23, 2015 9:07 pm

Re: Naze32 Full / Taranis Plus / D4R-II / Telemetry

Post by WellCrafted »

Are you still having problems figuring this out? https://www.youtube.com/watch?v=_1RWb49wjjI&list=PLxeXlhhg8Z8PdsGtMwYPIIS3-QXrbM0Xf This video helped me get up and running. You need watch the all the videos esp the last video which is probably the options you missed in cleanflight.

User avatar
DirtCreature
Posts: 3
Joined: Sat Nov 22, 2014 7:42 pm

Re: Naze32 Full / Taranis Plus / D4R-II / Telemetry

Post by DirtCreature »

WellCrafted wrote:Are you still having problems figuring this out? https://www.youtube.com/watch?v=_1RWb49wjjI&list=PLxeXlhhg8Z8PdsGtMwYPIIS3-QXrbM0Xf This video helped me get up and running. You need watch the all the videos esp the last video which is probably the options you missed in cleanflight.


Thanks for posting. I should have followed up!

Turns out that the green lead connecting to the D4R-II was broken somewhere. I spent hours and hours looking for a solution until I learned that valuable lesson: use a multimeter to tone connections.

Thanks again, tho!

Post Reply