BrianPeek.com

Every stack installs HID devices differently so digging through the registry entries is probably not going to be of much help.

My one and only suggestion is to ensure you have the absolute latest drivers and stack for the device you're using.  Outside that, due to the fact that the Wiimote isn't a 100% compatible bluetooth device, and the fact that bluetooth itself is finicky, you're left with some stacks/adatpers working great and others exhibiting behavior like yours.

I'm using an MSI Starkey with the WIDCOMM stack on Vista x64 and a Dell Truemobile 355 with the MS stack on Vista x86 and both are working great.

I wish I had better information for you but I do not... 

Yep I've seen some strange behavior with the BT stuff.

I've ordered the MSI starkey and will evaluate Widcomm for my application.

Now for one issue I already created a work around: I perform an additional check on the BT device class and don't connect to it if it's an unclassified device. (Bluesoleil API)

Now a second issue is that even when no Wiimotes are connected I still find the PID and VID in the HID device list with the HidD_GetAttributes function. (WiimoteLib)

So that's the big problem at the moment. Does the widcomm stack remove the Wiimote from the HID list when it is disconnected?

Already thanks for your support

 An update on the situation:

I'm now using the widcomm stack and he is indeed mapping the Wiimote in a much cleaner way then BlueSoleil.

So the WiimoteLib works fine with this stack and I strongly advice everybody that has BlueSoleil issues to use the Widcomm stack.

But now I'm trying to use the Widcomm SDK. This ons is much lower level then the BlueSoleil API. In BlueSoleil you look for services and just connect the only one he finds.

The Widcomm sdk is (a lot) trickier. I've managed to inquire the wiimote, find it's address and look for the service. But now I have to set up the connection.

Should I use the L2CAP protocol or something else...

I've been trying to set it up with the L2CAP layer but I'm not succesfull yet...

Any one has experience with this SDK and the Wiimote?

 Regards,

Gerrit

I appear to be having the same problem here. I have the blueSoliel stack which is working 100% using a multitude of C++ Wiimote classes included the one I wrote, so there is nothing wrong with the blue tooth stack its self. However when ever I try to run either Johnny Lee's virtual desktop or the 1.4 version of WiiMoteLib test it fails to connect to the wiimote. The lib correctly enumerates the wiimotes and finds the one connected, it just falls over when trying to retrieve the calibration data. Any ideas? FYI im a complete C# newb, using C# 2008 express so I dont know if there are some HID components missing?

Well let's start with this...

In the lib you wrote, how did you enumerate and connect to the Wiimote?

Thanks for the response, I will get back to you asap, having spent a little time tracking through the code I think it's the library trying to connect to a wiimote that is not connected. I have had 3 Wiimotes connected to the PC, each of those get's enumerated even though they are not currently connected. the lib then tries to connect to them one at a time and throws an exception if it's unable to connect, which unfortunatly it cannot do as the current Wiimote im using is the 3rd in the list. I just need to adjust the code to only throw the exception if the all the wiimotes have been tried...

Are the unconnected Wiimotes still listed in the list of Bluetooth devices?

Also, if you look at the top of the FindWiimote method (v1.4 or higher) you'll see a comment by me where I comment out the DIGCF_PRESENT flag...try throwing it back in and see if that has any impact.

At least in my case, the unconnected wiimotes are still listed and inserted in the Wiimote collection. Therefore exceptions are raised.

I uncommented the DIGCF_PRESENT flag: the connected wiimotes are found, but exceptions are still raised for the unconnected ones.

Bizzare.. I responded to this the other day but my post isn't here.. I think we were having ISP trouble that day though. the DIGCF_PRESENT made everything work for me:).. Ta.

You had exactely the issue I have (exception due to registered unconnected wiimotes) and you solved it by using HIDImports.DIGCF_DEVICEINTERFACE | HIDImports.DIGCF_PRESENT...

Unfortunately, I still run into the issue... Have you any hint? Have you changed also other portions of code?

 

I'll have to dig into this one and see if I can figure out what's going on.  I don't think I've ever seen this happen on my end, but I'll see if I can reproduce it.

 Hi Guys,

I have a similar problem, I get the error "Wiimote not found" but this happen only when I connect more than one wiimotes. [:'(]

For example, if I connect one wiimote, all run fine, but if I connect two wiimote I get the error.

I tryed with widcomm's bluetooth stack, and with Microsoft bluettoth stack but nothing,

I get the same error. However I'm asking to myself if service pack 3 can be the reason of this problem.

I never tryed WiimoteLib_1.5.2_src on service pack 2 but I remember that with previous version of the lib I had no problem with service pack 2 and same problem as above with sp2

Hi everybody, after having tried almost everything to fix the same problem (hours and hours of googling, registery searching etc...), I finally and simply installed widcomm for Xp/Vista. It works !! To try the same, just follow this link : http://www.commentcamarche.net/pilotes/telecharger-50-pilote-bluetooth-widcomm I have Vista 32bits, Broadcom 2045 Bluetooth 2.0 USB Device. But since I tried this solution on other configuration, I suppose this may work with most of the configurations. Have a nice week end. Have wii !