Hello guest, if you read this it means you are not registered. Click here to register in a few simple steps, you will enjoy all features of our Forum.
This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Issues Installing ELRS Reciever
#1
Hello everyone,

I am newer to the world of FPV and have recently purchased my first non-commercial FPV drone, a Venom H20 HD from Flywoo. Now for various reasons I ended up with a version that did not ship with a reciever (I had a deal for a v1 DJI controller but it fell through) and have decided to add my own ELRS reciever, so I purchased a Radiomaster RP1 and a matching Zorro TX, which I am very happy with. 

I have sucessfully soldered the reciever to the existing reciever wiring on the drone (I had it checked by an actual avionics specialist) and the reciever works. I've flashed the latest ELRS firmware onto both the TX and the RX and installed the necessary .lua scripts on the TX as well, and they pair up right away with eachother. The problem is the TX is not being recognized by the drone in Betaflight, so I'm going to assume that the RX and the FC are not communicating with eachother properly. The FC is a Goku Hex F411 and as such I checked the box in the ELRS configurator to invert the CRSF signal to allow it to communicate with the SBUS only FC, and also verified that the UART which is set to serial in BetaFlight matches the physical one on the FC. 

The problem I'm having is that I don't know if Flywoo did anything during the setup of this drone (because even though they ship a version with a CRSF reciever, this one was intended to use the built in DJI reciever in the Caddx Vista) that's causing me a problem, and since I don't yet know what exactly I don't know, I can't even Google an answer. If anyone has some insight I would be very greatful.
Reply
Login to remove this ad | Register Here
#2
While we’re waiting for someone more familiar with digital/dji to respond to this thread:

Can you please post clear photos of your wiring?
It would be helpful to see your wiring from the flight controller to your ELRS receiver, as well as the wiring going to where the vista meets the flight controller.

Just to verify, you have the Goku hex f411, not the Goku hex f405, correct?

The f411 has two full uarts. It is not sbus only.
If you are not using a dji controller, I believe you’ll need to disconnect the sbus wire between the flight controller and the vista.

After that, depending on how your receiver is wired, it may need to be reflashed if it is not connected up to an sbus pad.

I know you said you had your wiring checked, but, just to clarify, if you’re connected via sbus, it is the tx pad on the receiver that should be connected to the sbus pad.

If you are connected to a standard non inverted uart:
The tx pad on the receiver connects to the rx pad on the flight controller.
The rx pad on the receiver connects to the tx pad on the flight controller.
Dangerous operations.

Disclaimer: I don’t know wtf I’m talking about.
I wish I could get the smell of burnt electronics out of my nose.
Reply
#3
(28-Jan-2023, 08:26 AM)Lemonyleprosy Wrote: While we’re waiting for someone more familiar with digital/dji to respond to this thread:

Can you please post clear photos of your wiring?
It would be helpful to see your wiring from the flight controller to your ELRS receiver, as well as the wiring going to where the vista meets the flight controller.

Just to verify, you have the Goku hex f411, not the Goku hex f405, correct?

The f411 has two full uarts. It is not sbus only.
If you are not using a dji controller, I believe you’ll need to disconnect the sbus wire between the flight controller and the vista.

After that, depending on how your receiver is wired, it may need to be reflashed if it is not connected up to an sbus pad.

I know you said you had your wiring checked, but, just to clarify, if you’re connected via sbus, it is the tx pad on the receiver that should be connected to the sbus pad.

If you are connected to a standard non inverted uart:
The tx pad on the receiver connects to the rx pad on the flight controller.
The rx pad on the receiver connects to the tx pad on the flight controller.

Thank you for the quick reply. There's not a lot I can do at the moment, as I left my hex keys at my shop when I came home and now it's almost midnight and I'm not going back until tomorrow, so I'll have to wait to get those pictures. The parts list for the drone says that the FC is an F411, however I have no idea how to verify that. Because of the way it was wired up, I have no way of removing the FC from the drone to see the underside (I can still pull the vista off, which is stacked on top) because the wires from the motors are run to exactly the necessary length. I really don't want to start desoldering those things because they are unlabled and all black and I'll never get them all right again. I'll get some pictures of the wiring tomorrow, which would, in hindsight, have been a good idea while the quad was disassembled.
Reply
#4
Don’t need to see the bottom of the the board, just the top/sides where your receiver and vista are connected, as well as the wiring to the receiver itself.

Don’t desolder anything yet. Smile

Also, please post a dump and diff all.
(Connect to betaflight, click on the cli tab, type diff all and then hit enter, paste the result back here, then type dump and hit enter, and also paste that result back here.)
Dangerous operations.

Disclaimer: I don’t know wtf I’m talking about.
I wish I could get the smell of burnt electronics out of my nose.
Reply
#5
(28-Jan-2023, 08:58 AM)Lemonyleprosy Wrote: Don’t need to see the bottom of the the board, just the top/sides where your receiver and vista are connected, as well as the wiring to the receiver itself.

Don’t desolder anything yet. Smile

Once we’ve verified that your wiring is correct, please post a dump and diff all.
(Connect to betaflight, click on the cli tab, type diff all and hit enter, paste the result back here, and type dump and hit enter, and also paste that result back here.)

Will do. I wouldn't be surprised if the Betaflight config is all messed up now that I've spent 2 hours poking around at various things from a dozen different tutorials and videos when it could have been a wiring issue all along smh...
[-] The following 1 user Likes NyxOTNC's post:
  • Lemonyleprosy
Reply
#6
(28-Jan-2023, 08:58 AM)Lemonyleprosy Wrote: Don’t need to see the bottom of the the board, just the top/sides where your receiver and vista are connected, as well as the wiring to the receiver itself.

Don’t desolder anything yet. Smile

Also, please post a dump and diff all.
(Connect to betaflight, click on the cli tab, type diff all and then hit enter, paste the result back here, then type dump and hit enter, and also paste that result back here.)

Here are the photos of the wiring, I'll follow up with the info dumps in a bit if nothing seems horribly out of place. The image size limit on this forum is so low that the pictures have had to be massively compressed.

               
Reply
#7
It looks like for your receiver the RX and TX pins aren't correct. In Image 2-3, it looks like the yellow RX wire on your board goes to the RX pad on your receiver, and the white wire is the same for TX. On one end, you should swap these around.
[-] The following 1 user Likes matt0725's post:
  • Lemonyleprosy
Reply
#8
Yup, you’ve got your wiring wrong.

RX goes to TX, TX goes to RX. I know, it doesn’t make sense initially- I made the same mistake when I started out.
It makes sense once you understand that tx means transmit and rx means receive.

So, if you’re transmitting from something, you want the other thing to receive.

So, you’ll need to swap two wires to connect tx to rx and rx to tx.

Also, it looks like you are not connected to an sbus pad, so, you’ll also need to reflash your ELRS receiver- do not select the option to invert the signal this time.

After you fix your wiring and reflash your receiver, if it’s still not working please post your diff all and dump so that we can see if there’s anything wrong on the software side of things.
Dangerous operations.

Disclaimer: I don’t know wtf I’m talking about.
I wish I could get the smell of burnt electronics out of my nose.
Reply
#9
Based on the orientation of the osd chip on that board and the pad layout, I don’t think it’s an f411- or at least, it doesn’t line up to the f411 wiring diagram that I found. It does line up to the wiring diagram for an f745.

Can you please connect to betaflight, go to the cli tab, and type:

version

Then hit enter and paste the result back here?
I just want to make sure that we’re all looking at the right wiring diagram for the correct board.

Regardless, both boards show that you need to change your rx and tx wiring. Smile

[Image: vTw0DNal.jpg]
Dangerous operations.

Disclaimer: I don’t know wtf I’m talking about.
I wish I could get the smell of burnt electronics out of my nose.
Reply
#10
Thanks for all the help guys. I'll get on that tomorrow when I'm not so exhausted that I can't hold a soldering iron...
Reply
#11
(30-Jan-2023, 07:17 AM)NyxOTNC Wrote: Thanks for all the help guys. I'll get on that tomorrow when I'm not so exhausted that I can't hold a soldering iron...

Double check that the wiring from your vista to your flight controller is also going rx to tx and tx to rx while you’ve got it open, I was only paying attention to your ELRS receiver wiring.
Although, if it came installed, then it should be good, so if that’s the case, ignore this post.
Dangerous operations.

Disclaimer: I don’t know wtf I’m talking about.
I wish I could get the smell of burnt electronics out of my nose.
Reply
#12
Looking at your photos the FC in your Venom 20 HD is definitely the GOKU HEX F745 FC. Fkywoo only used an F411 FC on the analogue version of the Venom 20. All of the HD versions had an F745 FC installed.

Make sure your FC is flashed with Betaflight 4.2.x with the ExpressLRS receiver wired to the UART1 pads in the FC, then copy/paste all of the following commands into the CLI text and press <ENTER>. These are the Flywoo factory settings for a Venom 20 HD which has an ELRS receiver installed as found HERE.

You don't need to remove the SBUS wire between the Vista and the FC because it's wired to UART 4 which the factory CLI dump below just disables.

You will also need to re-flash your ExpressLRS receiver with the RCVR_INVERT_TX option switched OFF (unticked) because it doesn't need to invert the CRSF signal when connected to an F7 FC.

Code:
board_name FLYWOOF745HEX
manufacturer_id FLWO

# resources
resource BEEPER 1 D15
resource MOTOR 1 B00
resource MOTOR 2 B01
resource MOTOR 3 E09
resource MOTOR 4 E11
resource MOTOR 5 C09
resource MOTOR 6 A03
resource MOTOR 7 B04
resource MOTOR 8 B05
resource PPM 1 E13
resource LED_STRIP 1 D12
resource SERIAL_TX 1 A09
resource SERIAL_TX 2 D05
resource SERIAL_TX 3 B10
resource SERIAL_TX 4 A00
resource SERIAL_TX 5 C12
resource SERIAL_TX 6 C06
resource SERIAL_TX 7 E08
resource SERIAL_RX 1 A10
resource SERIAL_RX 2 D06
resource SERIAL_RX 3 B11
resource SERIAL_RX 4 A01
resource SERIAL_RX 5 D02
resource SERIAL_RX 6 C07
resource SERIAL_RX 7 E07
resource I2C_SCL 1 B06
resource I2C_SDA 1 B07
resource LED 1 A02
resource SPI_SCK 1 A05
resource SPI_SCK 2 B13
resource SPI_SCK 4 E02
resource SPI_MISO 1 A06
resource SPI_MISO 2 B14
resource SPI_MISO 4 E05
resource SPI_MOSI 1 A07
resource SPI_MOSI 2 B15
resource SPI_MOSI 4 E06
resource ADC_BATT 1 C03
resource ADC_RSSI 1 C05
resource ADC_CURR 1 C02
resource PINIO 1 C00
resource FLASH_CS 1 A04
resource OSD_CS 1 B12
resource GYRO_EXTI 1 E01
resource GYRO_CS 1 E04
resource USB_DETECT 1 A08

# timer
timer E13 AF1
# pin E13: TIM1 CH3 (AF1)
timer B00 AF2
# pin B00: TIM3 CH3 (AF2)
timer B01 AF2
# pin B01: TIM3 CH4 (AF2)
timer E09 AF1
# pin E09: TIM1 CH1 (AF1)
timer E11 AF1
# pin E11: TIM1 CH2 (AF1)
timer C09 AF3
# pin C09: TIM8 CH4 (AF3)
timer A03 AF2
# pin A03: TIM5 CH4 (AF2)
timer B03 AF1
# pin B03: TIM2 CH2 (AF1)
timer B04 AF2
# pin B04: TIM3 CH1 (AF2)
timer B05 AF2
# pin B05: TIM3 CH2 (AF2)
timer D12 AF2
# pin D12: TIM4 CH1 (AF2)

# dma
dma ADC 1 1
# ADC 1: DMA2 Stream 4 Channel 0
dma pin E13 1
# pin E13: DMA2 Stream 6 Channel 6
dma pin B00 0
# pin B00: DMA1 Stream 7 Channel 5
dma pin B01 0
# pin B01: DMA1 Stream 2 Channel 5
dma pin E09 2
# pin E09: DMA2 Stream 3 Channel 6
dma pin E11 1
# pin E11: DMA2 Stream 2 Channel 6
dma pin C09 0
# pin C09: DMA2 Stream 7 Channel 7
dma pin A03 0
# pin A03: DMA1 Stream 1 Channel 6
dma pin B03 0
# pin B03: DMA1 Stream 6 Channel 3
dma pin B04 0
# pin B04: DMA1 Stream 4 Channel 5
dma pin B05 0
# pin B05: DMA1 Stream 5 Channel 5
dma pin D12 0
# pin D12: DMA1 Stream 0 Channel 2

# mixer
mixer HEX6X

mmix reset

mmix 0  1.000 -0.500  0.866  1.000
mmix 1  1.000 -0.500 -0.866  1.000
mmix 2  1.000  0.500  0.866 -1.000
mmix 3  1.000  0.500 -0.866 -1.000
mmix 4  1.000 -1.000  0.000 -1.000
mmix 5  1.000  1.000  0.000  1.000

feature RX_SERIAL
feature MOTOR_STOP
feature -GPS
feature LED_STRIP
feature OSD
feature TELEMETRY
feature AIRMODE

# serial
serial 20 1 115200 57600 0 115200
serial 0 64 115200 57600 0 115200
serial 1 0 115200 9600 0 115200
serial 2 1 115200 57600 0 115200
serial 3 0 115200 57600 0 115200
serial 4 0 115200 57600 0 115200
serial 5 0 115200 57600 0 115200
serial 6 0 115200 57600 0 115200


# led
led 0 6,7::CO:8
led 1 7,7::CO:8
led 2 8,7::CO:8
led 3 9,7::CO:8

# aux
aux 0 0 1 1300 2100 0 0
aux 1 2 1 1700 2100 0 0
aux 2 0 0 900 900 0 0
aux 3 0 0 900 900 0 0
aux 4 0 0 900 900 0 0
aux 5 0 0 900 900 0 0
aux 6 0 0 900 900 0 0
aux 7 0 0 900 900 0 0
aux 8 0 0 900 900 0 0
aux 9 0 0 900 900 0 0
aux 10 0 0 900 900 0 0
aux 11 0 0 900 900 0 0
aux 12 0 0 900 900 0 0
aux 13 0 0 900 900 0 0
aux 14 0 0 900 900 0 0
aux 15 0 0 900 900 0 0
aux 16 0 0 900 900 0 0
aux 17 0 0 900 900 0 0
aux 18 0 0 900 900 0 0
aux 19 0 0 900 900 0 0

# beeper
beeper GYRO_CALIBRATED
beeper ARMING_GPS_FIX
beeper BAT_CRIT_LOW
beeper BAT_LOW
beeper GPS_STATUS
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

# rxfail
rxfail 6 s 2000

# master
set gyro_lowpass2_hz = 325
set dyn_lpf_gyro_min_hz = 260
set dyn_lpf_gyro_max_hz = 650
set acc_calibration = 56,4,-77,1
set mag_bustype = I2C
set mag_i2c_device = 1
set mag_hardware = NONE
set baro_bustype = I2C
set baro_i2c_device = 1
set rssi_channel = 12
set serialrx_provider = CRSF
set blackbox_device = SPIFLASH
set motor_pwm_protocol = DSHOT300
set failsafe_procedure = DROP
set current_meter = NONE
set battery_meter = ADC
set ibata_scale = 175
set beeper_inversion = ON
set beeper_od = OFF
set small_angle = 180
set gps_rescue_min_sats = 5
set gps_rescue_allow_arming_without_fix = ON
set osd_warn_arming_disable = ON
set osd_warn_batt_not_full = ON
set osd_warn_batt_warning = ON
set osd_warn_batt_critical = ON
set osd_warn_visual_beeper = ON
set osd_warn_crash_flip = ON
set osd_warn_esc_fail = ON
set osd_warn_core_temp = ON
set osd_warn_rc_smoothing = ON
set osd_warn_fail_safe = ON
set osd_warn_launch_control = ON
set osd_warn_no_gps_rescue = ON
set osd_warn_gps_rescue_disabled = ON
set osd_warn_rssi = OFF
set osd_warn_link_quality = OFF
set osd_warn_rssi_dbm = OFF
set osd_warn_over_cap = OFF
set osd_rssi_alarm = 20
set osd_link_quality_alarm = 80
set osd_rssi_dbm_alarm = -60
set osd_cap_alarm = 2200
set osd_alt_alarm = 100
set osd_distance_alarm = 0
set osd_esc_temp_alarm = -128
set osd_esc_rpm_alarm = -1
set osd_esc_current_alarm = -1
set osd_core_temp_alarm = 70
set osd_ah_max_pit = 20
set osd_ah_max_rol = 40
set osd_ah_invert = OFF
set osd_logo_on_arming = OFF
set osd_logo_on_arming_duration = 5
set osd_tim1 = 2560
set osd_tim2 = 2561
set osd_vbat_pos = 2304
set osd_rssi_pos = 2208
set osd_link_quality_pos = 234
set osd_rssi_dbm_pos = 128
set osd_tim_1_pos = 2400
set osd_tim_2_pos = 2368
set osd_remaining_time_estimate_pos = 234
set osd_flymode_pos = 2272
set osd_anti_gravity_pos = 234
set osd_g_force_pos = 234
set osd_throttle_pos = 234
set osd_vtx_channel_pos = 2325
set osd_crosshairs_pos = 205
set osd_ah_sbar_pos = 206
set osd_ah_pos = 78
set osd_current_pos = 140
set osd_mah_drawn_pos = 234
set osd_motor_diag_pos = 234
set osd_craft_name_pos = 2080
set osd_display_name_pos = 234
set osd_gps_speed_pos = 185
set osd_gps_lon_pos = 49
set osd_gps_lat_pos = 17
set osd_gps_sats_pos = 250
set osd_home_dir_pos = 217
set osd_home_dist_pos = 217
set osd_flight_dist_pos = 2201
set osd_compass_bar_pos = 234
set osd_altitude_pos = 2135
set osd_pid_roll_pos = 234
set osd_pid_pitch_pos = 234
set osd_pid_yaw_pos = 234
set osd_debug_pos = 234
set osd_power_pos = 234
set osd_pidrate_profile_pos = 234
set osd_warnings_pos = 2441
set osd_avg_cell_voltage_pos = 2336
set osd_pit_ang_pos = 234
set osd_rol_ang_pos = 234
set osd_battery_usage_pos = 234
set osd_disarmed_pos = 2411
set osd_nheading_pos = 234
set osd_nvario_pos = 234
set osd_esc_tmp_pos = 234
set osd_esc_rpm_pos = 234
set osd_esc_rpm_freq_pos = 234
set osd_rtc_date_time_pos = 234
set osd_adjustment_range_pos = 234
set osd_flip_arrow_pos = 2112
set osd_core_temp_pos = 2169
set osd_log_status_pos = 2144
set osd_stick_overlay_left_pos = 234
set osd_stick_overlay_right_pos = 234
set osd_stick_overlay_radio_mode = 2
set osd_rate_profile_name_pos = 234
set osd_pid_profile_name_pos = 234
set osd_profile_name_pos = 234
set osd_rcchannels_pos = 234
set osd_camera_frame_pos = 35
set osd_efficiency_pos = 234
set osd_stat_rtc_date_time = OFF
set osd_stat_tim_1 = OFF
set osd_stat_tim_2 = ON
set osd_stat_max_spd = ON
set osd_stat_max_dist = OFF
set osd_stat_min_batt = ON
set osd_stat_endbatt = OFF
set osd_stat_battery = OFF
set osd_stat_min_rssi = ON
set osd_stat_max_curr = ON
set osd_stat_used_mah = ON
set osd_stat_max_alt = OFF
set osd_stat_bbox = ON
set osd_stat_bb_no = ON
set osd_stat_max_g_force = OFF
set osd_stat_max_esc_temp = OFF
set osd_stat_max_esc_rpm = OFF
set osd_stat_min_link_quality = OFF
set osd_stat_flight_dist = OFF
set osd_stat_max_fft = OFF
set osd_stat_total_flights = OFF
set osd_stat_total_time = OFF
set osd_stat_total_dist = OFF
set osd_stat_min_rssi_dbm = OFF
set osd_profile = 1
set osd_profile_1_name = -
set osd_profile_2_name = -
set osd_profile_3_name = -
set osd_gps_sats_show_hdop = OFF
set osd_displayport_device = AUTO
set osd_rcchannels = -1,-1,-1,-1
set osd_camera_frame_width = 24
set osd_camera_frame_height = 11
set max7456_spi_bus = 2
set dashboard_i2c_bus = 1
set flash_spi_bus = 1
set gyro_1_bustype = SPI
set gyro_1_spibus = 4
set gyro_1_sensor_align = CW270
set gyro_1_align_yaw = 2700
set gyro_2_spibus = 4
set name = FLYWOO
set pid_process_denom = 2
set yaw_motors_reversed = ON

profile 0

# profile 0
set profile_name = -
set dyn_lpf_dterm_min_hz = 91
set dyn_lpf_dterm_max_hz = 221
set dyn_lpf_dterm_curve_expo = 5
set dterm_lowpass_type = PT1
set dterm_lowpass_hz = 150
set dterm_lowpass2_type = PT1
set dterm_lowpass2_hz = 195
set dterm_notch_hz = 0
set dterm_notch_cutoff = 0
set vbat_pid_gain = OFF
set vbat_sag_compensation = 0
set pid_at_min_throttle = ON
set anti_gravity_mode = SMOOTH
set anti_gravity_threshold = 250
set anti_gravity_gain = 3500
set feedforward_transition = 0
set acc_limit_yaw = 0
set acc_limit = 0
set crash_dthreshold = 50
set crash_gthreshold = 400
set crash_setpoint_threshold = 350
set crash_time = 500
set crash_delay = 0
set crash_recovery_angle = 10
set crash_recovery_rate = 100
set crash_limit_yaw = 200
set crash_recovery = OFF
set iterm_rotation = OFF
set iterm_relax = RP
set iterm_relax_type = SETPOINT
set iterm_relax_cutoff = 15
set iterm_windup = 100
set iterm_limit = 400
set pidsum_limit = 500
set pidsum_limit_yaw = 400
set yaw_lowpass_hz = 0
set throttle_boost = 5
set throttle_boost_cutoff = 15
set acro_trainer_angle_limit = 20
set acro_trainer_lookahead_ms = 50
set acro_trainer_debug_axis = ROLL
set acro_trainer_gain = 75
set p_pitch = 66
set i_pitch = 99
set d_pitch = 76
set f_pitch = 125
set p_roll = 61
set i_roll = 94
set d_roll = 70
set f_roll = 119
set p_yaw = 65
set i_yaw = 99
set d_yaw = 0
set f_yaw = 119
set angle_level_strength = 50
set horizon_level_strength = 50
set horizon_transition = 75
set level_limit = 55
set horizon_tilt_effect = 75
set horizon_tilt_expert_mode = OFF
set abs_control_gain = 0
set abs_control_limit = 90
set abs_control_error_limit = 20
set abs_control_cutoff = 11
set use_integrated_yaw = OFF
set integrated_yaw_relax = 200
set d_min_roll = 46
set d_min_pitch = 51
set d_min_yaw = 0
set d_min_boost_gain = 37
set d_min_advance = 20
set motor_output_limit = 100
set auto_profile_cell_count = 0
set launch_control_mode = NORMAL
set launch_trigger_allow_reset = ON
set launch_trigger_throttle_percent = 20
set launch_angle_limit = 0
set launch_control_gain = 40
set ff_interpolate_sp = AVERAGED_2
set ff_spike_limit = 60
set ff_max_rate_limit = 100
set ff_smooth_factor = 37
set ff_boost = 15
set idle_min_rpm = 0
set idle_adjustment_speed = 50
set idle_p = 50
set idle_pid_limit = 200
set idle_max_increase = 150
set level_race_mode = OFF

rateprofile 0

# rateprofile 0
set rateprofile_name = -
set thr_mid = 50
set thr_expo = 0
set rates_type = BETAFLIGHT
set roll_rc_rate = 100
set pitch_rc_rate = 100
set yaw_rc_rate = 100
set roll_expo = 0
set pitch_expo = 0
set yaw_expo = 0
set roll_srate = 70
set pitch_srate = 70
set yaw_srate = 70
set tpa_rate = 65
set tpa_breakpoint = 1250
set tpa_mode = D
set throttle_limit_type = OFF
set throttle_limit_percent = 100
set roll_rate_limit = 1998
set pitch_rate_limit = 1998
set yaw_rate_limit = 1998


# end the command batch
batch end


save
[-] The following 1 user Likes SnowLeopardFPV's post:
  • Lemonyleprosy
Reply
#13
I'm pleased to report that the drone is now working! I took it up for a quick flight around the yard and while I've got some tweaking to do, at least it's onto the fun little things that make this hobby so attractive.

I'd like to thank everyone who left suggestions, and especially to Lemonyleprosy for being a legend and SnowLeopard for the CLI code that enitrely fixed the issues I was having in betaflight.
[-] The following 2 users Like NyxOTNC's post:
  • Lemonyleprosy, ph2t
Reply
#14
Congratulations on getting it up in the air. It is a hell of an accomplishment. Smile

Happy flying!
Dangerous operations.

Disclaimer: I don’t know wtf I’m talking about.
I wish I could get the smell of burnt electronics out of my nose.
[-] The following 1 user Likes Lemonyleprosy's post:
  • tr8d3r8
Reply
#15
Amazing how these whoops literally drain energy!

Had the same problem, however. Analog. v2. at first sign of trouble I resorted to CP2102 bridge and flashed/upgraded ELRS receiver firmware & zero problems since except for HD goggles working perfectly with sbus wire removed from Vista. ?
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  Pavo Pico elrs bricked! Please help!! Jackstinn 10 275 21-Apr-2024, 04:06 PM
Last Post: mstc
  BetaFlight Connection Issues..... Coleon 17 612 02-Apr-2024, 12:26 PM
Last Post: iFly4rotors
Exclamation motors do not spin from reciever. PLZ HELP I NEED TO GET THIS TO WORK THIS WEEK lottacurry 15 283 21-Mar-2024, 10:46 PM
Last Post: mstc
  VTX+ELRS Placement JohnnyCornRocket 4 181 19-Mar-2024, 02:36 PM
Last Post: SnowLeopardFPV
Question Elrs receiver blinks green once? FeuerKai 5 213 09-Mar-2024, 10:05 PM
Last Post: FeuerKai


Login to remove this ad | Register Here