BrianPeek.com

Hi,

I'm using the Rocketfish "Bluetooth 2.0 EDR Class II Wireless USB Adapter" and trying to run the test program. My Wiimote is connected and shows up under "My Bluetooth Places\Entire Bluetooth Neighborhood"  as "Nintendo RVL-CNT-01" with the little green arrows. The LEDs blink. When I try and run the sample program, i get "Wiimote not found". It dies on doing the vendor/product ID comparisons. They are both set to -2 it seems for the only device that makes it to that if statement. Any ideas on what I can try? I can't find anything Nintendo-related in the registry, thought info on devices might be in there.

 
Thanks!
 

Update:

 

I found it in my registry, under HKLM\System\CurrentControlSet\Enum\some crazy guid\HID_KEYBOARD\1&30ee4ad&1&2964a21ab1700

 
The "HardwareID" key has 2 values apparently, like so:

{95C7A0A0-3094-11D7-A202-00508B9D7D5A}\HID_KEYBOARD
{95C7A0A0-3094-11D7-A202-00508B9D7D5A}\{00001124-0000-1000-8000-00805f9b34fb}&VID_057E&PID_0306

The second one has the right VID and PID... Am i suposed to have 2 entries here? Seems odd 

i figured it out... I had to go into the Device Manager and disable 2 of the 3 HID devices that were installed. There was "Bluetooth Remove Control" and 2 "Bluetooth Virtual HID Device" entries. I disabled the remote control and the Virtual device that wasn't nintendo and now the sample program works.

Anonymous:

Hi,

I'm using the Rocketfish "Bluetooth 2.0 EDR Class II Wireless USB Adapter" and trying to run the test program. My Wiimote is connected and shows up under "My Bluetooth Places\Entire Bluetooth Neighborhood"  as "Nintendo RVL-CNT-01" with the little green arrows. The LEDs blink. When I try and run the sample program, i get "Wiimote not found". It dies on doing the vendor/product ID comparisons. They are both set to -2 it seems for the only device that makes it to that if statement. Any ideas on what I can try? I can't find anything Nintendo-related in the registry, thought info on devices might be in there.

Thanks!
 

Please check the reg entries mentioned above and see if the device is listed there.  Also, what OS are you running?

Ok I would really like some help with this.

I had to reinstall my PC (I am using Vista) and the RocketFish USB dongle and everything was working before but now its not working. I am ending up in the exact same spot. It cannot find it although I have added the device, Widcomm shows it connected etc.

Can we make the HID detection a little more robust somehow?

Could you explain further what it is exactly looking for in the HID? I am looking in Device Manager and I see only 2 Bluetooth related items and they are:

Bluetooth Remote Control
Bluetooth Virtual HID Keyboard

Is the virtual keyboard the item you try and communicate to for the WiiMote? Is it possible the VID and PID don't match?

Any suggestions would be great. I don't think its too good to be removing devices and editting registry for this lib to find the WiiMote. If we could make it more robust that would be great. I am not familiar with Bluetooth and HID so any help would be greatly appreciated.

Very frustrating!

Thanks and take care.

This is the joy of Bluetooth.  The Wiimote is a Bluetooth device, but it was only ever intended to connect to a Wii.  So, it's not necessarily 100% standard.  When connected to Windows, on top of the Wiimote's lack of standards, we have the lack of Bluetooth standards.  Each stack installs devices and interacts with them in a different way.

The only way to connect to the device in a generic way is to use the HID stuff since the Wiimote shows up as a HID device.

So.  In terms of making it more robust, I don't know of any way in which to do that.  The HID calls are going to show any device which the HID layer says is available.  The code runs through all of those devices and compares the vendor ID and product ID to the Wiimote's.  If they don't match, it's either because a) it's not a Wiimote, or b) the Bluetooth stack didn't install the device properly.

Can you trace through the code and see  how many devices are found and what the detail path is for each?  You should automatically get that in the output window if you're running from the IDE.

Thanks for the help.

I'm not sure if this is what you were mentioning but here is the debug output:

0 \\?\hid#hidavcontrol#2&1d473603&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 0
1 \\?\hid#hidavcontrol#2&1d473603&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 0
2 \\?\hid#hidavcontrol#2&34ba8cf0&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 0
3 \\?\hid#hidavcontrol#2&5d3df16&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 0
4 \\?\hid#hid_keyboard#2&126e67e1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 0
5 \\?\hid#hid_mouse#2&f82cb3b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 0
6 \\?\hid#vid_045e&pid_008c&col01#6&e1f46da&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 0
7 \\?\hid#vid_045e&pid_008c&col02#6&e1f46da&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030} 0
8 \\?\hid#vid_045e&pid_008c&col03#6&e1f46da&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030} 0
9 \\?\hid#vid_045e&pid_028e&ig_00#7&2f189b0c&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 0
10 \\?\hid#vid_045e&pid_028e&ig_08#7&4b8ffce&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 0
11 \\?\hid#vid_045e&pid_0719&ig_00#7&2c2d1517&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 0
12 \\?\hid#vid_046d&pid_c30a&mi_00#7&15f9132e&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 0
13 \\?\hid#vid_046d&pid_c30a&mi_01&col01#7&39d050f0&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 0
14 \\?\hid#vid_046d&pid_c30a&mi_01&col02#7&39d050f0&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030} 0
15 \\?\hid#vid_046d&pid_c30a&mi_01&col03#7&39d050f0&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030} 0
16 \\?\hid#vid_046d&pid_c50e#6&b44dbe4&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 0
17 \\?\hid#vid_0738&pid_4426#7&1098c8bf&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 0
18 \\?\hid#vid_0a5c&pid_4502#7&233f099f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 0
19 \\?\hid#vid_0a5c&pid_4502#7&9256a4d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 0
20 \\?\hid#vid_0a5c&pid_4503#7&178b6d40&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 0
21 \\?\hid#vid_0a5c&pid_4503#7&335271df&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 0

So what device should it be looking for? What type of device does it typically show up as in device manager for you guys? 

 It seems none of them match the VID/PID?

Thanks and take care.

It looks like you have a variety of HID devices installed, but none of them are the Wiimote.  It appears your stack has not installed the Wiimote correctly for whatever reason.  What adapter and stack are you using?

I have a RocketFish bluetooth adapter. I was using the new WIDCOMM for Vista. I decided to downgrade to the XP version of WIDCOMM and it seems to be working again. Very odd.

I really wish the bluetooth scenario in Windows was much more common API.

Bizarre but glad you got it working.  Thanks for posting the resolution!  
 

There seems maybe to be some kind of bug in the WIDCOMM BT stack or the way it installs.  I recently bought a broadcom based BT chipset device assuming that would be best for communicating with the broadcom based chip of the wiimote and all seemed to go well at first.  From the beginning I was able detect and connect with the wiimote on a device level however none of the BT enabled programs I found could detect its presence.

After alot of reconnects and finally a bit of watching the device manager I realized it was detecting the wiimote as a Bluetooth Virtual HID Keyboard

After making this connection I selected that device and chose Uninstall - then disabled and reenabled my BT Dongle.

When the device reinitialized it asked to reinstall the BT Virt HID Kbd driver, which I allowed.  However this time it also added HID-compliant game controller - something which did not previously exist.  As soon as I saw this component I became very happy - my feeling was justified - when I reinitialized my connection with the wiimote it correctly detected and the WiimoteTest.exe was able to see the device.

I don't really know the cause of the problem but it was extremely frustrating to troubleshoot - I hope this solution works for anyone else having problems like this.  One thing I can tell though is that the problem is not caused in any way by the WiimoteLib.. which I am looking forward to playing with!

I was getting the same VID/PID problem. I did the Bluetooth Virtual HID Keyboard uninstall. Then reinstall while having my wiimote in discovery mode and it added the same HID-compliant game controller and all works correctly since. Many thanks for the trick!! By the way, I got a TrendNet TBW-101UB USB BLuetooth adapter.

 Hello,

 I have a similar problem but I'm not able to resolve it. I only have a temporary solution.

In the past everything was working fine and I had no issue connecting the Wii through the library.

I tried to install the same setup on another PC and was not able to get a connecting through the soft.

Then I tried to reproduce on my pc and guess what I was able to do so...

But of course now I'm completely screwed.

Info: DECTEL bluetooth dongle + BLUESOLEIL stack (which both worked fine in the past)

When I uninstall the BT dongle and the HID devices and then scan for devices then everything will be installed again and everything will work fine.

Now when I reboot my PC I'm again not able to connect the Wii through the library. If I repeat the uninstall/install procedure everything will be back in to place.

Info1: I have 2 HID devices when the Wiimote is connected.

        Device 1 Bluetooth HID unclassfied device (+HID-compliant game controller which seems to be linked to the device)

        Device 2 Bluetooth HID Joystick (+HID-compliant game controller also linked to this device)

        When I remove the 2 HID devices and scan for hardware changes the 2 devices are again installed (without bluetooth connection to the Wiimote). Connection to Wiimote through library fails.

        When I remove the 2 HID devices + BT device and scan for hardware changes the BT device is again installed and only 1 HID device is installed again (the unclassified device).

        If I now connect the Wiimote with Bluesoleil the device (joystick device) will be added in the HID list and everything will work fine.

Info2: Even when the Wiimote is connected I can't find the PID_0306 or VID_057E string in the registry. I've exported the complete registry and those strings are no where to be found.

        How is the WiiLib able to find the Wiimote without these entries ?

Problem is we want to use this for production tooling so I really need to get to the bottom of this because the problem will occur again.

I'm completly aware that this has nothing to do with the library it self but with the registration as a HID device.  

Any ideas how to solve this? Or some info on the registry entries?

Thanks a lot

Greets Zjeriet 

The next step in finding the issue...

 Some additional info:

 I've been snooping around in the registry and can find the entries in HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Enum

I have a device under this directory between brackets {} which is definitely linked to the Wiimote and then under the HID dir I find back 2

subdirs BLUEOOTHHID and BTHIDJOYSTK these both contain entries to the Wiimote. 

My problem started when I started to play with a second remote. Not simultaneously (always only one remote connected)

I believe that when I take another remote (which address is lower then the first remote) connect it and afterwards reconnect the other one.

The first remote will not work anymore due to the order in the registry. Is this BlueSoleil specific?

Brian in some other thread you adviced a user to use the standard windows stack. How do I find it? And does it have an API or something like that to automatically connect from an application?

And are you sure it will not have the same issue as my current problem?

 

Regards,

 

Gerrit