This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
projects:crazyflie:pc_utils:index [2012-03-10 16:08] arnaud |
projects:crazyflie:pc_utils:index [2021-06-24 16:52] (current) kimberly |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | <WRAP center round important 60%> | ||
| + | This page has deprecated and will be archived. Please go to [[https:// | ||
| + | </ | ||
| ====== Crazyflie PC utilities ====== | ====== Crazyflie PC utilities ====== | ||
| - | The Crazyflie PC utilities are developed using Python 2.6. The Crazyflie library is used from the command line tools as well as a graphical user interface. | + | The Crazyflie PC utilities are developed using Python 2.7. The Crazyflie library is used from the command line tools as well as a graphical user interface. For install instructions of PC side software please see [[projects: |
| - | ===== Common install instructions | + | ====== Crazyflie Python Library ====== |
| - | The following has to be installed for the PC utilities to work: | + | The Crazyflie library can be used to easily integrate control and communication with the Crazyflie quadcopter into an application. Currently |
| - | * [[http:// | + | |
| - | * [[http:// | + | |
| - | * [[http:// | + | |
| - | ===== Graphical User Interface | + | ====== List of applications ====== |
| - | ==== Install instructions | + | ===== Crazyflie control UI ===== |
| - | Besides the common bindings the following has to be installed for the user interface | + | The Crazyflie control UI is used to pilot the Crazyflie using a graphical |
| - | * [[http:// | + | |
| - | * [[http:// | + | |
| - | ==== Using the GUI ==== | + | < |
| + | usage: cfclient [-h] [--debug DEBUG] | ||
| - | ===== Command line tools ===== | + | cfclient - Crazyflie graphical control client |
| - | ==== Install instructions ==== | + | optional arguments: |
| - | Besides the common bindings nothing has to be installed. | + | -h, --help |
| + | --debug DEBUG, -d DEBUG | ||
| + | set debug level [minimal, info, debug, debugfile] | ||
| + | </ | ||
| - | ==== gamepadCtrl.py | + | ===== Crazyflie headless client |
| + | The Crazyflie headless client is intended to be run on the Raspberry Pi (see [[misc: | ||
| - | ==== crazyload.py ==== | ||
| - | |||
| - | // | ||
| - | |||
| - | To program a copter with a firmware compile in bootloader mode (see build environment documentation): | ||
| < | < | ||
| - | $ python crazyload.py | + | usage: cfheadless [-h] [-u URI] [-i INPUT] [-d] [-c CONTROLLER] |
| - | </ | + | |
| - | Here // | + | |
| - | The bootloader is normally able to automatically reset the copter in bootloader | + | optional arguments: |
| - | < | + | -h, --help |
| - | $ python crazyload.py | + | -u URI, --uri URI URI to use for connection |
| + | defaults to radio://0/10/250K | ||
| + | -i INPUT, --input INPUT | ||
| + | Input mapping to use for the controller, defaults to | ||
| + | | ||
| + | -d, --debug | ||
| + | -c CONTROLLER, --controller CONTROLLER | ||
| + | Use controller with specified id, id defaults to 0 | ||
| + | --controllers | ||
| </ | </ | ||
| - | This command is an example that would work if the copter is currently running a crazyflie firmware with radio configured to channel 77. | ||
| - | |||