nkruzan / ardu-configurator

ArduPilot Configurator

ArduPilot Configurator is a crossplatform configuration tool for the ArduPilot flight control system.

It runs as an app within Google Chrome and allows you to configure the ArduPilot software running on any supported ArduPilot target.

Various types of aircraft are supported by the tool and by ArduPilot, e.g. quadcopters, hexacopters, octocopters and fixed-wing aircraft.

Installation

Depending on target operating system, ArduPilot Configurator is distributed as standalone application or Chrome App.

Windows

1. Visit release page
2. Download Configurator for Windows platform (win32 or win64 is present)
3. Extract ZIP archive
4. Run ArduPilot Configurator app from unpacked folder
5. Configurator is not signed, so you have to allow Windows to run untrusted application. There might be a monit for it during first run

Linux

1. Visit release page
2. Download Configurator for Linux platform (linux32 and linux64 are present)
3. Extract tar.gz archive
4. Make the ArduPilot-configurator file executable (chmod +x ArduPilot-configurator)
5. Run ARDUPILOT Configurator app from unpacked folder

Mac

1. Visit release page
2. Download Configurator for Mac platform
3. Extract ZIP archive
4. Run ArduPilot Configurator
5. Configurator is not signed, so you have to allow Mac to run untrusted application. There might be a monit for it during first run

ChromeOS

ArduPilot Configurator form ChromeOS is available in Chrome Web Store

Building and running ArduPilot Configurator locally (for development or Linux users)

For local development, node.js build system is used.

1. Install node.js
2. From project folder run npm install
3. To build the JS and CSS files and start the configurator:
   • With NW.js: Run npm start.
   • With Chrome: Run npm run gulp. Then open chrome://extensions, enable the Developer mode, click on the Load unpacked extension... button and select the ARDUPILOT-configurator directory.

Other tasks are also defined in gulpfile.js. To run a task, use ./node_modules/gulp/bin/gulp.js task-name. Available ones are:

• build: Generate JS and CSS output files used by the configurator from their sources. It must be run whenever changes are made to any .js or .css files in order to have those changes appear in the configurator. If new files are added, they must be included in gulpfile.js. See the comments at the top of gulpfile.js to learn how to do so. See also the watch task.
• watch: Watch JS and CSS sources for changes and run the build task whenever they're edited.
• dist: Create a distribution of the app (valid for packaging both as a Chrome app or a NW.js app) in the ./dist/ directory.
• release: Create NW.js apps for each supported platform (win32, osx64 and linux64) in the ./apps directory. Running this task on macOS or Linux requires Wine, since it's needed to set the icon for the Windows app. If you don't have Wine installed you can create a release by running the release-only-linux task.

Quick start ( Devs use linux , so other platforms YMMV): 'npm run dev' to run it from the source folder without bundling any resources, great for debug and code hacking. Its also the only way the code runs right this instant., sorry, we haven't got any release ready yet. 'npm start' is very similar, but uses a 'bundled' main.html If the app starts-up for you, but right-click doesnn't allow you to use chrome-dev-tools or inspect stuff, then you don't have the 'sdk' version of NW installed. The command/s to try to remedy that are (one or more of these might help):
nvm deactivate mv ~/.npmrc ~/.npmrc.bak rm -rf node_modules/nw rm package-lock.json npm install --save [email protected] npm install --save [email protected] -g export NWJS_BUILD_TYPE=sdk; npm install

Bundling/releasing not working properly just now, but when it's working it will run like this: 'npm run gulp dist' to bundle it. 'npm run gulp release' to make win32/win64/osx/linux32/linux64 packages.

BUGs? absolutely.

See BUGS page

Different MAP providers?

See MAPS page

Notes

WebGL

Make sure Settings -> System -> "User hardware acceleration when available" is checked to achieve the best performance

Linux users

1. Dont forget to add your user into dialout group "sudo usermod -aG dialout YOUR_USERNAME" for serial access
2. If you have 3D model animation problems, enable "Override software rendering list" in Chrome flags chrome://flags/#ignore-gpu-blacklist

Support

GitHub issue tracker is reserved for bugs and other technical problems. If you do not know how to setup everything, hardware is not working or have any other support problem, please consult:

• discuss user forums thread

• developer chat

Issue trackers

For ArduPilot configurator issues raise them here

https://github.com/ArduPilot/ArduConfigurator/issues

For ArduPilot firmware issues raise them here

https://github.com/ArduPilot/ardupilot/issues

Developers

We accept clean and reasonable patches or PRs, submit them!

Credits - happy to correct these credits if they are wrong or incomplete.

ctn - author and maintainer ofof stuff from which this project was forked. Hydra - author and maintainer of stuff from which this project was forked. Konstantin Sharlaimov/DigitalEntity - author and maintainer of stuff from which this project was forked. Paweł Spychalski - author and maintainer of stuff from which this project was forked.