Using a wiimote with LabVIEW

[Ramsey_]

This question may be more appropriate on a separate thread, but I'm hoping to tap into the knowledge of everyone who contributed to this one.

A colleague of mine flagged up an interesting spate of robberies in the local area where only Wiis were taken (laptops, televisions etc left behind). In some cases the property was only vacant for a short period of time such as tens of minutes, and the Wii was in some convoluted part of the house (such as a loft-conversion games room). My colleague postulated that the Wiis were perhaps being detected, and maybe also located, wirelessly. It may simply be the case that the properties are being watched and the burglars are noting which window in the house they can see people flailing their wiimotes around in, but if the crimes are more high tech, can anyone propose how you could detect a Wii in standby mode? Do Wiis still emit any RF when on standby? Can any wiimote (i.e. not a synched one) be used to turn on any wii, and therefore get it into a more 'active' mode?

Thanks

Ramsey

[Alistair]

Hi Kovacs,

Thanks for the reply, I know it is definitely possible to get the battery information as you said, for example, using Brian Peeks exe file.  I was curious as to to whether this can also be read into LabVIEW using the VI's created by Sam Shearman

Thanks,

Alistair

[Nik1]

Hi, I've downloaded the Wiimote library and Im trying to extract the 4 X and Y IR values from the wiimote using the 'Acquistion and IR polled' VI, upon running this VI, it only seems to pick up one LED or display one set of X and Y values and not the remaining 3. The wiimote is paired fine with the computer, Ive checked that all the IR LEDs are being picked up correctly using the Test.exe in the WiimoteLib. Any Suggestions why the VI is not showing the remaining X/Y values?

[Kovacs]

@Ramsey

After reading your post I attempted to switch on my wii with my second (not-synched) wiimote and you're right, I was still able to switch it on.

But not only that, but when I tried to make contact with it (by pressing the A button) I got a different pattern of blinking lights than when it was switched off.

That is, when the wii was switched off the four lights would blink a certain number of time and then stop, but when it was switched on they would blink, then stop for a moment and then blink again. So yes, by the looks of it a person would know that the wii is now switched on (and close-by) when the different pattern emerges.

@Alistair

Ah, I see.

Well if it's possible I haven't found it yet among his VIs.

@Nik1

I stumbled upon the same problem. The "event" VI seems to do the trick though.

Perhaps if you compare the two you might stumble upon a difference.

[Ramsey_]

Hi Kovacs

That is very interesting, thankyou, I may investigate this further...!

Sorry to everyone else for temporarily hijacking this thread.

Thanks

Ramsey

[Nik1]

Hi Kovacs, I ran the 'event.vi' as well and the same issue is still there when running it. The VI is only picking up one set of X, Y, Raw X and Raw Y values as opposed to 2 sets (since we are using 2 LED points), still can't seem to figure out why though? Could there be a bug with the VIs or some additional tweaking that needs to be done to the VI for it to display more than one set of LEDs.

[EduU]

Hey guys, I have a wii too and I want to test it

Could anyone tell me where is the last version of wiimote?

Thanks!

[Kovacs]

@EduU, Try this

http://decibel.ni.com/content/docs/DOC-1353

@Nik1

Well that's odd. I just tried the Acquisition + IR (Event).vi again to be certain and I get 2 LEDs.. even 3 when I use my tv remote along with it.

[Nik1]

@Kovacs

Yeah it is quite odd. The Wiimote doesn't seem to record the X-Y of the 2nd LED or even notice it at times. Tried it with (Acquistion and Event).VI and it's the same problem in both VIs. On a related note, I tried to replace the Wiimote with a Webcam, but it doesn't seem that the NI-IMAQ Webcam files are compatible with Windows 7? - can't see any of the installation files and I've noticed other people having the same problem.

[Kovacs]

Have you tried to run wiimoteTest.exe?

It might help you in pinpointing the problem.