This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
misc:hacks:rasberrypi [2013-06-09 23:31] absoloodle37 Clarified how to create the cfheadless and xbox360 executable files in the /root/bin folder |
misc:hacks:rasberrypi [2017-05-22 11:43] arnaud [Install the headless client] |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== Using the Raspberry Pi as a base station for flying ====== | ====== Using the Raspberry Pi as a base station for flying ====== | ||
- | You should setup the CF Headless client (see [[# | + | In order to make it easy for users that have a Raspberry Pi to test out our headless client we prepared an SD-card image that is ready to use out of the box. |
+ | |||
+ | The full SD-card image, and instructions on how to install it are located [[http:// | ||
+ | |||
+ | Instead of the official Python headless client, there is also a working Ruby version of the headless client, developed by a user. This version, called Crubyflie, can be installed on top of the SD-card image described above or on a standalone version of Linux/ | ||
+ | |||
+ | ====== Manual Installation ===== | ||
+ | |||
+ | As an alternative to a full SD-card image, you can manually install the headless Python client as a program on your Pi. | ||
For the following installation instructions it is assumed that you are running the popular [[http:// | For the following installation instructions it is assumed that you are running the popular [[http:// | ||
Line 26: | Line 34: | ||
| | ||
and start it: '' | and start it: '' | ||
+ | |||
+ | <WRAP center round tip 80%> | ||
+ | **NOTE** | ||
+ | |||
+ | All modern Linux distribution now have a kernel driver for the x-box gamepad. Thus it is unlikely the //xboxdrv// user-space driver is needed. | ||
+ | </ | ||
Plugin your Crazyradio and your controller, power up the Crazyflie and start the client (via SSH and Ethernet or by using an USB hub to connect Crazyradio, controller and keyboard)((If you get an error message that '' | Plugin your Crazyradio and your controller, power up the Crazyflie and start the client (via SSH and Ethernet or by using an USB hub to connect Crazyradio, controller and keyboard)((If you get an error message that '' | ||
- | python ~/ | + | python ~/ |
The client should start up, hopefully find your Crazyradio dongle, your Crazyflie and your controller and start accepting commands: | The client should start up, hopefully find your Crazyradio dongle, your Crazyflie and your controller and start accepting commands: | ||
Line 82: | Line 96: | ||
INFO: | INFO: | ||
</ | </ | ||
+ | |||
+ | ===== Manually Customizing Your .json Configuration File ===== | ||
+ | If you created a customized .json file for your xbox controller using a Windows PC and the cfclient GUI and are planning to copy it over to your Raspberry Pi, here is some advice: | ||
+ | |||
+ | -save the new .json file as something different than the default, so you can recognize it easily. | ||
+ | |||
+ | -the new .json file is not located in the Program Files(x64)/ | ||
+ | |||
+ | -copy your new .json file into the correct RPi folder: / | ||
+ | |||
+ | < | ||
+ | |||
+ | Verify netatalk was installed successfully on your RPi by checking the Finder window on your Mac for a " | ||
+ | |||
+ | -the cfheadless client on RPi may not recognize the same controller channel " | ||
+ | |||
+ | Xbox Controller Input = id# | ||
+ | |||
+ | Left stick vertical = 1 | ||
+ | |||
+ | Left stick horizontal = 0 | ||
+ | |||
+ | Right stick vertical = 3 | ||
+ | |||
+ | Right stick horizontal = 2 | ||
+ | |||
+ | Right trigger = 4 | ||
+ | |||
+ | Customize your flying configuration anyway you like using the inputs/ | ||
**Note**: If you have more than one controller attached, you can select the one to use using the commandline parameter '' | **Note**: If you have more than one controller attached, you can select the one to use using the commandline parameter '' | ||
Line 113: | Line 156: | ||
[[http:// | [[http:// | ||
- | * Still dependent on QT (the plan is to remove this very soon) | + | * <del>Still dependent on QT (the plan is to remove this very soon)</ |
- | * Not much error handling yet (the plan is to improve this) | + | * <del>Not much error handling yet (the plan is to improve this)</ |
* < | * < | ||
* < | * < | ||
- | * No good way to quit it yet so you will have to kill the process | + | * <del>No good way to quit it yet so you will have to kill the process</ |
===== Make the client startup automatically on Crazyradio plug in ===== | ===== Make the client startup automatically on Crazyradio plug in ===== | ||
Line 128: | Line 171: | ||
</ | </ | ||
- | and (as root) create a file ''/ | + | and (as root) you will create a file ''/ |
<code bash> | <code bash> | ||
Line 146: | Line 189: | ||
</ | </ | ||
- | You can only create the cfheadless file above in the /root/bin/ folder by being root--not pi or any other user name. Switch to root by typing: sudo -i and then navigating | + | You can only create the cfheadless file above in the /root/bin/ folder by being root--not pi or any other user name. Switch to root: '' |
- | And for the XBox360 Controller (after an " | + | For the XBox360 Controller (after an " |
Create a udev file ''/ | Create a udev file ''/ | ||
Line 161: | Line 204: | ||
killall -9 xboxdrv | killall -9 xboxdrv | ||
fi</ | fi</ | ||
+ | |||
+ | Don't forget to make your files executable after you've created them: '' | ||
+ | |||
+ | <code bash> | ||
+ | </ | ||
+ | |||
+ | The -h halts all processes, the -r is the command to reboot after shutdown. | ||
+ | |||
+ | This should now take care to startup the headless client when you plug in the dongle and (hopefully ;-)) kill it again when you unplug. If you need any additional setup to get your controller working, you can add a similar udev-rule for that to take care of everything upon plugging in the controller as well. | ||
:!: **Important** :!: Due to the current state of the client, you **must** make sure to first connect your controller and power up the Crazyflie before connecting the Crazyradio dongle and thus starting the client. If the client can't find either controller or Crazyflie, it will just hang and you'll have to re-plug the dongle again. | :!: **Important** :!: Due to the current state of the client, you **must** make sure to first connect your controller and power up the Crazyflie before connecting the Crazyradio dongle and thus starting the client. If the client can't find either controller or Crazyflie, it will just hang and you'll have to re-plug the dongle again. | ||
- | **Troubleshooting** If it still doesn' | + | **Troubleshooting** |
- | * / | + | If it still doesn' |
+ | * / | ||
* / | * / | ||
+ | |||
+ | Also, if xboxdrv can't be run without the sudo command, or there are other permissions issues with the xbox wireless usb controller, try adding the the xbox360 wireless receiver to a group you created that has root privileges, like ' | ||
+ | |||
+ | <code bash> | ||
+ | |||
+ | Also, if running the xboxdrv command from a terminal window gives you the following error: | ||
+ | |||
+ | <code bash> | ||
+ | |||
+ | ...your controller may very well have already started automatically per the udev rule you created above and could be working correctly and currently is in use. Make sure your wireless xbox controller is powered on and connected (green arc showing), turn on your crazyflie and then plug in your crazyradio. | ||
+ | |||
===== Make your base station portable ===== | ===== Make your base station portable ===== | ||