WiimoteConnect UPDATE(0.5.9) now with multi wiimote support!  (Read 177638 times) Print

1 2 3 ... 6 B

thex  May 25, 2008, 02:24:11 PM


I wrote a little app to easyly connect a wiimote to a vista computer using the standard windows vista bluetooth stack.
The app works fine on my DELL D630 running Vista SP1.

find the new version in the new thread

so this thread can be closed

- start app on connect
- glove pie starter
- automatic removal from known devices list
- tray icon (startup send to tray now in settings)
- autoconnect on startup
- multiple wiimote detection

- other BT stacks

I havn't got a second Vista PC here so I need you people to test the app.

Seems to work with Vista and XP with the standard Microsoft bluetooth stack

loaded the pics and the right zip file onto my webspace

//updated Version 0.5


//updated Version 0.5.9 (2008/11/11)
- added multi wiimote support
- fixed app starting bugs


Constructive critics welcome!



UndCon  May 25, 2008, 05:07:20 PM

a nice program - I can test with Vista on my laptop and on my stationary


thex  May 26, 2008, 03:08:58 AM

you deleted the link, not the attachements as i wanted ;) there is a dll missing in the attachement.

i corrected it but i can't find a way to delete an attachement.


//edit everything ok, attachements removed now, was blind ;)


UndCon  May 26, 2008, 06:11:35 AM

Sorry for that -I missunderstood your message...
I'm glad you sorted it out in the end - so I deleted my line there as well...


benpaddlejones  May 26, 2008, 07:26:24 AM

Another step in making this tech more accessible!
Any chance of a XP version???



inio  May 26, 2008, 11:41:33 AM

First: I'd seriously consider figuring out a new Name.  WiimoteConnect or or something.  WiiConnect is awfully close to WiiConnect24, and likely to draw ire from the N.

Beyond that, we should work together.  I'm working on a cross-platform system for accessing Wii Remotes.  You have a platform-specific app that connects to the Wii Remotes and keeps them happy while not in use, then "client" programs connect to that app via localhost TCP sockets.  That way all the really platform-specific stuff is in one place, letting the client be mostly cross-platform (or entirely cross-platform if it uses SDL or the like).  It also lets you keep the Wii Remtoes connected between runs, since connecting them is still a bit annoying.


thex  May 26, 2008, 02:32:33 PM

you're right about the name, ill think about a new one, didn't think that far!

why not work together, have you got some interface definitions or something like this?


inio  May 26, 2008, 08:45:04 PM

you're right about the name, ill think about a new one, didn't think that far!

why not work together, have you got some interface definitions or something like this?

Not sure what you mean by interface definitions.   API?

Yeah, and it's fairly thin.  All of the Wii Remote management logic is pushed into the client app*.  Right now it uses unix-domain sockets instead of TCP sockets, but you can see it here: http://www.soe.ucsc.edu/~Inio/wii.html

It's a zip archive, so you should be able to unpack it in windows.

For the change to TCP, I'm thinking the following will happen:

+ connection host listens on a specific port on the loopback device only (not visible to network, less likely to cause UAC alerts)
+ single connection is used to communicate with all connected Wii Remotes, second byte of packet in either direction indicates which remote it's from (first is length)
+ this would change the API exposed by wiidev_client.h a bit  relating to opening and updating devices, and would require a new enumeration API.

* there's two big reasons for pushing wii remote logic into client app:
1. removes version dependency from client to connection host
2. allows clients to use features as they're discovered


justG01  May 27, 2008, 07:08:38 PM

OK. I downloaded the WiiConnect application and it comes up, connects my Wiimote, but when I try to have it run a program (Grid, finger tracking, etc), nothing happens. What's going on? BTW - I am using Vista on an HP Pavillion


thex  May 29, 2008, 02:56:58 AM

ok, what is the path in the textbox? can you paste it here?

does the bottom of the dialog become green and says connected?

after doing the connecting procedure the program waits a few seconds and thenn checks if the wii is connected after that it launches the programm, maybe the period is to short and when i check if it is connected it isn't jet so the program isn't gonna start.

but i just got an idea how to fix this, i aint got my wiimote with me but i gonna wite it now and upload another version. i can't test it with my wiimote so you have to.



Omri  May 29, 2008, 01:19:25 PM

Hey Thex, I've tried to use your tool to connect to the wii but I didn't succeed.
I am using Windows Vista 64bit on HP tx2120 with an internal bluetooth device.

I did the following:
  • Extracted both your program and the whiteboard app into the same directory with sub folders.
  • Opened your program and hit connect - didn't work
  • Added the wii remote using Bluetooth Devices (where it said it is connected but the wii continued flashing all the lights)
  • Added the link to the whiteboard application in your program
  • Tried to connect again - wasen't successful

Hope this information helps you, and I am looking forward to hearing from you as I really want to start using the Wiimote for my classes.


thex  May 29, 2008, 08:14:13 PM

hm, is there any error or does it say "connected" but just the whiteboard doesnt work?

as long as no programm is startet that uses the wiimote countinious blinking means the wiimote is connected properly, if there is no connection the wiimote will stop flashing after some 20 seconds or so.

johnnys whiteboard is using the wiimote lib you can download the lib and the package contains a test tool, if jou get a connection with that one something other goes wrong.

also using the built in bt doesn't necessarily mean you are using the ms bluetooth stack, som vendors bundle their products with widcom or similar stacks... see attachement, thats what you need (sorry only in german)

also i can't really test x64 compatibility



Omri  May 30, 2008, 02:41:54 AM

Thex, thank you, I did check in the device manager and I do not have the ms stack, but I downloaded the Wiimote Lib and used the test program and it connected with the wii wonderfully.

But even though after the wii has responded to the Wiimote Lib test tool the whiteboard is not working yet.

Sorry I am posting this in this topic but I still plan to beta test your program as well after I manage to make everything work perfectly.


thex  May 30, 2008, 01:20:41 PM

no prob, hope you go on testing the app because i'm not sure if it eventually works with other bt stacks too.

i just found out something that might be your problem!
i tried to use wiinremote with my wiimote but it didnt work. it somehow messed up my wiimote. the connection is established just as before but when i start the whiteboard it says "no wiimote found". to make it work again you have to take out the batteries and then put them back in place and then reconnect it.

i'm working on the code right now i already programmed a new way to determine if the wiimote is connected.
gonna upload an update later ;)



thex  June 04, 2008, 04:10:14 AM

new update:
- now check if wiimote is connected works better
- autoclose added
- little bugs fixed

download it here: