This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
misc:hacks:rasberrypi [2013-08-13 03:54] absoloodle37 Identified xbox controller input and corresponding id's in .json file |
misc:hacks:rasberrypi [2013-08-13 05:04] absoloodle37 Added clarity and example code |
||
---|---|---|---|
Line 157: | Line 157: | ||
</ | </ | ||
- | and (as root) create a file ''/ | + | and (as root) you will create a file ''/ |
<code bash> | <code bash> | ||
Line 175: | Line 175: | ||
</ | </ | ||
- | 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 197: | Line 190: | ||
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. |