Naze32 Motors Oddity

[MinisterPhobia]

Brand new to Multi-rotors here, new to Aerial RC in general, actually. My apologies if this has already been answered somewhere already. I did ask Google and it told me that it didn't know what I was talking about (lots of search results, none that helped).

I've setup a mini(micro?) quad of the 220mm size with the Naze32, Mystery 12A ESCs (same as HK blueseries), and Sunnysky 2300KV motors.

Overall everything seems to be working when I'm using the Baseflight Configurator. If I go into Motor testing, I'm told that all four motors are spinning up at exactly the same time at the same rates. Everything appears good here.

When I switch over to my Tx and try to use it to spin things up, though, Motors 1 and 4 spin up the same, 2 starts up late and doesn't hit the max like 1 and 4, and 3 doesn't even make it to half power. The Tx is a Turnigy 9x (I know, not the greatest, but, for a brand new to me hobby, it fit the budget).

Using the Configurator, I've reset the settings on the FC and redid everything. Nothing changed. I made sure all the wiring was plugged in where it should be and that there were no shorts or anything like that. I haven't swapped the motors around yet to see if they're at fault, but, with the motor tests in Configurator working without issue, I would assume they're not at fault.

While I suspect this might be a setting error on my Tx, I'm not certain of this. Can anyone make any suggestions of other things to look at?

[scrat]

Did you calibrated esc's?

[timecop]

midrc, and your tx isn't trimmed at 1500.
this stuff is in the manual, come on.

[MinisterPhobia]

Did you calibrated esc's?

Yes.

midrc, and your tx isn't trimmed at 1500.
this stuff is in the manual, come on.

midrc is at 1500. I see nothing in the manual about settings on the Tx, nor does the manual explain how to "subtrim" each of the channels. Think you might be able to help with that rather than tell me that I didn't read the manual?

Here's the full current settings. I don't know if this will help at all:

Code: Select all

Current settings: 
looptime = 2500
emf_avoidance = 0
midrc = 1500
minthrottle = 1100
maxthrottle = 1850
mincommand = 1000
mincheck = 1100
maxcheck = 1900
deadband3d_low = 1406
deadband3d_high = 1514
neutral3d = 1460
deadband3d_throttle = 50
motor_pwm_rate = 400
servo_pwm_rate = 50
retarded_arm = 0
flaps_speed = 0
fixedwing_althold_dir = 1
reboot_character = 82
serial_baudrate = 115200
softserial_baudrate = 9600
softserial_1_inverted = 0
softserial_2_inverted = 0
gps_type = 0
gps_baudrate = 0
serialrx_type = 0
telemetry_provider = 0
telemetry_port = 0
telemetry_switch = 0
vbatscale = 110
currentscale = 400
currentoffset = 0
multiwiicurrentoutput = 0
vbatmaxcellvoltage = 43
vbatmincellvoltage = 33
power_adc_channel = 0
align_gyro = 0
align_acc = 0
align_mag = 0
align_board_roll = 0
align_board_pitch = 0
align_board_yaw = 0
yaw_control_direction = 1
acc_hardware = 0
max_angle_inclination = 500
moron_threshold = 32
gyro_lpf = 42
gyro_cmpf_factor = 600
gyro_cmpfm_factor = 250
pid_controller = 0
deadband = 0
yawdeadband = 0
alt_hold_throttle_neutral = 40
alt_hold_fast_change = 1
throttle_correction_value = 0
throttle_correction_angle = 800
rc_rate = 90
rc_expo = 65
thr_mid = 50
thr_expo = 0
roll_pitch_rate = 0
yaw_rate = 0
tpa_rate = 0
tpa_breakpoint = 1500
failsafe_delay = 10
failsafe_off_delay = 200
failsafe_throttle = 1200
failsafe_detect_threshold = 985
rssi_aux_channel = 0
yaw_direction = 1
tri_unarmed_servo = 1
gimbal_flags = 1
acc_lpf_factor = 4
accxy_deadband = 40
accz_deadband = 40
acc_unarmedcal = 1
small_angle = 25
acc_trim_pitch = 0
acc_trim_roll = 0
baro_tab_size = 21
baro_noise_lpf = 0.600
baro_cf_vel = 0.985
baro_cf_alt = 0.965
accz_lpf_cutoff = 5.000
mag_declination = 1650
gps_pos_p = 11
gps_pos_i = 0
gps_pos_d = 0
gps_posr_p = 20
gps_posr_i = 8
gps_posr_d = 45
gps_nav_p = 14
gps_nav_i = 20
gps_nav_d = 80
gps_wp_radius = 200
nav_controls_heading = 1
nav_speed_min = 100
nav_speed_max = 300
nav_slew_rate = 30
p_pitch = 40
i_pitch = 30
d_pitch = 23
p_roll = 40
i_roll = 30
d_roll = 23
p_yaw = 85
i_yaw = 45
d_yaw = 0
p_alt = 50
i_alt = 0
d_alt = 0
p_level = 90

[MinisterPhobia]

Nevermind. Figured it out.

[Hoppsan_84]

and what did you come up whit? You know so gogle can answer it next time

[MinisterPhobia]

It was, indeed, the subtrim issue. It took me nearly an hour to figure out WHERE the subtrim is, only to find out that it's on the Tx, not in the program.

While timecop was correct, the way he responded made me not want to look into this community any more deeply. Being that he's the main guy for the project (the only guy?), I would expect him to have a little more tolerance for noobs and perhaps actually explain things a bit. I'm assuming he wrote the "manual" for it, the one that he told me to look in, but, I found it to be a poor guide for how to do any setup, especially when a wiki site about the controller and all of it's settings and whatnot would be a MUCH better. Not only would it allow for greatly expanded detail on everything, it would easily allow for cross-linking between sections that refer to each other, as happens several times through the manual.

Naze32 might be a very good flight controller, but, I won't be buying another. Perhaps it's just me and my opinions, but, if the dev team is going to respond to a noob as they/he did to me, then they clearly don't want to expand the hobby and are content to drive people away.

[timecop]

get off your newb horse, bro.
there's a section in the manual that exactly covers this.
I'm sorry but if you needed more info than that, you should probably drive to your nearest dji dealer asap.

[MinisterPhobia]

get off your newb horse, bro.
there's a section in the manual that exactly covers this.
I'm sorry but if you needed more info than that, you should probably drive to your nearest dji dealer asap.

I was going to respond, but, you're simply proving my point.