Now that Cleanflight 2.0 is here, you'll find that the Cleanflight Configurator for 2.0 won't talk to version 1.x Cleanflight any more. If you don't want to update (and why should you if your quad flies well as it is?), Painless360 recently put up a useful video which explains how to install the old version of the Cleanflight Configurator alongside the new one.

One thing he didn't point out was that you can easily change the name of the old version of Cleanflight Configurator to make it much easier to tell the two apart. 

If you look in the folder where you unzipped the old version of the configurator before installing it, you should see a file named 'manifest.json'. The first few lines of this text file look like this:


{
    "manifest_version": 2,
    "minimum_chrome_version": "38",
    "version": "1.2.4",
    "author": "Hydra",
    "name": "Cleanflight - Configurator",
    "short_name": "cleanflight",


Just change the two bold words to something more appropriate and save the changes to the file before you add the unpacked extension to Chrome. For example:

    "name": "OLD Configurator 1.2.4",
    "short_name": "OLD Cleanflight",

and you'll see a much less confusing set of icons on your Chrome apps screen:



"short_name" is what is shown underneath the icon and "name" is shown when you hover the cursor over the icon and in the list of installed extensions in the chrome://extensions/ screen.

Thanks for the guide very helpful
Any reason why we still want to use old version cleanflight but not the newer version or even Betaflight?

I was under the impression the newest configurator only works with the latest version of the Firmware - so if you had a fully functioning fully awesomely set up F1 based old F/C you'd be forced update etc etc

(21-Apr-2017, 09:37 AM)Oscar Wrote: Thanks for the guide very helpful
Any reason why we still want to use old version cleanflight but not the newer version or even Betaflight?

If something isn't broken, why fix it?

As Aaron points out, if you have an older F1 based flight controller, upgrading to the latest release might not even be an option.

I agree with Aaron and unseen.  Just ran into this myself...I upgraded to Cleanfight 2.0 and then went to make some adjustments on a Naze 32 rev 6a and was forced to load new firm wear onto the board.  Of course, many of the old settings no longer worked under the new firmware...what a pain.  I have no problem upgrading if there is a reason to do so.....but not just because there is new better stuff out there......

(21-Apr-2017, 09:37 AM)Oscar Wrote: Thanks for the guide very helpful
Any reason why we still want to use old version cleanflight but not the newer version or even Betaflight?

From what i read, there's a lot of things that don't work properly, or at all anymore in newest versions.

Aside from certain features and hardware-support being dropped, for example many mixer configuration presets seem to be not working. Betaflight is/was so focused on normal x-type quads only, that anything out of the norm (tricopter, +hex or fixed wing for example) is likely to be broken, or at least not working without some serious configuration magic (remapping resources and/or manual mixer editing etc). And since cleanflight re-based off betaflight 3-dot-something it's pretty much the same right now.

https://github.com/cleanflight/cleanflight/issues/2764

https://github.com/betaflight/betaflight/issues/3011

https://github.com/betaflight/betaflight/issues/3036

PS: btw you can also just directly rename the apps in the chrome apps screen, or even create a shortcut to them on your desktop. Though i admit unseen's way is a lot more elegant.