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
Quad listing and not at %100
#1
Alright!! So, learned some lessons this time around (props to unseen for helping me on the path to enlightenment!). The issue is, ~50% throttle on punchouts, and one ESC is not producing. What I mean, is on punchout, all are giving me around 50% power, except #4 which is pegged at 100% as the quad lists over. Dumping the data and the blackbox. This was a live flight, props on  Wink. Quad was battery powered on level ground, so the gyro should not be an issue. ESCs had been calibrated, but now trying to calibrate them and they do not respond. 

Happens the same as this guys video
 



Quad:
Armattan Chameleon
DYS XSD30AV2
Emax 2205 2300KV
CL Racing F4 fc
TBS Unify Pro HV
X4RSB Frsky
ZOP 1500mAH battery (45C)

Log of flight


Code:
# dump

# version
# Betaflight / CLRACINGF4 (CLR4) 3.2.0 Sep 11 2017 / 06:31:34 (649ccd7c7) MSP API: 1.36

# name
name r3ptile

# resources
resource BEEPER 1 B04
resource MOTOR 1 B00
resource MOTOR 2 B01
resource MOTOR 3 A03
resource MOTOR 4 A02
resource MOTOR 5 B08
resource MOTOR 6 NONE
resource MOTOR 7 NONE
resource MOTOR 8 NONE
resource SERVO 1 NONE
resource SERVO 2 NONE
resource SERVO 3 NONE
resource SERVO 4 NONE
resource SERVO 5 NONE
resource SERVO 6 NONE
resource SERVO 7 NONE
resource SERVO 8 NONE
resource PPM 1 NONE
resource PWM 1 NONE
resource PWM 2 NONE
resource PWM 3 NONE
resource PWM 4 NONE
resource PWM 5 NONE
resource PWM 6 NONE
resource PWM 7 NONE
resource PWM 8 NONE
resource LED_STRIP 1 B08
resource SERIAL_TX 1 A09
resource SERIAL_TX 2 NONE
resource SERIAL_TX 3 B10
resource SERIAL_TX 4 A00
resource SERIAL_TX 5 NONE
resource SERIAL_TX 6 C06
resource SERIAL_TX 7 NONE
resource SERIAL_TX 8 NONE
resource SERIAL_TX 9 NONE
resource SERIAL_TX 10 NONE
resource SERIAL_TX 11 NONE
resource SERIAL_RX 1 A10
resource SERIAL_RX 2 NONE
resource SERIAL_RX 3 B11
resource SERIAL_RX 4 A01
resource SERIAL_RX 5 NONE
resource SERIAL_RX 6 C07
resource SERIAL_RX 7 NONE
resource SERIAL_RX 8 NONE
resource SERIAL_RX 9 NONE
resource SERIAL_RX 10 NONE
resource SERIAL_RX 11 NONE
resource INVERTER 1 C00
resource INVERTER 2 NONE
resource INVERTER 3 NONE
resource INVERTER 4 NONE
resource INVERTER 5 NONE
resource INVERTER 6 NONE
resource INVERTER 7 NONE
resource INVERTER 8 NONE
resource INVERTER 9 NONE
resource INVERTER 10 NONE
resource INVERTER 11 NONE
resource LED 1 B05
resource LED 2 NONE
resource LED 3 NONE
resource RX_BIND 1 NONE
resource RX_BIND_PLUG 1 NONE
resource TRANSPONDER 1 NONE
resource SPI_SCK 1 A05
resource SPI_SCK 2 B13
resource SPI_SCK 3 C10
resource SPI_MISO 1 A06
resource SPI_MISO 2 B14
resource SPI_MISO 3 C11
resource SPI_MOSI 1 A07
resource SPI_MOSI 2 B15
resource SPI_MOSI 3 C12
resource ESCSERIAL 1 B09
resource CAMERA_CONTROL 1 B09
resource ADC_BATT 1 C02
resource ADC_RSSI 1 C03
resource ADC_CURR 1 C01
resource ADC_EXT 1 NONE

# mixer
mixer QUADX

mmix reset


# servo
servo 0 1000 2000 1500 100 -1
servo 1 1000 2000 1500 100 -1
servo 2 1000 2000 1500 100 -1
servo 3 1000 2000 1500 100 -1
servo 4 1000 2000 1500 100 -1
servo 5 1000 2000 1500 100 -1
servo 6 1000 2000 1500 100 -1
servo 7 1000 2000 1500 100 -1

# servo mix
smix reset



# feature
feature -RX_PPM
feature -INFLIGHT_ACC_CAL
feature -RX_SERIAL
feature -MOTOR_STOP
feature -SERVO_TILT
feature -SOFTSERIAL
feature -GPS
feature -SONAR
feature -TELEMETRY
feature -3D
feature -RX_PARALLEL_PWM
feature -RX_MSP
feature -RSSI_ADC
feature -LED_STRIP
feature -DISPLAY
feature -OSD
feature -CHANNEL_FORWARDING
feature -TRANSPONDER
feature -AIRMODE
feature -RX_SPI
feature -SOFTSPI
feature -ESC_SENSOR
feature -ANTI_GRAVITY
feature -DYNAMIC_FILTER
feature RX_SERIAL
feature TELEMETRY
feature RSSI_ADC
feature OSD
feature DYNAMIC_FILTER

# 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 -MULTI_BEEPS
beeper DISARM_REPEAT
beeper -ARMED
beeper -SYSTEM_INIT
beeper -ON_USB
beeper -BLACKBOX_ERASE

# map
map AETR1234

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

# led
led 0 0,0::C:0
led 1 0,0::C:0
led 2 0,0::C:0
led 3 0,0::C:0
led 4 0,0::C:0
led 5 0,0::C:0
led 6 0,0::C:0
led 7 0,0::C:0
led 8 0,0::C:0
led 9 0,0::C:0
led 10 0,0::C:0
led 11 0,0::C:0
led 12 0,0::C:0
led 13 0,0::C:0
led 14 0,0::C:0
led 15 0,0::C:0
led 16 0,0::C:0
led 17 0,0::C:0
led 18 0,0::C:0
led 19 0,0::C:0
led 20 0,0::C:0
led 21 0,0::C:0
led 22 0,0::C:0
led 23 0,0::C:0
led 24 0,0::C:0
led 25 0,0::C:0
led 26 0,0::C:0
led 27 0,0::C:0
led 28 0,0::C:0
led 29 0,0::C:0
led 30 0,0::C:0
led 31 0,0::C:0

# color
color 0 0,0,0
color 1 0,255,255
color 2 0,0,255
color 3 30,0,255
color 4 60,0,255
color 5 90,0,255
color 6 120,0,255
color 7 150,0,255
color 8 180,0,255
color 9 210,0,255
color 10 240,0,255
color 11 270,0,255
color 12 300,0,255
color 13 330,0,255
color 14 0,0,0
color 15 0,0,0

# mode_color
mode_color 0 0 1
mode_color 0 1 11
mode_color 0 2 2
mode_color 0 3 13
mode_color 0 4 10
mode_color 0 5 3
mode_color 1 0 5
mode_color 1 1 11
mode_color 1 2 3
mode_color 1 3 13
mode_color 1 4 10
mode_color 1 5 3
mode_color 2 0 10
mode_color 2 1 11
mode_color 2 2 4
mode_color 2 3 13
mode_color 2 4 10
mode_color 2 5 3
mode_color 3 0 8
mode_color 3 1 11
mode_color 3 2 4
mode_color 3 3 13
mode_color 3 4 10
mode_color 3 5 3
mode_color 4 0 7
mode_color 4 1 11
mode_color 4 2 3
mode_color 4 3 13
mode_color 4 4 10
mode_color 4 5 3
mode_color 5 0 9
mode_color 5 1 11
mode_color 5 2 2
mode_color 5 3 13
mode_color 5 4 10
mode_color 5 5 3
mode_color 6 0 6
mode_color 6 1 10
mode_color 6 2 1
mode_color 6 3 0
mode_color 6 4 0
mode_color 6 5 2
mode_color 6 6 3
mode_color 6 7 6
mode_color 6 8 0
mode_color 6 9 0
mode_color 6 10 0
mode_color 7 0 3

# aux
aux 0 0 0 900 1500
aux 1 2 1 900 1200
aux 2 26 3 900 1400
aux 3 28 1 1800 2100
aux 4 35 2 1500 2100
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

# 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
adjrange 12 0 0 900 900 0 0
adjrange 13 0 0 900 900 0 0
adjrange 14 0 0 900 900 0 0

# rxrange
rxrange 0 1000 2000
rxrange 1 1000 2000
rxrange 2 1000 2000
rxrange 3 1000 2000

# vtx
vtx 0 0 0 0 900 900
vtx 1 0 0 0 900 900
vtx 2 0 0 0 900 900
vtx 3 0 0 0 900 900
vtx 4 0 0 0 900 900
vtx 5 0 0 0 900 900
vtx 6 0 0 0 900 900
vtx 7 0 0 0 900 900
vtx 8 0 0 0 900 900
vtx 9 0 0 0 900 900

# rxfail
rxfail 0 a
rxfail 1 a
rxfail 2 a
rxfail 3 a
rxfail 4 h
rxfail 5 h
rxfail 6 h
rxfail 7 h
rxfail 8 h
rxfail 9 h
rxfail 10 h
rxfail 11 h
rxfail 12 h
rxfail 13 h
rxfail 14 h
rxfail 15 h
rxfail 16 h
rxfail 17 h

# master
set align_gyro = DEFAULT
set gyro_lpf = OFF
set gyro_sync_denom = 1
set gyro_lowpass_type = PT1
set gyro_lowpass_hz = 90
set gyro_notch1_hz = 400
set gyro_notch1_cutoff = 300
set gyro_notch2_hz = 200
set gyro_notch2_cutoff = 100
set moron_threshold = 48
set gyro_use_32khz = OFF
set align_acc = DEFAULT
set acc_hardware = AUTO
set acc_lpf_hz = 10
set acc_trim_pitch = 0
set acc_trim_roll = 0
set mid_rc = 1500
set min_check = 1050
set max_check = 1900
set rssi_channel = 0
set rssi_scale = 41
set rssi_invert = OFF
set rc_interp = AUTO
set rc_interp_ch = RP
set rc_interp_int = 19
set fpv_mix_degrees = 0
set max_aux_channels = 14
set serialrx_provider = SBUS
set sbus_inversion = ON
set spektrum_sat_bind = 0
set spektrum_sat_bind_autoreset = 1
set airmode_start_throttle = 1350
set rx_min_usec = 885
set rx_max_usec = 2115
set serialrx_halfduplex = OFF
set input_filtering_mode = OFF
set blackbox_p_denom = 16
set blackbox_device = SDCARD
set blackbox_on_motor_test = OFF
set blackbox_record_acc = ON
set min_throttle = 1024
set max_throttle = 2000
set min_command = 1000
set dshot_idle_value = 500
set use_unsynced_pwm = OFF
set motor_pwm_protocol = DSHOT300
set motor_pwm_rate = 480
set motor_pwm_inversion = OFF
set thr_corr_value = 0
set thr_corr_angle = 800
set failsafe_delay = 4
set failsafe_off_delay = 10
set failsafe_throttle = 1000
set failsafe_kill_switch = OFF
set failsafe_throttle_low_delay = 100
set failsafe_procedure = DROP
set align_board_roll = 0
set align_board_pitch = 0
set align_board_yaw = 0
set gimbal_mode = NORMAL
set bat_capacity = 1500
set vbat_max_cell_voltage = 43
set vbat_full_cell_voltage = 41
set vbat_min_cell_voltage = 33
set vbat_warning_cell_voltage = 35
set vbat_hysteresis = 1
set current_meter = ADC
set battery_meter = ADC
set vbat_detect_cell_voltage = 30
set use_vbat_alerts = ON
set use_cbat_alerts = OFF
set cbat_alert_percent = 10
set vbat_cutoff_percent = 100
set vbat_scale = 110
set ibata_scale = 250
set ibata_offset = 0
set ibatv_scale = 0
set ibatv_offset = 0
set beeper_inversion = ON
set beeper_od = OFF
set beeper_frequency = 3800
set beeper_dshot = ON
set yaw_motors_reversed = OFF
set 3d_deadband_low = 1406
set 3d_deadband_high = 1514
set 3d_neutral = 1460
set 3d_deadband_throttle = 50
set servo_center_pulse = 1500
set servo_pwm_rate = 50
set servo_lowpass_hz = 0
set tri_unarmed_servo = ON
set channel_forwarding_start = 4
set reboot_character = 82
set serial_update_rate_hz = 100
set accxy_deadband = 40
set accz_deadband = 40
set acc_unarmedcal = ON
set imu_dcm_kp = 2500
set imu_dcm_ki = 0
set small_angle = 25
set auto_disarm_delay = 5
set disarm_kill_switch = ON
set gyro_cal_on_first_arm = OFF
set gps_provider = NMEA
set gps_sbas_mode = AUTO
set gps_auto_config = ON
set gps_auto_baud = OFF
set gps_wp_radius = 200
set nav_controls_heading = ON
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 = ON
set deadband = 0
set yaw_deadband = 0
set yaw_control_reversed = OFF
set pid_process_denom = 4
set tlm_switch = OFF
set tlm_inverted = OFF
set tlm_halfduplex = ON
set frsky_default_lat = 0
set frsky_default_long = 0
set frsky_gps_format = 0
set frsky_unit = IMPERIAL
set frsky_vfas_precision = 0
set hott_alarm_int = 5
set pid_in_tlm = OFF
set report_cell_voltage = OFF
set ledstrip_visual_beeper = OFF
set sdcard_dma = OFF
set osd_units = METRIC
set osd_rssi_alarm = 20
set osd_cap_alarm = 2200
set osd_alt_alarm = 100
set osd_ah_max_pit = 20
set osd_ah_max_rol = 40
set osd_tim1 = 2560
set osd_tim2 = 2561
set osd_vbat_pos = 2072
set osd_rssi_pos = 2048
set osd_tim_1_pos = 54
set osd_tim_2_pos = 33
set osd_flymode_pos = 2381
set osd_throttle_pos = 225
set osd_vtx_channel_pos = 377
set osd_crosshairs = 200
set osd_ah_sbar = 200
set osd_ah_pos = 200
set osd_current_pos = 385
set osd_mah_drawn_pos = 353
set osd_craft_name_pos = 362
set osd_gps_speed_pos = 218
set osd_gps_lon_pos = 82
set osd_gps_lat_pos = 65
set osd_gps_sats_pos = 51
set osd_home_dir_pos = 302
set osd_home_dist_pos = 303
set osd_compass_bar_pos = 266
set osd_altitude_pos = 504
set osd_pid_roll_pos = 423
set osd_pid_pitch_pos = 455
set osd_pid_yaw_pos = 487
set osd_debug_pos = 1
set osd_power_pos = 321
set osd_pidrate_profile_pos = 345
set osd_warnings_pos = 2377
set osd_avg_cell_voltage_pos = 24
set osd_pit_ang_pos = 257
set osd_rol_ang_pos = 289
set osd_battery_usage_pos = 392
set osd_disarmed_pos = 2218
set osd_nheading_pos = 311
set osd_nvario_pos = 279
set osd_esc_tmp_pos = 82
set osd_esc_rpm_pos = 83
set osd_stat_max_spd = ON
set osd_stat_max_dist = OFF
set osd_stat_min_batt = ON
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_endbatt = OFF
set osd_stat_bb_no = ON
set osd_stat_tim_1 = OFF
set osd_stat_tim_2 = ON
set task_statistics = ON
set debug_mode = NONE
set cpu_overclock = OFF
set pwr_on_arm_grace = 5
set vtx_halfduplex = ON
set vcd_video_system = 0
set vcd_h_offset = 0
set vcd_v_offset = 0
set displayport_msp_col_adjust = 0
set displayport_msp_row_adjust = 0
set displayport_max7456_col_adjust = 0
set displayport_max7456_row_adjust = 0
set displayport_max7456_inv = OFF
set displayport_max7456_blk = 0
set displayport_max7456_wht = 2
set esc_sensor_halfduplex = OFF
set led_inversion = 0
set camera_control_mode = HARDWARE_PWM
set camera_control_ref_voltage = 330
set camera_control_key_delay = 180
set camera_control_internal_resistance = 470

# profile
profile 0

set dterm_lowpass_type = BIQUAD
set dterm_lowpass = 100
set dterm_notch_hz = 260
set dterm_notch_cutoff = 160
set vbat_pid_gain = OFF
set pid_at_min_throttle = ON
set anti_gravity_threshold = 350
set anti_gravity_gain = 1000
set setpoint_relax_ratio = 100
set dterm_setpoint_weight = 0
set acc_limit_yaw = 100
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_windup = 50
set iterm_limit = 150
set pidsum_limit = 500
set pidsum_limit_yaw = 400
set yaw_lowpass = 0
set p_pitch = 58
set i_pitch = 50
set d_pitch = 35
set p_roll = 40
set i_roll = 40
set d_roll = 30
set p_yaw = 70
set i_yaw = 45
set d_yaw = 20
set p_alt = 50
set i_alt = 0
set d_alt = 0
set p_level = 50
set i_level = 50
set d_level = 75
set p_vel = 55
set i_vel = 55
set d_vel = 75
set level_limit = 55
set horizon_tilt_effect = 75
set horizon_tilt_expert_mode = OFF
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

# rateprofile
rateprofile 0

set rc_rate = 100
set rc_rate_yaw = 100
set rc_expo = 0
set rc_expo_yaw = 0
set thr_mid = 50
set thr_expo = 0
set roll_srate = 70
set pitch_srate = 70
set yaw_srate = 70
set tpa_rate = 10
set tpa_breakpoint = 1650
Reply
Login to remove this ad | Register Here
#2
One motor only being at 100% means there's something wrong with that motor or esc or maybe the solder joints... The other motors are held back in order to keep attitude.

No clue about the calibration issue though.
[-] The following 1 user Likes fftunes's post:
  • s3npai
Reply
#3
Pretty sure it is the ESC. I just replaced this one and will see. I have noticed that the same ESC burns up (same arm) each time. I have swapped motors to see if it could be the motor. Is there any way a flight controller can toast an ESC?

Also, on the calibration issue, I fixed that. MY ESCs are set to DShot300, and DShot is already calibrated. However you can force a calibration on them by putting them in MultiShot/OneShot from the config tab, doing a normal calibration, and then setting them back to DShot.
Reply
#4
Hm maybe because of timer issues... On some versions of betaflight there was a cli variable called "sdcard_dma" or something similar which was often recommended to turn off when such issues came up.
Reply
#5
fftunes Wrote:Hm maybe because of timer issues... On some versions of betaflight there was a cli variable called "sdcard_dma" or something similar which was often recommended to turn off when such issues came up.


Pretty sure I found the issue. So I have noticed that when I use the artificial horizon, even after starting it up on level ground, it seems to yaw left. No idea why. Pulled up the sensors tab and found this gem (see attachment). 
   

It starts off when plugged in on zero and slowly rises up to around 10. Pretty sure that gyro ate it at some point. I would assume that, coupled with a bad esc is causing these problems.
Reply
#6
It certainly looks like there's a problem with the ESC that drives motor number 4. As you can see in your log, the craft actually starts to tilt towards motor 4 when the motor is being asked to deliver maximum power. If changing the ESC does not solve the problem, check carefully that none of the mounting screws for motor 4 are too long.

If any of your mounting screws are too long they can short motor windings to each other or to the frame.

The artificial horizon on the OSD is derived from the accelerometer data, not the gyro data. You should calibrate the accelerometer in the configurator while your quad is level.

The gyro measures the speed of rotation around each axis. What you show happening in your last post is definitely not right. Unless the quad was actually spinning clockwise around the X axis at 8 degrees per second, I'd suspect there is something wrong with the gyro. However, I don't actually see that behaviour in your black box log. Even right at the end of the flight, when you return the sticks to centre, the gyros return to zero on all three axes.
Reply
#7
unseen Wrote:It certainly looks like there's a problem with the ESC that drives motor number 4. As you can see in your log, the craft actually starts to tilt towards motor 4 when the motor is being asked to deliver maximum power. If changing the ESC does not solve the problem, check carefully that none of the mounting screws for motor 4 are too long.

If any of your mounting screws are too long they can short motor windings to each other or to the frame.

The artificial horizon on the OSD is derived from the accelerometer data, not the gyro data. You should calibrate the accelerometer in the configurator while your quad is level.

The gyro measures the speed of rotation around each axis. What you show happening in your last post is definitely not right. Unless the quad was actually spinning clockwise around the X axis at 8 degrees per second, I'd suspect there is something wrong with the gyro. However, I don't actually see that behaviour in your black box log. Even right at the end of the flight, when you return the sticks to centre, the gyros return to zero on all three axes.

Yea, checked the screws. The things are almost too short to screw in enough. 

Pretty sure the horizon issue was because I was arming on the hood of my car, which is tilted. However, even when doing it on the ground, the acc. would be good, but the gyro would still drift.

Not sure entirely on the gyro issue. I did email Mr. Cheng, and he responded almost immediately. Sent him a pic of the gyro sensor data and he said I can send it to him for repair, if possible. That guy is AWESOME! I plugged in a battery a few minutes ago and one of the motors that were on that same failing side put on a smoke show. So, it just keeps getting more bizarre. However, considering it was on the same side as the ESCs that kept failing, I am pretty sure it was bad in the first place. So, now to the corner to get enough money for a new set of motors. I have lost trust in these used ones.
Reply
#8
From what I understand from your posts, you've replaced the same ESC several times and you've also swapped motors around without the problem following the motor.

If that's correct, then either you are unlucky enough to have two faulty ESCs, two faulty motors or there is something you are doing wrong.

The flight controller itself can't cause an ESC to smoke a motor. The only thing that applies power to the motor is the ESC and there is no command that the flight controller can send which would cause the ESC to smoke the motor. But, you say that the motors you have are used? As in, second hand? If so, maybe the previous owner used screws that were too long and damaged the windings. An intermittent short circuit on the motor windings would certainly cause problems driving the motor and even cause it to burn up when the ESC uses the motor to make the beep sounds you get on power up.
Reply
#9
While you are waiting for new parts, build yourself a smoke stopper and save yourself from smoking motors and burning ESCs.
Reply
#10
unseen Wrote:While you are waiting for new parts, build yourself a smoke stopper and save yourself from smoking motors and burning ESCs.

Most definitely will! I have already got two of the techs I work with to build quads as well, so we will make it a community effort, lol!

Setup: Motors were second hand from RCGroups. ESCs were second hand as well.

As far as the ESCs, this is the order it has gone in.

Start:
35a BL Heli Bullet ESCs with current motors
 - Noticed the quad wanted to drift, half power only, and listing
 - No issue of ESCs failing
 - Figured issue was front left ESC
 - Ordered new DYS ESCs
 - Put on new ESCs and tested. Quad performed superbly, despite drift issue.
 - Second flight, next day, quad started listing again with power cuts
 - Replaced front left ESC and same thing. Half power and listing.

I have swapped the motors around (1 to 4, 2 to 3), but have noticed no issue there. The only thing I have noticed that is similar in all of the failures, is that these are always going out.[Image: JtiFieZ]

I have checked the ESCs, checking motor tab to ground, usually gives a reading of ~10kOhms. Except this side, whenever the ESC starts acting up, the reading goes to crap. Not even a solid Ohm. Not sure what is up with that. Would not think these motors would kill 30a ESCs. I think I am going nuts. I do have two more motors on order to replace the one that smoked, and one that gave me high  amperage leakage during the test. So we shall see. Couple that all with a new FC, and if this thing does not fly well, I believe someone will be getting a great deal on a barely used Armattan frame, lol.
Reply
#11
I'd never buy second hand motors or ESCs. You've just no idea how the previous owner has treated them. I don't really understand what you mean when you talk about 'checking motor tab to ground'. Can you describe what you are measuring? From where to where? Under what conditions?

Measuring the resistance from a motor output on the ESC to ground with no motor connected but the ESC connected to the flight controller can give you very misleading results. Just the residual charge on the gate of the output FET is enough to turn the FET on. This is why your motors can feel harder to turn just after flying, even though the battery is disconnected. An hour or so later, when all residual charge has leaked away, they will be easier to turn.

When you get your new parts, post some pictures of how you have put everything together.
[-] The following 1 user Likes unseen's post:
  • s3npai
Reply
#12
unseen Wrote:I'd never buy second hand motors or ESCs. You've just no idea how the previous owner has treated them. I don't really understand what you mean when you talk about 'checking motor tab to ground'. Can you describe what you are measuring? From where to where? Under what conditions?

Measuring the resistance from a motor output on the ESC to ground with no motor connected but the ESC connected to the flight controller can give you very misleading results. Just the residual charge on the gate of the output FET is enough to turn the FET on. This is why your motors can feel harder to turn just after flying, even though the battery is disconnected. An hour or so later, when all residual charge has leaked away, they will be easier to turn.

When you get your new parts, post some pictures of how you have put everything together.

Yea, will not be buying much else from there. Kind of a let down.

Anyways, I am measuring here[Image: 3NnLP]

The ESCs have been off the quad for a bit, and it has not been powered up in days at that point. I was trying to find something common between these ESCs that seem to keep going out, and that is all I could come up with. I had noticed at one point that a motor was just a tad slower than the others, and was curious if it had an effect.

Measuring on a Fluke 87 V, resistance setting.

I also measured the motors using the fluke on AC setting, and spinning the stator with a drill. Gave me 2 motors with a consistent reading (across leads 1-2,1-3,2-3) of around 409mV, and two motors (including the smoked one) with odd readings. One read a little high, around 420mV, and the other burned motor, read two phases around 409, and one phase at 390.

I will be shelving it for a bit until I get everything in. Sorry for all of the information dumping. I hope at least a little of this madness made sense! And thank you kindly for all of the wisdom!
Reply
#13
Hmm...I'm not quite sure how useful measuring the outputs of the ESC to ground is. Testing the motors as generators is a help for sure but I don't know if the variations you saw indicate a fault or not. Ideally, you'd want an inductance meter to test each phase and make sure they're within a few uH of each other, plus a 4-wire resistance meter to check the resistance of each phase.

I'll look forward to the next instalment!
Reply
#14
(16-Oct-2017, 08:17 PM)unseen Wrote: Hmm...I'm not quite sure how useful measuring the outputs of the ESC to ground is. Testing the motors as generators is a help for sur,e but I don't know if the variations you saw indicate a fault or not. Ideally, you'd want an inductance meter to test each phase and make sure they're within a few uH of each other, plus a 4-wire resistance meter to check the resistance of each phase.

I'll look forward to the next instalment!

Haha, Christ. I'd rather it not be looked forward to, lol. Almost foreboding. Anyways, to clarify a little on the ESC test I was doing. I found that the ESCs that we're performing optimally, would have uniform readings of 10.98kOhms. This was both the DYS and surprisingly, the Emax bullets as well. The ones that had issues, on that first side I highlighted would be off. Just found it odd. Not exactly sure how it applies, but it's data none the less. And yes, inductance meter would be sweet, but my shop (electronics shop) doesn't seem to have one Sad
[-] The following 1 user Likes s3npai's post:
  • unseen
Reply
#15
Out of idle curiosity, I just dug a bunch of random brand new ESCs out of my spares box and made the same measurement.

V1 RacerStar 20A BLHeli_S : 11K
DYS XM20A BLHeli : 11K
FVT Littlebee 20A BLHeli : 44K
FVT Spring 40A BLHeli_S: 54K

If I reverse the leads on my Fluke and put the positive probe on the ground wire, the resistance rises with each second I keep the probes on the device.

Maybe if there's a significant difference in the measurement between the three motor outputs and ground it might tell you something - there was no significant difference between terminals on the ESCs I tested.

If you look at the output stages of any modern ESC, there are three of these circuits:

[Image: YLm2LMpl.png]

A dedicated high and low side driver chip drives banks of high power MOSFETs to generate the output signal to the motors.

There's also the simpler transistor based way of doing it, but the result is pretty much the same:

[Image: mPkNuSLl.png]


Each phase output is connected to ground via a high resistance voltage divider and at the mid point to the MCU via a current limiting resistor. This circuit is used to observe the back EMF from a phase when it's not being driven.

What we're measuring with the positive on the phase output and the negative on ESC ground is the voltage divider and all the parallel resistances created by the rest of the devices on the phase output. There are a bunch of floating FETs and a driver in that circuit as well, so I'm surprised how consistent the resistances were, varying by at most 200 ohms.

I test ESCs by connecting them to a motor on my thrust stand and seeing if they can spin a motor and prop. If you don't have a thrust stand, screw a motor onto your bench! I power up the ESC for the first time on a current limited bench supply. The cheaper alternative is a smoke stopper.

Testing and checking stuff should be simple and quick.

Building should be careful, methodical and thorough.

After each step that involves soldering, I inspect every aspect with a microscope or loupe. I've picked off so many tiny little strands of wire and solder balls you wouldn't believe it and not all of them are mine! If you double check everything you do as you work, it's no more time and saves tears later. Once I'm finished with a build, I'm confident that unless I have a bad component, everything should work when I power up for the first time.

It's all too easy in this hobby to get bogged down in details, particularly if you're interested in electronics, robotics and computing. When I'm finished building a new quad, my checklist is short and simple:

1. Check resistance on battery input.
2. Power up flight controller with USB.
3. Power up quad from bench supply with max current set to about 750mA.

If these first three steps pass, I'm confident to connect a battery for the rest of the steps.

4. Check motor direction and correct as required.
5. Calibrate ESCs (if required).
6. Find and set min_throttle.
7. Bind and check receiver.
8. Set favourite rates and mode switches.
9. Check flight controller orientation and calibrate accelerometer.

Then I add props, go outside and fly!

Configuring the OSD, the FPV camera and fine tuning can be done after the line of sight maiden flight. 

I don't buy used stuff. Not ESCs or flight controllers, soldered to or not. Never motors, unless in unopened new packaging. You never know what people might knowingly or unknowingly pass off and it's hard to be sure you didn't buy a lemon before your quad falls out of the sky.


We're here if you need help!
[-] The following 2 users Like unseen's post:
  • s3npai, McDee
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  Need help with quad drifting…. danny 20 955 06-Apr-2024, 04:53 PM
Last Post: infrared4ever
  Anyone ever X-Ray a quad? Rob Axel 0 97 18-Mar-2024, 06:54 PM
Last Post: Rob Axel
  Where do I start PID tuning this quad? relentlesstech 15 281 17-Mar-2024, 05:22 PM
Last Post: Rob Axel
  Mid Air Radio Failure on a quad with RTH Pathfinder075 9 171 26-Feb-2024, 10:26 AM
Last Post: SnowLeopardFPV
  Can a DJI RC Motion 2 control anything other than a DJI quad? Wellcordinated 8 549 17-Feb-2024, 05:00 PM
Last Post: segler999


Login to remove this ad | Register Here