IR Raw tracking gives you access to the 4 individual IR objects the Wiimote detects, leaving you the task to filter and interpret the data. A user once created a light painting installation with it. You can use it to control the mouse cursors. It is designed to work with the Mouse Absolute events.

The IR(x, y) tracking is a composite of the 4 tracked IR objects into one virtual (x, y) cursors. It can help tweaking this parameter, but in practice I have not seen huge improvements. IR sensitivity is a setting that change the hardware sensivity. In my case I was usually using candlelights, but when I used a customized IR bar, it really made the difference, because the IR source was more steady and accurate. You have to find the best lighting source for your application. IR tracking works normally but is greatly affected by lighting conditions. It's strange, as this process was exteremly simple when using the gyroscope to track head movements. If I start at 0˚ = 0.5 (IR, x) then rotate the glasses to 30˚, and then back again to 0˚, it does not return to its original value of 0.5. Why does the data appear to be randomly jumping around? e.g. Should I use IR(x, y) tracking, or IR raw tracking? (I think the latter, especially as I will be extending this to 2 Wii Remotes later)Ģ. Its value was either 0125 or 0.0625, with no obvious reason for whether it was one or the other.ġ. I also tried using the IR raw tracking, but the size parameter (s) didn't really change as I varied the rotation angle or the distance. I have tried changing the sensitivity or the IR and also the smoothing - these help a little, but I'm still not getting data that makes much sense to me. a 0˚) and the data appears to often move about very randomly. The problem I have is not understanding what the data (x, y) represents - I've tried many different movements, and there seems to be no point of reference (i.e. I have the IR glasses, and the wii is definitely detecting them and I see the data in Pure Data, using 'udpreceive'. Now, I want to create a different head-tracker, using a Wii and a pair of IR Leds (Johnny Lee style). I've already created a head-tracking system, whereby the user wears a Wii RemotePlus on their head - all working nicely. The camera housings are mounted with pipe brackets to another pvc pipe so they can be rotated to change the covered area.Firstly, thanks for OSCulator - it's a great piece of software, and up until recently hasn't been a problem to use. Caps for the pipes can be used to hold the original ir-filter from the Wiimote. Arduino Mega with wiring to the camerasįor a convenient setup the two camera modules are connected with long flexible wires and stored inside some small pvc pipes.

For this project a CD4053BCN analog multiplexer is sufficient. There are IIC multiplexers available to drive a larger number of I2C devices. All cameras use the same I2C hardware address. Connecting multiple cameras at the same time requires additional hardware. A ~25MHz Oscillator is needed as clock input for the camera. Two Pixart ir-camera modules from Nintendo WiimotesĬonnecting such a camera to an Arduino board is pretty straightforward. One way is to break that case open and resolder the module to new wires. The camera module resides in a small metallic case. The straightforward way is to take them out of the Wiimotes by hand. For a stereo tracking system, two cameras are needed. That makes it an ideal device for cheap and simple ir-tracking applications. The camera is connected via I2C and already has a four point blob-tracking implemented on its chip. The Nintendo Wii Remote Controller contains a high framerate (200Hz, possibly more) infrared camera. This project implements a cheap and simple infrared stereo tracking system with consumer hardware.

Using the ir and wiimote osculator