flashed from Cleanflight to Betaflight 2.5.3- motors wont arm, cant test them

[djmk4]

Hi all,

Having a play around with Betaflight today getting some config back on, I cant get the thing to arm, the motor tests are not working either with the battery and USB plugged in.

Anyone free to take a second glance over the config if I do a dump to see why its not arming? I have been through the config and cant see what the issue is at the moment, spent a good few hours looking over this, this is my problem at the moment I dont really have the time to find little issues like this after 3-4 hours of exhausting options. Just need it to fly well and I can do some tweaking :)

Any help appreciated

My TX is communicating with the RX and the Naze32, as when I unplug battery I get telemetry lost, plug back in telemetry recovered, the throttle, yaw, pitch roll movements are recognized through cleanflight.

The LEDs on the board with nothing being touched and USB in is BLUE and RED.

The LEDs on the board with the battery only plugged in and ready to fly is BLUE and RED, when I go to arm it with the TX by doing left stick bottom right hand corner to arm the green led comes on which usually means good to go, but nothing is happening


I have attached the CLI dump

I am using Taranis Plus TX, D4r-ii reciever and naze32 board

Still trying to figure it out, a nice sunny afternoon wasted trying to get it to arm




config


==================================


# dump

# version
# BetaFlight/NAZE 2.5.3 Mar  6 2016 / 14:16:58 (0aac025)
# dump master

# mixer
mixer QUADX
mmix reset
smix reset


# 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 -CHANNEL_FORWARDING
feature RX_PPM
feature VBAT
feature MOTOR_STOP
feature FAILSAFE
feature TELEMETRY
feature ONESHOT125


# 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


# map
map AETR1234


# serial
serial 0 1 115200 57600 0 115200
serial 1 0 115200 57600 0 115200


# led
led 0 15,15:ES:IA:0
led 1 15,8:E:WF:0
led 2 15,7:E:WF:0
led 3 15,0:NE:IA:0
led 4 8,0:N:F:0
led 5 7,0:N:F:0
led 6 0,0:NW:IA:0
led 7 0,7:W:WF:0
led 8 0,8:W:WF:0
led 9 0,15:SW:IA:0
led 10 7,15:S:WF:0
led 11 8,15:S:WF:0
led 12 7,7:U:WF:0
led 13 8,7:U:WF:0
led 14 7,8:D:WF:0
led 15 8,8:D:WF:0
led 16 8,9::R:3
led 17 9,10::R:3
led 18 10,11::R:3
led 19 10,12::R:3
led 20 9,13::R:3
led 21 8,14::R:3
led 22 7,14::R:3
led 23 6,13::R:3
led 24 5,12::R:3
led 25 5,11::R:3
led 26 6,10::R:3
led 27 7,9::R:3
led 28 0,0:::0
led 29 0,0:::0
led 30 0,0:::0
led 31 0,0:::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

# aux
aux 0 1 0 900 1200
aux 1 2 0 1300 1700
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

# 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

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

set mid_rc = 1500
set min_check = 1040
set max_check = 1900
set rssi_channel = 0
set rssi_scale = 30
set rssi_ppm_invert = OFF
set input_filtering_mode = OFF
set rc_smoothing = OFF
set roll_yaw_cam_mix_degrees = 0
set max_aux_channels = 6
set debug_mode = NONE
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 use_oneshot42 = OFF
set use_multishot = OFF
set motor_pwm_rate = 400
set servo_pwm_rate = 50
set disarm_kill_switch = OFF
set auto_disarm_delay = 5
set small_angle = 25
set fixedwing_althold_dir = 1
set reboot_character = 82
set serialrx_provider = SBUS
set sbus_inversion = ON
set spektrum_sat_bind = 0
set spektrum_sat_bind_autoreset = 1
set telemetry_switch = OFF
set telemetry_inversion = OFF
set frsky_default_lattitude =  0.000
set frsky_default_longitude =  0.000
set frsky_coordinates_format = 0
set frsky_unit = IMPERIAL
set frsky_vfas_precision = 0
set frsky_vfas_cell_voltage = OFF
set hott_alarm_sound_interval = 5
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 vbat_pid_compensation = OFF
set current_meter_scale = 400
set current_meter_offset = 0
set multiwii_current_meter_output = OFF
set current_meter_type = ADC
set align_gyro = DEFAULT
set align_acc = DEFAULT
set align_mag = DEFAULT
set align_board_roll = 0
set align_board_pitch = 0
set align_board_yaw = 0
set max_angle_inclination = 700
set gyro_lpf = OFF
set gyro_sync_denom = 8
set gyro_soft_lpf =  60.000
set moron_threshold = 32
set imu_dcm_kp = 2500
set imu_dcm_ki = 0
set alt_hold_deadband = 40
set alt_hold_fast_change = ON
set deadband = 0
set yaw_deadband = 0
set throttle_correction_value = 0
set throttle_correction_angle = 800
set yaw_control_direction = 1
set yaw_motor_direction = 1
set yaw_jump_prevention_limit = 200
set tri_unarmed_servo = ON
set servo_lowpass_freq = 400
set servo_lowpass_enable = OFF
set acro_plus_factor = 30
set acro_plus_offset = 40
set failsafe_delay = 10
set failsafe_off_delay = 10
set failsafe_throttle = 1000
set failsafe_kill_switch = OFF
set failsafe_throttle_low_delay = 100
set failsafe_procedure = OFF
set rx_min_usec = 885
set rx_max_usec = 2115
set gimbal_mode = NORMAL
set acc_hardware = AUTO
set acc_lpf_hz =  10.000
set accxy_deadband = 40
set accz_deadband = 40
set acc_unarmedcal = ON
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 baro_hardware = AUTO
set mag_hardware = AUTO
set mag_declination = 0
set pid_process_denom = 1
set blackbox_rate_num = 0
set blackbox_rate_denom = 0
set blackbox_device = SERIAL
set magzero_x = 0
set magzero_y = 0
set magzero_z = 0

# 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

# dump profile

# profile
profile 0

set yaw_p_limit = 300
set pid_delta_method = MEASUREMENT
set dterm_lpf_hz =  0.000
set dterm_average_count = 4
set pid_controller = MWREWRITE
set p_pitch = 54
set i_pitch = 40
set d_pitch = 22
set p_roll = 42
set i_roll = 40
set d_roll = 18
set p_yaw = 90
set i_yaw = 50
set d_yaw = 0
set p_pitchf =  1.400
set i_pitchf =  0.400
set d_pitchf =  0.010
set p_rollf =  1.100
set i_rollf =  0.400
set d_rollf =  0.010
set p_yawf =  4.000
set i_yawf =  0.400
set d_yawf =  0.000
set level_horizon =  4.000
set level_angle =  4.000
set sensitivity_horizon = 75
set p_alt = 50
set i_alt = 0
set d_alt = 0
set p_level = 30
set i_level = 30
set d_level = 100
set p_vel = 120
set i_vel = 45
set d_vel = 1

# rateprofile
rateprofile 0

set rc_rate = 100
set rc_expo = 70
set rc_yaw_expo = 20
set thr_mid = 50
set thr_expo = 0
set roll_rate = 0
set pitch_rate = 0
set yaw_rate = 0
set tpa_rate = 0
set tpa_breakpoint = 1500

# dump rates

# rateprofile
rateprofile 0

set rc_rate = 100
set rc_expo = 70
set rc_yaw_expo = 20
set thr_mid = 50
set thr_expo = 0
set roll_rate = 0
set pitch_rate = 0
set yaw_rate = 0
set tpa_rate = 0
set tpa_breakpoint = 1500

[DarkButterfly]

I had a similar issue with my mini hex after loading betaflight, my problem was the mixer setting as I was using a custom mix, but I can see yours isn';t custom, so that may not be the cause of it.

How are you arming, by stick or switch?

[djmk4]

I used to be able to arm in clean flight by left stick.

Put it in the bottom right position and would arm ready for throttle.

I tried putting clean flight back on works fine, put betaflight on and nothing, can';t even test the motors in the motor section.

Unfortunately these days I need something that';s quick to get up and running, I';m hoping if I can find this issue then the rest will be OK with maybe some minor tweaks

[Powernumpty]

Have you gone through the esc calibration again?

Just out of interest what connection method, PPM, SBUS etc?

[atomiclama]

I hope your ESCs are one shot capable as betaflight is oneshot enabled by default

Code Select Expand

feature ONESHOT125

try disabling it

Code Select Expand

feature -ONESHOT125

That';s all I can see if you say you can';t even use the motors tab to control the motors.

What ESC and version of FW are you using?

[djmk4]

I did try disabling oneshot but didn';t make a difference

The escs are emax simonk firmware

Esc calibration I thought you do this in the motors tab,  unless there is a new procedure. Will have a look,

Is there something about the tx range that';s stopping it arming I';m hearing mixed talk on?

[Mickkn]

What is your min. throttle? If it';s above 1040 it won';t arm. Change min_check or scale down the min throttle on your radio

[Andy7]

What is your min. throttle? If it';s above 1040 it won';t arm. Change min_check or scale down the min throttle on your radio

Yep, there it is...

Code Select Expand

set min_throttle = 1150

That would have been my guess too.

[Powernumpty]

Esc calibration I thought you do this in the motors tab,  unless there is a new procedure. Will have a look,

Probably I';m barking up the wrong tree, I have a Naze that won';t arm since the latest cleanflight and while checking things out I noticed the ESC';s would run up at different points so had to recalibrate but as you say the motor control won';t work it can';t not that.

Other things I read can stop it arming are Baro when there is none or Throttle not in correct range for arm as mentioned, I think there needs to a good 100 clearance between the min/max and your transmitter endpoints.

[bazzerh]

lower min_command in increments of 10 until it will arm. think ive had to go to 980 on some of my quads before. do this after doing the normal calibrations.

[atomiclama]

lower min_command in increments of 10 until it will arm. think ive had to go to 980 on some of my quads before. do this after doing the normal calibrations.

What baz said and not min_throttle as mentioned before, that is the value sent to the esc once armed.

min_command is the value sent when disarmed. But this is the same in cleanflight I think so is probably not the issue.

Is there something about the tx range that';s stopping it arming I';m hearing mixed talk on?

Get the motors running in the motors tab before you start thinking about this.

BTW Why do you want betaflight? Moost of the good stuff is now in cleanflight now.

Running betaflight you really need to know what you are doing. Also I would stick to a major version V2.5 and not one of the minor releases that may have introduced a bug. V2.5 has been tested quite a bit through a few RC.

[bazzerh]

There were known issues with chirping and arming when the looptimes got lower and lower, some users had to lower min_command to solve it. Obviously a hardware dependant issue.

[atomiclama]

He';s not running silly LTs

Code Select Expand

set gyro_sync_denom = 8

Should be fine with 1kHz

[nub]

the twitching issues have been sorted.

[atomiclama]

the twitching issues have been sorted.

Glad to hear it 

[nub]

and the itching ones too!

[djmk4]

Will test the above when I get a chance on the above pointers and let you know results, thanks all :)

[djmk4]

What baz said and not min_throttle as mentioned before, that is the value sent to the esc once armed.

min_command is the value sent when disarmed. But this is the same in cleanflight I think so is probably not the issue.

Get the motors running in the motors tab before you start thinking about this.

BTW Why do you want betaflight? Moost of the good stuff is now in cleanflight now.

Running betaflight you really need to know what you are doing. Also I would stick to a major version V2.5 and not one of the minor releases that may have introduced a bug. V2.5 has been tested quite a bit through a few RC.

I was told that betaflight had a good default setup for flying ? With rate mode on clean flight i couldnt quite get the tuning right and it flew OK but didn';t feel quite there (I don';t have hours to spend on tuning and testing) so though betaflight was recommended for a good default setup and you may have to tweak a tiny bit?

Saying that, there was a period where I didn';t fly between Oct -  current time so not sure if there has been major improvements on some of the default setup after you flash.

[Gandhi]

Sorry dude, this is my fault for recommending it to you!

Really, betaflight works very well but does need some set-up and sometimes things change and aren';t documented very well. As was mentioned above, a lot of the improvements from betaflight have trickled down to cleanflight since october, so it might be worth flashing back to that if you haven';t got the time to dick about with Betaflight.

I';m at a bit of a loss as to why it won';t arm with betaflight. I';d normally say look at mincheck and the receiver inputs but that shouldn';t effect the motor testing tab. You should always be able to get the motors going here.

I know you had issues with flashing so I wonder if there is actually some weird problem with the board itself?

The only other thing that might stop the board arming or working in the motor test is if the accelerometer or gyros won';t settle or are given time to be level.

Is it a genuine naxe32 rev5?

[agrs1974]

Done the exact same with my 250 and it';s the same with a few others.

I';d recommend going back a few versions. It';s the software that';s the problem.  I tried everything to no avail. 

[atomiclama]

I was told that betaflight had a good default setup for flying ? With rate mode on clean flight i couldnt quite get the tuning right and it flew OK but didn';t feel quite there (I don';t have hours to spend on tuning and testing) so though betaflight was recommended for a good default setup and you may have to tweak a tiny bit?

It has worked well for me. I have only just started to tweak the settings a bit, but it has been very stable in flight.

But I';m on V2.5 and don';t plan on moving for a while.

[Gandhi]

I';m on 2.5.3 and it';s worked flawlessly for me. That';s on 2x v5 naze and 2x v6.a, all with KISS Esc';s.

I';m wondering if that is part of the problem here. The SimonK emax esc';s are ok, but not sure if they';re oneshot capable or able to keep up with Betaflight?

[agrs1974]

I think the problem could be the firwmare version and the older naze boards are not recognising the it. Maybe Im wrong.

[Gandhi]

Could well be. I know the OP had some issues flashing the bf firmware.

[atomiclama]

I';m wondering if that is part of the problem here. The SimonK emax esc';s are ok, but not sure if they';re oneshot capable or able to keep up with Betaflight?

Just thinking out loud here.

He has already tried disabling oneshot. didn';t make a difference.

when you switch off oneshot the update rate of the pwm is fixed by a config value. so it don';t matter what looptime you run at, the ESC does not get updated at LT rate. so that should not be a problem with the ESC keeping up.

I have some of those ESC  I';ll try and find some time to try them out. Will be with a CC3D board though.

[Cheredanine]

*sigh*
Ok first point, it is generally recommended that switch arm is used, not stick arm, for betaflight, this is because air mode you frequently use zero throttle, hence it is possible you disarm in the air, there really is no reason to use stick arming, it is a hangover from older days and different types of flying machines.

Quad won';t arm -
1. The quad has to be flat and level to arm, if you exceed the small angle setting cf/bf wont arm
2. To stick arm the throttle signal has to be below min check. Boris has lowered this from the old default (see comment about stick arming above) to 1040, on the Rx tab check what throttle does when you try and stick arm, if it reaches 1040 then it won';t arm, you have two choices - set up your channel on your radio correctly or increase min check

Your min throttle is too high, it should be set to 10 points higher than that value where all 4 motors are spinning

What radio are you using? Don';t think you said but if you are using a taranis or many of the other common radios your channel map is wrong, this would stop it arming

[atomiclama]

All true but I don';t think any of that will effect the ability to run the motors in the motor tab which he can';t do.

the motor tests are not working either with the battery and USB plugged in.

[Cheredanine]

All true but I don';t think any of that will effect the ability to run the motors in the motor tab which he can';t do.

Seen that fixed by recalibration of ESCs, but otherwise likely to be a physical problem, the config, whilst not ideal, shouldn';t stop that

[djmk4]

Sorry dude, this is my fault for recommending it to you!

Really, betaflight works very well but does need some set-up and sometimes things change and aren';t documented very well. As was mentioned above, a lot of the improvements from betaflight have trickled down to cleanflight since october, so it might be worth flashing back to that if you haven';t got the time to dick about with Betaflight.

I';m at a bit of a loss as to why it won';t arm with betaflight. I';d normally say look at mincheck and the receiver inputs but that shouldn';t effect the motor testing tab. You should always be able to get the motors going here.

I know you had issues with flashing so I wonder if there is actually some weird problem with the board itself?

The only other thing that might stop the board arming or working in the motor test is if the accelerometer or gyros won';t settle or are given time to be level.

Is it a genuine naxe32 rev5?

Haha alright :)

Betaflight was timing out when getting to the validating during flash, but on a few further attempts it completed fine with no issues.

I will try raising the min throttle to get it to arm, but if there have been some changes in to cleanflight since oct I may try this also.

If I can stick to the most stable thats not going to have too many changes to it which required loads of reading and unknowns then that may be better for me

However saying that I will try both and see how I get on.


Work has been super busy as usual but im hoping to maybe have another attempt at getting the FC to arm the motors on the weekend, will let yo know how I get on, will give Betaflight another go first

I want to see how it performs out of the box with the default and basic set-up, and compare it to clean-flights latest.

I dont mind doing some PID tuning but im not a massive expert, Ghandi helped me out loads last year so thanks to him :)