This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
misc:hacks:rasberrypi [2013-07-04 14:34] macke [Current state of the headless client] |
misc:hacks:rasberrypi [2015-07-15 16:31] 127.0.0.1 external edit |
||
---|---|---|---|
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 83: | Line 91: | ||
</ | </ | ||
- | **Note**: | + | ===== 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. | -save the new .json file as something different than the default, so you can recognize it easily. | ||
Line 95: | Line 104: | ||
Verify netatalk was installed successfully on your RPi by checking the Finder window on your Mac for a " | 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 " | + | -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 143: | Line 165: | ||
</ | </ | ||
- | and (as root) create a file ''/ | + | and (as root) you will create a file ''/ |
<code bash> | <code bash> | ||
Line 161: | Line 183: | ||
</ | </ | ||
- | 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: '' | + | 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: '' |
- | <code bash> | + | For the XBox360 Controller (after an " |
- | </ | + | |
- | + | ||
- | 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. An example for the Microsoft Wireless XBox360 controller for PC can be found [[http:// | + | |
- | + | ||
- | And for the XBox360 Controller (after an " | + | |
Create a udev file ''/ | Create a udev file ''/ | ||
Line 183: | Line 198: | ||
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. |