baseflight configurator (win/linux/mac)

[cTn]

Hi guys, @fiendie recently hooked me up with stm32mini dev board, purely for development purposes, so i decided to pitch in "a little" to the community even thought i am not really using multiwii for flying.
There wasn't a multi-platform GUI for baseflight so i decided to make you guys something that's "up to the challenge" and hopefully easy enough to work with for the end user.

Installation
https://chrome.google.com/webstore/deta ... innofofigk

Source
https://github.com/multiwii/baseflight-configurator

If you like my work, buy me a new set of eye drops


Enjoy

Changelog

Code: Select all

11.14.2013 - 0.16
- Minimum required Google Chrome / Chromium version is now 31
- Polished Firmware Flasher UI
- Bugfixes related to flashing rev5 naze boards

11.14.2013 - 0.15
- Added firmware flasher (currently supporting 2 modes)
- 1 - "local flashing", from a .hex file
- 2 - "online flashing", latest firmware is fetched from github.com

11.12.2013 - 0.14
- Re-Enabled Servos tab (hopefully with all problems sorted out)
- Added support for "Motor Testing Mode" in Motor/Servo Outputs tab
- Updated MSP
- Utilizing notification API to promote new app version updates

11.10.2013 - 0.13
- Disabling Servos tab until all bugs are ironed out
- Bugfixes

11.09.2013 - 0.12
- Bugfixes related to failing connect procedure
- Bugfixes related to GPS data types
- Implemented experimental Servos tab
- Updated MSP to the latest version
- Major MSP refactoring, improving reliability in some cases
- Initial notify implementation for critical errors
11.02.2013 - 0.11
- Debug values are now displayed and plotted in Sensor tab (dade)
- Command history in CLI tab (dade)
- Bugfixes related to GPS tab

10.30.2013 - 0.10
- AUX Configuration now shows current AUX channel state
- Polished couple of texts
- Added changelog within the app
- 3D view in Initial Setup now displays model type selected

10.16.2013 - 0.9
- Polished Auxiliary configuration tab
- Polished Raw sensod data tab
- Updated libraries

[fiendie]

Hi guys, @fiendie recently hooked me up with stm32mini dev board, purely for development purposes, so i decided to pitch in "a little" to the community even thought i am not really using multiwii for flying.
There wasn't a multi-platform GUI for both MW and baseflight so i decided to make you guys something that's "up to the challenge" and hopefully easy enough to work with for the end user.

Enjoy

Great work cTn.
Thanks a lot.

[Crashpilot1000]

@cTn: Very nice project !! The altitude graph seems a little easy to confuse, but over all, great alternative!

Cheers
Kraut Rob

[cTn]

@cTn: Very nice project !! The altitude graph seems a little easy to confuse, but over all, great alternative!

Cheers
Kraut Rob

Do you have any recommendation of how would you like the altitude graph to look like? i could probably improve it if you tell me whats "wrong"

[Crashpilot1000]

The graph looks perfect until the hight turns negative. Then the scaling is out of wack just a small issue. BTW: will this gui also run on those google/android tablets?

[fiendie]

BTW: will this gui also run on those google/android tablets?

Not out of the box anyway.
http://www.pocketables.com/2012/12/no-plans-for-google-chrome-on-android-and-ios-to-run-extensions-or-apps.html

[Mis]

AUX configuration not work (display none). My MWC is custom version with some additional AUX setting, but working right with oryginal MWC GUI.

[cTn]

@Crashpilot1000 the baro < 0 bug should be fixed now
@Mis, show me your source, as it should be working

[Mis]

cTn:
Ok, my MWC source: http://romek_by.republika.pl/MK/MultiWii_2_21b_MIS.zip (with my current configuration for airplane).

[whakahere]

I'm having issues connecting this to a mac. The app starts but I can't connect. no new option comes up even after refreshing. I tried with bluetooth that works through multiwii and that didn't come up either. Any idea what I need to do?

[monkeyman]

I'm having issues connecting this to a mac. The app starts but I can't connect. no new option comes up even after refreshing. I tried with bluetooth that works through multiwii and that didn't come up either. Any idea what I need to do?

i'm struggling with this also on a mac,
can anyone help with this? i've got some naze32 boards i want to setup but can't,

i'm pulling my hair out here, hope someone can point us in the right direction.

[mopedcrosser]

This is awesome ! Thanks a lot !! Hopefully we get sth. like that as standard.. The regular gui is a little ..

PS: A "Read" button is missing to get the values for PID and RC. I had to click save once to get the values.. But saving lots of 0´s is not nice...

Sebastian

[patrik]

@monkeyman unfortunately there's a bug in Chrome (chrome.serial) that for some reason makes it unable to find the SiLabs serial port on OSX systems

luckily:

There is a workaround for this problem: you can add a symlink that Chrome will see as a valid TTY dev node. For example: 'sudo ln -s /dev/tty.SLAB_USBtoUART /dev/tty.usbserial', and now Chrome will find it.

[felixrising]

Star the hell out of that bug... get it higher priority..

[monkeyman]

<span>@monkeyman unfortunately there's a [url=<a href="https://code.google.com/p/chromium/issues/detail?id=230694]bug[/url]" class="smarterwiki-linkify">https://code.google.com/p/chromium/issues/detail?id=230694]bug[/url]</a> in Chrome (chrome.serial) that for some reason makes it unable to find the SiLabs serial port on OSX systems</span>

luckily:

There is a workaround for this problem: you can add a symlink that Chrome will see as a valid TTY dev node. For example: 'sudo ln -s /dev/tty.SLAB_USBtoUART /dev/tty.usbserial', and now Chrome will find it.

Hi Patrik,
is it possible can you give me a quick rundown on how to implement this workaround? i've had a look through various pages but am at a loss as how to get this up and running.
many thanks.

[crashlander]

sudo ln -s /dev/tty.SLAB_USBtoUART /dev/tty.usbserial

That is the complete rundown of workaround!
You just copy-paste that line into open Terminal.app window, while SILabs usb2serial port/dongle/converter is connected, and press enter. Respond with your login password when asked (it will not echo on screen).

Regards
Andrej

BTW: If you have some other (non SiLab's) USB2SERIAL converter you must change that part after first "tty." accordingly, you can get real name in original MWII GUI when selecting serial port.

[monkeyman]

sudo ln -s /dev/tty.SLAB_USBtoUART /dev/tty.usbserial

That is the complete rundown of workaround!
You just copy-paste that line into open Terminal.app window, while SILabs usb2serial port/dongle/converter is connected, and press enter. Respond with your login password when asked (it will not echo on screen).

Regards
Andrej

BTW: If you have some other (non SiLab's) USB2SERIAL converter you must change that part after first "tty." accordingly, you can get real name in original MWII GUI when selecting serial port.

this is the part i was after , where to stick the code, thanks for your help patrik and crashlander

i hope whakahere sees this.

[cTn]

configurator received some major updates in the past couple of days, i suggest current users or even new users have a look on the latest version

[scrat]

Thanks Andrej

[felixrising]

That's a great new feature. A major step up that turns it into a one stop baseflight shop. Very cool.

[scrat]

Changelog
11.14.2013 - 0.15
- Added firmware flasher (currently supporting 2 modes)
- 1 - "local flashing", from a .hex file
- 2 - "online flashing", latest firmware is fetched from github.com

11.12.2013 - 0.14
- Re-Enabled Servos tab (hopefully with all problems sorted out)
- Added support for "Motor Testing Mode" in Motor/Servo Outputs tab
- Updated MSP
- Utilizing notification API to promote new app version updates

11.10.2013 - 0.13
- Disabling Servos tab until all bugs are ironed out
- Bugfixes

11.09.2013 - 0.12
- Bugfixes related to failing connect procedure
- Bugfixes related to GPS data types
- Implemented experimental Servos tab
- Updated MSP to the latest version
- Major MSP refactoring, improving reliability in some cases
- Initial notify implementation for critical errors
11.02.2013 - 0.11
- Debug values are now displayed and plotted in Sensor tab (dade)
- Command history in CLI tab (dade)
- Bugfixes related to GPS tab

10.30.2013 - 0.10
- AUX Configuration now shows current AUX channel state
- Polished couple of texts
- Added changelog within the app
- 3D view in Initial Setup now displays model type selected

10.16.2013 - 0.9
- Polished Auxiliary configuration tab
- Polished Raw sensod data tab
- Updated libraries

When will be version 0.15 available? I have 0.14 no upgrade option?

[cTn]

chrome should auto update it for you, if it doesn't you can do it manually through tools -> extensions -> update extensions button
you should also make sure you are running the latest chrome by going into the about page

[scrat]

chrome should auto update it for you, if it doesn't you can do it manually through tools -> extensions -> update extensions button
you should also make sure you are running the latest chrome by going into the about page

Thanks. It's working

[--Oz--]

Does this work with blue tooth? (winXp or Win7 notebook) TIA

[cTn]

Does this work with blue tooth? (winXp or Win7 notebook) TIA

if you can configure the bluetooth module to use the same baud rate as baseflight, then yes it should work (depends mostly on the bluetooth unit though)

[--Oz--]

Does this work with blue tooth? (winXp or Win7 notebook) TIA

if you can configure the bluetooth module to use the same baud rate as baseflight, then yes it should work (depends mostly on the bluetooth unit though)

Thanks for the reply.

My BT dongle does not show a com port after plugging in (in device manager it is under "Blue tooth Radios" in Win7).

Any other baseflight configurators that work in windows using bluetooth? TIA

[timecop]

...
Then the problem is your fucking dongle, not the configurator.

[--Oz--]

We pretty much know it doesn't work, so;

Any other baseflight configurators that work in windows using bluetooth?

[felixrising]

Baseflight Configurator works just fine over a bluetooth ttl dongle. Both Win7 and OS X

[--Oz--]

Baseflight Configurator works just fine over a bluetooth ttl dongle. Both Win7 and OS X

TY!

[felixrising]

If it doesn't show up as a COM port, then you have either a driver issue with your bluetooth dongle or the serial bluetooth module isn't working/not paired or any one of a number of other issues. Generally they either work or they don't after being paired. You can interrogate the paired device and see what profiles/services are made available.. serial must be one of them. It might help to specify exactly what bluetooth ttl module you have.

[iamhandgun]

I found this thread because I couldn't get my board to show up in the configurator on osx. I did the terminal work around and now an option for usb serial shows up but it still won't connect when selected. It shows up and connects in the multiwii gui just fine. I have the rev4 white naze32 with latest chrome on osx 10.6.8 . Any clue as to what I'm doing wrong?

[QAV400]

Since the update to the Application a couple of days ago I can not get it to see the board/Commports at all. Was working perfect before that tho.

Also it all works if i use Multiwiiconf.exe So I assume something is up with the latest update and my specific hardware.

Im on a Rev4 acro naze32 on baseflight firmware dated 26-11-13
https://code.google.com/p/afrodevices/d ... p&can=2&q=

Any help?

[cTn]

Have you tried flashing the board with the latest firware? as there was some protocol changes that was made a while back, which could break compatibility

[QAV400]

I just removed the App and re instlled it in chrome, now its working , but when clicking on the tabs between reciever , Pids etc it freezes up and you have to click on them and back again heaps etc to get the tab to show up.

Is there a newer baseflight firmware that is proven tested and solid working? if so i have not been sure of where to find it, could you maybe help me in link or something pls

cheers

[cTn]

everyone that i know usually runs the latest version compiled/published on github, the easiest way to get it is to enrer firmware flasher and load online firmware from there

[felixrising]

QAV400. Baseflight is tested by its users... if you spot anything, feel free to log a issue on github or drop by #multiwii to provide some constructive feedback. The latest version of baseflight .hex is available on github or as cTn mentioned, you can just use the firmware flasher built into Baseflight Configurator.
https://github.com/multiwii/baseflight

[stronnag]

The latest version (0.25) no longer works for me, on either USB for Bluetooth. After opening the serial port, it hangs for several seconds before successfully closing the port. Other MSP tools, such as mwp and MultiWiiConf work fine. Earlier versions of baseflight also worked (excellently).

21:01:49 -- Running - OS: Linux, Chrome: 33.0.1750.117, Configurator: 0.25
21:01:55 -- Serial port successfully opened with ID: 5
21:02:05 -- No configuration received within 10 seconds, communication failed
21:02:05 -- Serial port successfully closed

[cTn]

The latest version (0.25) no longer works for me, on either USB for Bluetooth. After opening the serial port, it hangs for several seconds before successfully closing the port. Other MSP tools, such as mwp and MultiWiiConf work fine. Earlier versions of baseflight also worked (excellently).

21:01:49 -- Running - OS: Linux, Chrome: 33.0.1750.117, Configurator: 0.25
21:01:55 -- Serial port successfully opened with ID: 5
21:02:05 -- No configuration received within 10 seconds, communication failed
21:02:05 -- Serial port successfully closed

on which revision of naze do you have this problem ?
+ i am guessing you already run the latest firmware from github

[stronnag]

The latest version (0.25) no longer works for me, on either USB for Bluetooth. After opening the serial port, it hangs for several seconds before successfully closing the port. Other MSP tools, such as mwp and MultiWiiConf work fine. Earlier versions of baseflight also worked (excellently).

21:01:49 -- Running - OS: Linux, Chrome: 33.0.1750.117, Configurator: 0.25
21:01:55 -- Serial port successfully opened with ID: 5
21:02:05 -- No configuration received within 10 seconds, communication failed
21:02:05 -- Serial port successfully closed

on which revision of naze do you have this problem ?
+ i am guessing you already run the latest firmware from github

Apologies, for not stating previously; this is not naze, it's multiwii FC, (MW 2.3) which has worked well previously. In the case that baseflight now only supports naze, mea culpa, and perfectly understandable.

[QAV400]

everyone that i know usually runs the latest version compiled/published on github, the easiest way to get it is to enrer firmware flasher and load online firmware from there

As my Quad is worth a bit to me I will just use multiwiiconf.exe from now on as I dont want to really risk running always the latest firmware etc.. Once it flys how i like and im happy with it I dont want to have to change anything if its not needed.

thanks anyways.

[LVNeptune]

Your statement makes no sense...Baseflight Config doesn't FORCE you to upgrade, it's an option you have to select yourself... Stating you aren't going to use this because you don't want to update the firmware makes zero sense.

[QAV400]

Well a couple of times with my naze32 rev4 board the Baseflight chrome App has been working fine then the app updates it self and then I have issues with either jargon on the cli page or pages not loading or comm ports not even there at all to connect to and when i have updated the firmware on the board it has fixed the issues and since I could not figure out a way for the chrome app to stop updating itself it appeared i was in a sort of forced upgrade loop.

Just so you know its cool I am not upset or anything like that, I will just use that multiwiiconf.exe , as that is seeming to work and i dont think that will update itself, but im not 100% sure


cheers

[cTn]

in worst case scenario you can always use tagged releases that i have on github, as those won't auto update, however this wont help you much at the moment as there have been major changes in serial api and the "incompatible" brak was expected.

Regarding the non-naze hardware, support for anything else but naze was in the configurator for a while, there is a slim chance that this condition will be loosen up when i run more tests on generic mw hardware, but don't hold your breath on that one

[LVNeptune]

I see what you were referring too...The newer version of Baseflight Config was semi-broken with the current firmwares. On top of that my Baseflight Config wouldn't detect COM port AT ALL until I upgraded. I didn't even know there was an upgrade until someone on IRC pointed it out.

[tanman]

Is it normal not to have the compass dial on the initial setup page?

[cTn]

Is it normal not to have the compass dial on the initial setup page?

yes its normal, it was removed due to lack of space for the initial tab options

[tanman]

Is it normal not to have the compass dial on the initial setup page?

yes its normal, it was removed due to lack of space for the initial tab options

Thanks for much

[BlackRock]

So has anyone got a fix for the "new serial API fails to set higher baudrate then 38400" issue? I had my Naze32 all setup and then while waiting for RC parts to come in Chrome or Mac updated and now the app is completely broken. I've since reinstalled Chrome and Base Flight Configurator which pointed me to a convoluted thread on versioning and bugs, but no solution.

I upgraded the app to Configurator: 0.26, I'm running Mac OSX 10.9.2 and Chrome: 33.0.1750.117. I had the same problem on Mac OSX 10.9.1 as well.

Every time I open the app I get the following lines in the log window:
21:28:19 -- Running - OS: MacOS, Chrome: 33.0.1750.117, Configurator: 0.26
21:28:19 -- Configurator detected that you are running Chrome / Chromium with broken Serial API which breaks the communication completely on this platform
21:28:19 -- You can find more about this issue on this address "new serial API fails to set higher baudrate then 38400"

So now I'm completely stuck. I can't get it to connect or flash my Naze32. Is there a way to downgrade to previously stable versions? Is this still only a problem in Mac but fixed on other machines? I see that in version notes that in .25 it's running the new serial API for Chrome 33+.

I must be missing something. Either way I'm going nuts. My motors just came in and if I'm not flying by this weekend I'm pretty sure my head will explode

[cTn]

So has anyone got a fix for the "new serial API fails to set higher baudrate then 38400" issue? I had my Naze32 all setup and then while waiting for RC parts to come in Chrome or Mac updated and now the app is completely broken. I've since reinstalled Chrome and Base Flight Configurator which pointed me to a convoluted thread on versioning and bugs, but no solution.

I upgraded the app to Configurator: 0.26, I'm running Mac OSX 10.9.2 and Chrome: 33.0.1750.117. I had the same problem on Mac OSX 10.9.1 as well.

Every time I open the app I get the following lines in the log window:
21:28:19 -- Running - OS: MacOS, Chrome: 33.0.1750.117, Configurator: 0.26
21:28:19 -- Configurator detected that you are running Chrome / Chromium with broken Serial API which breaks the communication completely on this platform
21:28:19 -- You can find more about this issue on this address "new serial API fails to set higher baudrate then 38400"

So now I'm completely stuck. I can't get it to connect or flash my Naze32. Is there a way to downgrade to previously stable versions? Is this still only a problem in Mac but fixed on other machines? I see that in version notes that in .25 it's running the new serial API for Chrome 33+.

I must be missing something. Either way I'm going nuts. My motors just came in and if I'm not flying by this weekend I'm pretty sure my head will explode

That message is obsolete now, i just forgot to remove it, configurator works just fine on OSX & 33.0.1750.117