Difference between revisions of "Configuration:WiiMotes with CWiiD"
Jump to navigation
Jump to search
| Line 40: | Line 40: | ||
/home/user/bin/wiid stop | /home/user/bin/wiid stop | ||
</pre> | </pre> | ||
| + | |||
| + | == Troubleshooting == | ||
| + | If you receive '''unable to open uinput''' when running wminput; | ||
| + | <pre> | ||
| + | Starting WMINPUT | ||
| + | Started! | ||
| + | unable to open uinput | ||
| + | </pre> | ||
| + | |||
| + | Your user does not have access to use the uinput module, see [[Advanced:udev-uinput-rules|udev Rules for uinput module]] | ||
Revision as of 03:51, 9 January 2011
CWiiD
You can have a WiiMote (or WiiMotes) sync to the PC using CWiiD. This program also runs in daemon mode so it can run constantly in the background behind Wah!Cade syncing as though your PC was an actual Wii.
There are numerous methods for starting applications at boot up, but here we will configure Wah!Cade to begin the daemon during startup and destroy it during exit.
Installation
Ubuntu derivatives may follow the Ubuntu Wiki for CWiiD installation instructions
- Install CWiiD
- Save the CWiiD Daemon Control Script as /home/<user>/bin/wiid
- Make the script executable chmod +x /home/<user>/bin/wiid
- Configure the script
- Use a script like the Wah!Cade Startup Wrapper start Wah!Cade.
Wah!Cade Startup Wrapper Example
#!/bin/bash
WAHCADEDIR="/home/user/wahcade"
PYTHON=`which python`
#
### PRE COMMANDS ###
# user commands to run before wahcade
#
# Start the wminput daemon
/home/user/bin/wiid start
#
### WAHCADE COMMAND ###
#
cd ${WAHCADEDIR}
${PYTHON} wahcade.py
wait
#
### POST COMMANDS ###
# user commands to run after wahcade
#
# Stop the wminput daemon
/home/user/bin/wiid stop
Troubleshooting
If you receive unable to open uinput when running wminput;
Starting WMINPUT Started! unable to open uinput
Your user does not have access to use the uinput module, see udev Rules for uinput module