Differences

This shows you the differences between two versions of the page.

--- misc:hacks:rasberrypi [2013-08-13 03:54]
absoloodle37 Identified xbox controller input and corresponding id's in .json file
+++ misc:hacks:rasberrypi [2021-06-24 16:45] (current)
kimberly
@@ Line 1: / Line 1: @@
+<WRAP center round important 60%>
+This page has deprecated and will be archived. Please go to [[https://www.bitcraze.io/]].
+</WRAP>
 ====== Using the Raspberry Pi as a base station for flying ======
-You should setup the CF Headless client (see [[#current_state_of_the_headless_client|below]]) instead of the regular PC client on your Pi, since the UI seems to a bit too heavyweight for the Pi (controlling got **very** laggy during tests).
+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://wiki.bitcraze.se/projects:crazyflie:binaries:raspberrypi|here.]]
+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/Debian/Raspbian.  It allows you to adjust control variables (like X-mode or max thrust) by changing the values in a configuration file.  For more information visit [[https://github.com/hsanjuan/crubyflie|the Crubyflie installation page.]]
+====== 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.  You should setup the CF Headless client (see [[#current_state_of_the_headless_client|below]]) instead of the regular PC client on your Pi, since the UI seems to a bit too heavyweight for the Pi (controlling got **very** laggy during tests).
 For the following installation instructions it is assumed that you are running the popular [[http://www.raspbian.org|Raspbian]] distrubution on your Pi.
@@ Line 26: / Line 37: @@
 and start it: ''sudo xboxdrv''
+<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.
+</WRAP>
 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 ''python2'' could not be found, edit ''~/crazyflie-pc-client/bin/cfheadless'' and change the ''python2'' in the first line to ''python'')):
@@ Line 157: / Line 174: @@
 </code>
-and (as root) create a file ''/root/bin/cfheadless'' with the following contents:
+and (as root) you will create a file ''/root/bin/cfheadless'' using the instructions below, with the following contents:
 <code bash>
@@ Line 175: / Line 192: @@
 </code>
-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: ''sudo -i'' and then navigate to the /root/bin/ folder: ''cd /root/bin/''.  Create the cfheadless file by typing: ''touch cfheadless'' to create the file.  Then ''nano cfheadless'' to edit the file with the code shown above ('sudo' prefix not needed because you're already root).  Use the same method for the xbox360 file described in the section below, if using a xbox360 controller.  Don't forget to make your files executable after you've created them: ''chmod +x /root/bin/cfheadless'' and ''chmod +x /root/bin/xbox360''. Once you've created the cfheadless file (and xbox360 file, if needed), exit the root mode by typing Ctl + D.  You may have to restart your RPi in order for all new udev rules to take effect. Rather than unplug/replug your RPi, consider the following command:
+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: ''sudo -i'' and then navigate to the /root/bin/ folder: ''cd /bin/''.  Create the cfheadless file by typing: <code bash>touch cfheadless</code> to create the file.  Then <code bash>nano cfheadless</code> to edit the file, adding the code shown above ('sudo' prefix not needed because you're already root).  Remember to substitute your desired config file in the appropriate place in the code above (replace: <your input config...>).  Use the same method for the xbox360 file described in the section below if using a xbox360 controller:
-<code bash>sudo shutdown -h now -r
+For the XBox360 Controller (after an "apt-get install xboxdrv"):
-</code>
-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://forum.bitcraze.se/viewtopic.php?p=490#p490|in this forums post]] or as detailed below.
-And for the XBox360 Controller (after an "apt-get install xboxdrv"):
 Create a udev file ''/etc/udev/rules.d/99-xbox360.rules'' with contents (if using a Microsoft wireless gaming receiver):
@@ Line 197: / Line 207: @@
         killall -9 xboxdrv
 fi</code>
+Don't forget to make your files executable after you've created them: ''chmod +x /bin/cfheadless'' and ''chmod +x /bin/xbox360''. Once you've created the cfheadless file (and xbox360 file, if needed), exit the root mode by typing Ctl + D.  You may have to restart your RPi in order for all new udev rules to take effect. Rather than unplug/replug your RPi, consider the following command:
+<code bash>sudo shutdown -h now -r
+</code>
+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.

Bitcraze Wiki

User Tools

Site Tools

Differences

Page Tools