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-05-21 13:49] foosel [Current state of the headless client] |
misc:hacks:rasberrypi [2013-07-04 14:34] macke [Current state of the headless client] |
||
---|---|---|---|
Line 29: | Line 29: | ||
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 81: | Line 81: | ||
INFO: | INFO: | ||
INFO: | INFO: | ||
+ | </ | ||
+ | |||
+ | **Note**: 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 " | ||
+ | |||
+ | |||
+ | **Note**: If you have more than one controller attached, you can select the one to use using the commandline parameter '' | ||
+ | |||
+ | < | ||
+ | usage: cfheadless [-h] [-u URI] [-i INPUT] [-d] [-c CONTROLLER] | ||
+ | [--controllers] | ||
+ | |||
+ | optional arguments: | ||
+ | -h, --help | ||
+ | -u URI, --uri URI URI to use for connection to the Crazyradio dongle, | ||
+ | defaults to radio:// | ||
+ | -i INPUT, --input INPUT | ||
+ | Input mapping to use for the controller, defaults to | ||
+ | PS3_Mode_1 | ||
+ | -d, --debug | ||
+ | -c CONTROLLER, --controller CONTROLLER | ||
+ | Use controller with specified id, id defaults to 0 | ||
+ | --controllers | ||
</ | </ | ||
Line 94: | Line 128: | ||
[[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)</ |
* < | * < | ||
- | * The headless client will open the first input-device found (so don't plug more than one) | + | * <del>The headless client will open the first input-device found (so don't plug more than one)</ |
- | * 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 115: | Line 149: | ||
if test " | if test " | ||
then | then | ||
- | / | + | / |
echo $! > / | echo $! > / | ||
else | else | ||
Line 127: | Line 161: | ||
</ | </ | ||
- | Don't forget to make it executable: '' | + | 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> | ||
+ | </ | ||
+ | |||
+ | 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 " | And for the XBox360 Controller (after an " | ||
Line 145: | Line 186: | ||
:!: **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 ===== | ||