HOWTO: Wii remote in Ubuntu 8.04

[tqft]

You can restart udev once you have updated the rules with

sudo /etc/init.d/udev restart

Rebooting the machine is generally cleaner and safer but not always practical for testing

[Rhubarb]

You can restart udev once you have updated the rules with

sudo /etc/init.d/udev restart

Rebooting the machine is generally cleaner and safer but not always practical for testing

Thanks tqft

That is indeed a smarter way of doing things.
Another way of achieving the same result would be:

sudo service udev restart

... some day I'll see if the wiimote needs any special configuration for Ubuntu Karmic. But now I'm in too much of a lazy mood

[Gidskid]

I have a glovepie script and want to know if i can convert it to a Cwiid Config File? It requires 2 wiimotes which is another complication.



Thanks


G

[thelethargarian]

I have read through most of this thread, but I can not find out how to use the D-pad to move the cursor smoothly when you hold it. I find that using the ir and sensor bar mode isn't completely accurate for small buttons, so I would like to be able to use the D-pad once I get in the range with the ir mode.

I've tried

Wiimote.Dpad.X    = REL_X
Wiimote.Dpad.Y    = -REL_Y

, but that just moves one pixel per button press.

Thanks,
thelethargarian

[thelethargarian]

Nobody knows?

[acatak]

old thread, i know but will it work on 10.10?

[emoguitarist06]

old thread, i know but will it work on 10.10?

Bump

will it?

[ibanezguy19]

i want to assign the buttons on the wiimote to keyboard combinations(like CTRL+C). How would I go about doing this?

[inate]

Help, I'm stuck at the wminput 00:1A:1A:10:6C:0D part when I type this in it tells
unable to open uinput

[hfxdesign]

For now, ignore the uinput error, it starts it up (i checked the code). It's just a dev error, they forgot to check if the file exists before executing, I'm new to c++ but have had design experience in other languages, so I'm trying to find a workaround, the closest thing I've come to for newer ubuntu is removing "/dev/input/uinput" from the list. I'll keep looking into this. For those of you having compile errors, I had them too, they are due to missing headers in some of the files. Do some research on it and edit the .hpp files that are throwing errors and add the includes (most are stdio.h and stdint.h) until you get it compiled.

UPDATE: I fixed the uinput error, here's how:

1. Open the uinput.cpp file in your source folder
2. Find this statement near the top of the file:

if ((fd = open(uinput_filename[i], O_WRONLY | O_NDELAY)) >= 0)
        {
          break;
        }
      else
        {
          std::cout << "Error: " << uinput_filename[i] << ": " << strerror(errno) << std::endl;

3. Change to this:

if ((fd = open(uinput_filename[i], O_WRONLY | O_NDELAY)) >= 0)
        {
          std::cout<< "uinput (" << uinput_filename[i] << ") started" <<std::endl;
          break;
        }
      else if ( i >= 2 )
        {
          std::cout << "Error: " << uinput_filename[i] << ": " << strerror(errno) << std::endl;

That will fix the error messages, just a little bit of debugging.