Hi,

after connect, the navigation tabs in cleanflight configurator disappear. They still work, clicking on the empty area changes the tabs, but they are hidden.

I'm using Chrome 41 beta on Windows 8.1.

Screenshot before connect:

Screenshot after connect:

Thanks,

Ulf

I have several neo6m gps modules that work really well with normal multiwii at 5hz 115200baud.
Cleanflight will sometimes change the module refresh rate to 10hz which is giving it greatly reduced position hold performance.

Is there anyway to stop cleanflight from configuring the GPS module automatically. It should be written in the GPS docs if so.

You obviously have no clue how to operate the configurator from developer side since you failed numerous times to deal with something so simple as version expiration dates which i implemented to help inform people with broken googleupdate, this check was implemented to help/inform people about potential problems, its not there to create confusion by your misuse.

Not counting the failure you made with keeping my analytics ID in your fork, at least god damn look what the hell are you pulling as i don't have all day to deal with issues that are created by your laziness and incompetence.

https://github.com/cleanflight/cleanflight-configurator/blob/master/js/review.js#L106
https://github.com/cleanflight/cleanflight-configurator/blob/master/js/review.js#L117

Learn to read damn licencing that is included in svg artwork files that you blindly pull with no regard to original author/s

https://raw.githubusercontent.com/cleanflight/cleanflight-configurator/master/resources/motor_order/quad_x.svg
https://raw.githubusercontent.com/cleanflight/cleanflight-configurator/master/resources/motor_order/quad_x.svg

Same goes for exported blender models that are used with the threejs

https://github.com/cleanflight/cleanflight-configurator/blob/master/resources/models/quad_x.json#L5
https://github.com/cleanflight/cleanflight-configurator/blob/master/resources/models/tricopter.json#L5

Happy holidays.

I appear to have got cleanflight configurator into a mode where ANGLE wants to show as active even when the current channel receiver state is outside the activation range.

NOTE that it only does it when no receiver signal is being received - regardless of value displayed on screen.

See screenshot - AUX1 is setup for arm, angle and horizon modes all in same range. Aux1 showing 1500 on screen and ARM and Horizon correctly disabled. Angle however is showing green.

Removing it, adding it back in, saving and rebooting doesn't fix the problem.
Not sure if its a UI issue or actually the mode is really enabled.

20:52:06 -- Running - OS: Windows, Chrome: 40.0.2214.91, Configurator: 0.60.0
20:52:09 -- Serial port successfully opened with ID: 1
20:52:09 -- MultiWii API version received - 1.3
20:52:09 -- Flight controller info, identifier: CLFL, version: 1.6.0

Config Dump:

dump

version

Cleanflight/NAZE Jan 16 2015 / 12:40:10 (d72983e)

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 VBAT
feature RX_SERIAL
feature FAILSAFE
feature SONAR

map

map TAER1234

led

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

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 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 = 1
set serial_port_2_scenario = 3
set serial_port_3_scenario = 0
set serial_port_4_scenario = 0
set reboot_character = 82
set msp_baudrate = 115200
set cli_baudrate = 115200
set gps_baudrate = 115200
set gps_passthrough_baudrate = 115200
set gps_provider = 0
set gps_sbas_mode = 0
set gps_auto_config = 1
set gps_auto_baud = 0
set serialrx_provider = 2
set spektrum_sat_bind = 0
set telemetry_provider = 0
set telemetry_switch = 0
set telemetry_inversion = 0
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 = 112
set vbat_max_cell_voltage = 43
set vbat_min_cell_voltage = 33
set vbat_warning_cell_voltage = 36
set current_meter_scale = 400
set current_meter_offset = 0
set multiwii_current_meter_output = 0
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 0 1700 2100
aux 1 1 0 1700 2100
aux 2 2 0 1700 2100
aux 3 12 2 1700 2100
aux 4 21 1 1700 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
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

If you close the configurator with the CLI tab open there is no "Exit" command send to the CLI.
If you open the cleanflight-configurator again without unplugging the usb it is impossible to reconnect because the board is still in CLI mode and so doesn't answer to MSP commands.

auto disarm delay
disarm kill switch

Every time there is a forced Cleanflight Configurator update which breaks compatibility with the old firmware, a good percentage of users can't recover their old board settings to migrate them to the new firmware. In this situation it would be nice if at least the CLI tab still worked in the Configurator, so users could be directed to "dump" on their old firmware using that, flash the new firmware, then reload their configuration and double check if anything didn't port across.

If old (or even current) versions of the Configurator were published separately from the main "latest" version of the Configurator in the store, people could install these fixed-versions with one click and they'd never have to complain about it being updated from underneath them.

I can't for the life of me get the Cleanflight configurator to install in my apps on Win 7. I may have messed something up because I had it installed and now it clearly is not and I keep getting a network error. If someone has a solution please be as specific as possible. In the alternatibe way, what does "clone the repo" mean?
Thanks

Not hugely important, but for channels 9-12 , no graph data appears to be displayed when receiver channel gets updated. The bar graph (Green bars) displays the inputs, but its not logged on the scrolling graph.

Hi, I'm new user of the CleanFlight Configurator. Would it be possible to select the frame type/mixer via the GUI (possibly Initial Setup tab) rather than delving into the CLI. I think this would help ease more new users into using CleanFlight. Thanks

Hello Dominic,
Firstly many thanks for all the development time you and the other contributors have given to Cleanflight codebase and Configurator.

I have a minor issue where I cannot get the Arm to turn green on the Aux Config Tab. It used to work in an older version of Configurator (I think it was 50.1)

Here are my stats:
Cleanflight Configurator: 0.51.4
Naze32 Rev. 5 FC
Firmware # version: Cleanflight / NAZE Nov 8 2014 19 (28da97f)/ 12:32:
Running - OS: Windows XP Home 32 bit, Chrome: 38.0.2125.111
Blackout Mini H Quad – Tiger MN2206 motors – Tiger 12 Amp ESC’s – Turnigy 3 Amp UBEC – Minim OSD – UBLOX Neo 6M GPS - Fatshark 5.8 GHz 250mW VTx - Mini DC-DC Converter 3 Amp – 16 x 2812B Addressable LED Strip – Crius Bluetooth Module – FrSKY D8-XP Receiver – Taranis X9D Transmitter.
Regards,
Mike (max3228)

Screen grab above showing ARM not turning GREEN when armed on my Taranis X9D Tx.

dump

version

Cleanflight/NAZE Nov 8 2014 / 12:32:19 (28da97f)

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 RX_PPM
feature VBAT
feature MOTOR_STOP
feature GPS
feature FAILSAFE
feature TELEMETRY
feature LED_STRIP

map

map AETR1234

led

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

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 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 small_angle = 25
set flaps_speed = 0
set fixedwing_althold_dir = 1
set serial_port_1_scenario = 1
set serial_port_2_scenario = 2
set serial_port_3_scenario = 0
set serial_port_4_scenario = 0
set reboot_character = 82
set msp_baudrate = 115200
set cli_baudrate = 115200
set gps_baudrate = 115200
set gps_passthrough_baudrate = 115200
set gps_provider = 1
set gps_sbas_mode = 0
set gps_auto_config = 0
set serialrx_provider = 0
set telemetry_provider = 0
set telemetry_switch = 0
set frsky_inversion = 0
set frsky_default_lattitude = 0.000
set frsky_default_longitude = 0.000
set frsky_coordinates_format = 0
set frsky_unit = 0
set frsky_battery_size = 0
set vbat_scale = 111
set vbat_max_cell_voltage = 43
set vbat_min_cell_voltage = 34
set current_meter_scale = 400
set current_meter_offset = 0
set multiwii_current_meter_output = 0
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

dump profile

profile

profile 0

aux

aux 0 0 0 1600 2100
aux 1 2 1 1400 2100
aux 2 3 1 1400 2100
aux 3 4 1 1400 2100
aux 4 5 3 1800 2100
aux 5 9 1 1800 2100
aux 6 10 1 1400 1600
aux 7 20 2 1800 2100
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 = 11
set gps_pos_i = 0
set gps_pos_d = 0
set gps_posr_p = 20
set gps_posr_i = 8
set gps_posr_d = 45
set gps_nav_p = 14
set gps_nav_i = 20
set gps_nav_d = 80
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 = -220
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 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

feature

Enabled features: RX_PPM VBAT MOTOR_STOP GPS FAILSAFE TELEMETRY LED_STRIP

Would it be possible to assign a PID controller (since we have a few choices now) to a specific pid bank so that when we switch PID banks we would also switch the controller with it, allowing us to compare controllers in the field?

When target stops responding to MSP requests (in debugger in my case), it seems that callback handlers are still created in configurator. It takes quite long to recover when connection is restored, during this time the app is frozen.

Old (just before graphics update) version did handle this gracefully

Is there a way to separate the pitch and roll in flight pid adjustments so they can be tuned separately tuning both at the same time will not worl for most setups

Hi,
I am using WS2812B which were purchased here:
http://www.ebay.co.uk/itm/1m-WS2812B-RGB-LED-Pixel-Strip-60-Individually-Addressable-Pixels-60-m-/151478784787?

I have made a test strip and connected as specified in the Wiki. However the LED are behaving randomly, incorrect colours and incorrect LED lit. You mentioned recompiling the source with a different frequency but ive not managed to successfully re compile the source, would it be possible to add the frequency to the CLI tools please.

Has any one successfully got the WS2812B's to work.
Also can anyone explain how the ID of each led is set, I know its different but before ive used an I2C bus but each device had to have its ID set. How can i know that my first LED in the strip is the first ID???

Many Thanks,
Tony Brock

This is something i seem to use quite a bit.. lately.. the motors config Tab its great... but would be even better, super, fab, fantastic better.... :-) if there was an option maybe to set some. fixed motor speeds for balancing...

so it would work like this.... set a speed 1300 maybe. then have the ability to quickly switch from motor 1 to 4 with the same speed setting....the ability to log the acc data too while doing these quick tests would show which motor or prop needs the most balancing..

I just find it a very manual way to do it at the moment... obviously it would need some very strict warnings when props were attached...!!!!!!

OOOOOOooooohhhhh OOOOOoooouch....

or some other automated method.of getting a consistent result...

I realise that the method of balancing the props is not going to change but at least we can all see the results far easier..

Thanks Hydra and all the rest of the team for all the hard work you putting in.. I love Cleanflight and still continue to spread the word... great work fellas...

Latest 1.3.0 is displayed as "v1.3.0 NAZE 2014-11-0 17:27"
1.2.0 was/is displayed as "v1.2.0 NAZE 2014-11-1 0:59"

I assume its due to different locales (german here) in OS (Windows)

The models should rotate around the center of the model as outlined by the motors. Currently the center point is slightly off-center.

On the version 0.60.0, before I connect the tab controls (Setup, Ports, Configuration) are visible, when I click Connect, the tab controls then disappear:

I can click on them by guessing the position of the tabs.
Display adaptor is Intel HD Graphics 3000

Hello,

It seems cleanflight auto updated to ver 0.58.0 and now I cannot connect to my naze32 FC for further tuning. It just sits on the 'waiting for data' animation and doesn't go any further.

Any clues as to whats up? I'm running on OS X 10.8.5, and all was working fine until this update from the 3rd Jan.

Thanks, I hope you can help.

Just a todolist

• add new tab Controls
• move the Servos display from the Motors tab to the Servos tab
• build a dropdown for spektrum_bind_blug

For new users, the checkbox format was sufficient and for most users, sufficient as well.

New range format adds complexity and would slow adoption of cleanflight by users.

Currently, if the API version is not current, the configurator can't connect to the board at all. If the user wants to retrieve some settings, they have to use a third party terminal program.

It would be great if the CLI tab could be activated even if the API version is not current, which would allow users to retrieve a dump of their current settings.

Battery voltage scale should change to take into account the modification linked to this pull request : cleanflight/cleanflight#108

11:40:34 -- You're using an old version of Cleanflight - Configurator. Please update so you can benefit from recently added features and bugfixes.

I am running Cleanflight - Configurator 0.51.1

In Development version 0.61.0, the alignment of the text in the PID Controller dropdown is too far to the right obscuring the value of the box when the dropdown box isn't open:

and

Thanks

Adding indicators for system status would be useful.

three important states are: calibrating, armed and failsafe.

From one of our forum members:

"cleanflight cant save modes to my full naze32. Save to the eprom in cleanflight then when I disconnect and reconect one of the flight modes are saved."

I've seen similar reported elsewhere also, but not on here. So here's a potential bug report.

Has something changed or is this a bug?

There should be a option to set tpa_breakpoint under the TPA value in the PID Tuning tab.

InitialSetup - Info - Current draw: is always displayed as positive value, event when actual value is negative. This is very confusing when adjusting current_meter_offset in cli ..

An issue that is quite frustrating to me (and others) is the way that occasionally, when a new version of the configurator is released, it breaks all communication with boards that are running the previous version of Cleanflight.

This has happened a number of times in the past, and most recently with the version that was released around the 5th January 2015.

The effect this has is that the configurator will silently update itself, so when the user goes to adjust some PID values, or change the way that aux channels are configured, the configurator can't connect to the board. This happens without the users knowledge in most cases, so it's a complete surprise when the user is locked out of being able to fly their craft.

What would be great is if some consideration is made towards backwards compatibility when changes are made. This would mean that users would be given some warning before being locked out of being able to use this software.

Hi, I'd like to start using clean flight over the other configurator as it has some features I like and it seems to be going in a more useful direction.
I've only had a brief look, as the sun is out, and there's no wind!!
I can't get a signal from my receiver, I have enabled RX_PPM... but not much else.
The Tx is a turnigy 9xr with orange module and 615x Rx.
I'm not very computer literate so please forgive me if this is an obvious setting I've missed.
I haven't set a new model on the radio just used the one I had for the other configurator, which when reflashed and the settings dumped back on works flawlessly, so TX and RX are talking. Please advise.

Have been testing Bluetooth connections with cleanflight.
115K baudrate via wired connection works, 115k doesn't seem to work via BT (whereas other FC's do work on same settings).

Changing BT module (BT4 BLE) to 57K and setting msp_baudrate to 57K works to get connection.
Interface very slow and CLI unusable. Setting cli_baudrate to 57K as well doesn't help.

I've recorded my findings here: http://1drv.ms/ZUqNT5

I've just found out that my old Naze32 full board will not work with firmware any older that #149 (opening an issue for that) October 6th. Now I can't use the latest configurator to do Aux channel setup.
Can we please have backward compatibility.

Colin.

The GPS signal strength data is not cleared upon disconnect, reboot board (with GPS disconnected), and reconnect. Need to close the configurator and relaunch to clear it. I suspect this is happening as the MSP response to the sv info command only returns data for active satellites and the CLI musn't write anything beyond that to its internal array. That means if a satellite is lost it's old value will be retained which could be misleading. Unfortunately my Javascript skills are non-existent.

Since the new Configurator I cannot connect to my flip32+ board. The setup screen is showing "Waiting for data" and the packet errors are counting.

I tried different computers and tried usb and bluetooth connection, nothing works.

I used the latest cleanflight configurator, and saved the setting for Auxiliary configuration. I discovered after disconnection / reconnection that in fact nothing was saved.

It's not mandatory to be connected to COM port to flash via USB, but correct COM port must be selected in top left field otherwise flash is not starting (sorry I don't note the error message).
Release 0.59.0
/Phil

Looks to be the code already contain parts to enable DFU flashing? Not sure what the actual state is and if this part of the code is already working. Actually the GUI is only allowing Hex files to be selected and will do some basic tests. Also an STM device in boot mode is not detected by the GUI. Would be nice to be able to flash all targets easily via the GUI.

I have opened an related issue in CF already:
cleanflight/cleanflight#412

The newest binary firmware image is available here

here/link points to: https://github.com/cleanflight/cleanflight/tree/master/obj
Should be changed to: https://github.com/cleanflight/cleanflight/releases instead

When you go to flash firmware, the board type automatically selects CC3D. A better option would be to default to something along the lines of "Please select board type".

Just something to help make the GUI idiot proof. (i know plenty have already tried to flash their naze boards with CC3D firmware).

The profile selection combobox is in the PID tuning folder though it is related to most features (Receiver, Modes...)

this combobox should be either availabel in all related folder OR in a unique place outside the folders

After restoring parameter, battery informations for Min cell voltage and Max cell voltage are not set correctly.
Same thing for Auxiliary configuration, Aux5->Aux8 are set with random values, instead of empty values in my case (There was empty values when I saved my configuration).

When pasting a complete dump into the CLI, data is lost because the Naze can't keep up with the writes (I tend to lose the AUX configuration from my dumps). Adding a delay between each line sent on the serial bus should cure this and make restoring dumps easier for everybody.

Hi,

Got a problem with configuration tab when connected.
it keeps telling me waiting for data with packet error counter increasing,

Just flashed twice but nothing different happens,

Can I get help, please? accro naze 32 here

I noticed that the CleanFlight configurator is using the Baseflight icon, although in another color. Reusing the BaseFlight logo with such minor changes is problematic in several ways. The biggest problem is that people may not notice the difference at all and confuse BaseFlight and CleanFlight.

I also noticed that there seems to exist no common logo nor graphical profile for CleanFlight neither on the home page, on github or in the configurator itself. Logos and graphical profiles might seem like trivial details, but are important for the recognition and perseption of a open source "brand". High quality software is always branded by some sort of visual implements.

I played with the letters C and F in CleanFlight and made a few scetches of what could be used as both logos and icons. I am not a graphical artist and know that others are far better at this than I am My attempts may perhaps serve as an inspiration for someone else.

Not sure how feasible this is. I am new to this flight controller and Hydra said to share my experience.

One item that I think would be handy would be the ability after selecting the controller and flash type, would be either another tab or something where you could essentially mock up your connections and layout.

For example if I am using a Naze 32 , with HEXA motor layout, sonar, and a PPM input encoder, a receiver.

That I could see a reference diagram of the pinnouts.

That way there would be a logical reference with the pins in use being numbered or "lit" in the diagram and to help make sure that each motor is connected to the right set of pins.

Maybe even add a link to a manual on the manufactures site for the common items.

Low priority. Just a thought. Couldn't hurt to ask.

-WhirlyGig

Previous to the "Board Alignment" feature implementation in CFC, users would adjust board alignment via cli, with many used to 0-360 notation.

Example:
set align_board_yaw = 270

The "Board Alignment" feature in CFC enforces "-180" to "+180" range limits, causing confustion for new users who attempt to enter "270" when they should use "-90".

Please replace the "[deg]" description in the Board Alignment feature variables with the allowable ranges of -180 deg to +180 deg, or lift the restriction and allow 0-360 notation.

-=dave