WiiLi.org

[blahblah]

Hello, I just got my new wiimote working (using it for midi stuff). Does anyone out there know how to make a gpie script that will process the ir data to give x,y co-ordinates and separate values for rotation?

Would come in very handy, hopefully for many of us.

thanks

[CarlKenner]

I haven't tried using IR for rotation, since I don't have a sensor bar. And it would only provide roll.

To seperate the rotation of the Wiimote from accelerations, you can use:

Wiimote.Roll
Wiimote.Pitch
Wiimote.Nunchuk.Roll
Wiimote.Nunchuk.Pitch

They will be in degrees. GlovePIE uses the accelerometers to update the rotation only while the wiimote has a total acceleration of about 1g. But it doesn't seperate rotation from acceleration very well. Sometimes it is too choppy updating the rotation, and sometimes it updates the rotation when it shouldn't.

There are lots of good scripts for positioning a mouse based on the IR data. Have a look at them. But at its most basic, all you need to do is read:
Wiimote.dot1x
Wiimote.dot1y

Note that dot1x is backwards from what you might expect (it is from the point of view of the camera).

[blahblah]

Thanks,

Actually what I meant was to be able to account for teh roll of the handset when in IR mode.

I want to be able to get x,y data from the IR but be able to change the roll of the wiimote at the same time.

When getting the x,y from the ir, if you change the roll of the wiimote to (for instance) 90 degrees, my x becomes the computers y. It should be possible to remove the roll from the xy data so that no matter what the orientation of the remote, we know its absolute position in xy (or at least where on the xy plane it is pointing). Does that make more sense?

[mrsoyo]

[squeakypants]

The Wiimote.Roll value (drawn from the accelerometers) and the IR's roll should be near to exactly the same. However, if you must: