I'm totaly newbie in Wiimote WB, as I have bought my Wiimote just today. But I think that rightclick could have a pretty simple solution.
If the sampling period of Wiimote is 10ms, what we need for the right click is let's say 15ms IR flash to make sure, that Wiimote has caught it. This means, that wiimote will return 1 or max 2 samples with IR on. On the other hand it is necessary to ensure, that left click  will take longer to 30ms.
On the side of IR pen it is an easy task for some microcontroller (I'll try to construct it with PIC10F202 in the next days).
On the side of Windows it is just the question of recognition of the  length of IR LED on-state.

Jakub

 

There was another post that questioned Johnny's statement that the frame rate of the Wii's IR camera is 100 Hz, roughly the same as the rate at which it sends reports over Bluetooth. That post stated that the PixArt camera used in the Wiimote has a frame rate of 30 Hz. This question is quite important for anyone building in a right-click using a flashing code.

I built a simple flasher circuit using a 555 timer IC with some pots and hacked the whiteboard app to display a basic "oscilloscope trace", high for IR point detected and low for no IR point detected. The trace takes 16 seconds to cross the form, with a width of 1280 pixels. That is 80 reports per second. I found that I could increase the frequency of the IR pulses to the point where the Wiimote would reliably show a "high" signal for 1 to 2 reports. Any frequency above this would result in very obvious aliasing, with the signal switching between longer periods of high and low. The aliasing must indicate that the frequency was approaching the frame rate of the camera.

This seems to confirm that the camera operates at a frame rate closer to 100 Hz than 30 Hz, and this should be really good news for anyone wanting to use flashing codes.

I did some experimentation and found that the maximum rate at which one can double-click is about 10 Hz. This is relevant because we don't want a double-click to register as a right-click.

The IR camera in the wee remote only has to detect and report blob positions, I have read that this
is done by dedicated 'on sensor' logic so 100Hz is probably feasible as you've found.


Nial.

I have already programmed a µC. It flashes with 20ms to be sure that every flash can be recognized. The setup is a little bit big, since I am using the µC board as stroboscope with high power LEDs.

Burning will not be that problematic. You can use the serial interface on your pc to emulate a burning devive. Of course it will be slower to write/read ...

The only thing I'm missing is the recognition software ;P

personally i am going this route
http://h10010.www1.hp.com/wwpc/id/en/sm/WF06c/A1-1697201-1698431-1698431-1698473-1698473-78019431.html

i bought 10 of these bluetooth (thin!) mice for $6 each. they weigh 42g each!

i want to wire up an IR led to run continuously off its battery so instead of the IR flash being a mouse click, the IR is constantly on setting the mouse position

the left and right click are built into the mouse so its a simple solution!

Exactly, then its easier to use the WiiRemote as its normally used, in your hand and the ir leds at the screen.. then you got a whole lot more buttons & the accel. functions

troy59: What idea do you mean? Do you mean using the wiiremote itself as the mouse? Or do you mean something else? Because thats exactly how the WiiRemote operated without any hacks/mods