EvoSapien.com

[traynor]

Here is a link to screen shots:

http://www.flickr.com/photos/14246042@N07/2224070643/

http://www.flickr.com/photos/14246042@N07/2224862188/

Please let me know if you need any more information.

Regards,
Traynor

[roschler]

Traynor,

You need to run the test I mentioned a couple of posts ago:

[traynor]

http://www.flickr.com/photos/14246042@N07/2224178945/

http://www.flickr.com/photos/14246042@N07/2224178873/

http://www.flickr.com/photos/14246042@N07/2224178761/

the hid reader screen shot is the same as the one posted before.\

Regards,
Traynor

[roschler]

traynor,

The screen shot you show of the HID Reader doesn't have the "Show Reports" box checked.

Try this and in this specific order:

* Make sure you're WiiMote is properly paired (activated). Especially make sure you click on the checkbox next to the WiiMote icon found in the final screen that appears during the pairing process (activation), if it is not already checked.

* Go to the HID Reader screen

* Check the box that says "Show Reports"

* Go to the WiiMote Interface screen.

* Click on the button that says "Force Motion Reports"

* While at the same screen, click on some buttons on the WiiMote.

* Then go back to the HID Reader screen and take a screenshot.

I'm trying to see if there are any signs of life from the WiiMote at all.

[traynor]

Followed the steps outlined.

http://www.flickr.com/photos/14246042@N07/2224666857/


Regards,
Thomas

[roschler]

That's unfortunate. When you pressed "Force Motion Reports" we should have at least seen a write operation to the WiiMote take place. I'll have to think about what else to try so it will be a few days.

If you're brave enough, there's a trial version of the Blue Soleil drivers you can try. I haven't tried them myself though:

http://www.bluesoleil.com/download/

[traynor]

Installed new drivers. No Luck...


Regards,
Traynor

[roschler]

Ok. Over the next few days I'll be creating some diagnostic code to run some tests on your and Wewell's systems. I'll post a message when it's ready.

One other screen shot I'd like to see is what you get when you right-click on the Bluetooth System tray icon and click on "View Devices In Range".

BTW, the Blue Soleil drivers are supposed to "auto-pair(connect)" with the WiMote. Did you find that to be true?

[traynor]

http://www.flickr.com/photos/14246042@N07/2226316715/


http://www.flickr.com/photos/14246042@N07/2226316477/

Do you think that the highlighted item is something that windows xp sp2 is loading drivers. These two item have different pid's. Could it be a problem with the microsoft bluetooth drivers are getting loaded anyway. There are quite a few other articles about problems with BT and sp2?

The other driver I could not get them to auto-pair at all. It did "see" the will remote at all.

Regards,
Traynor

[roschler]

traynor,

The first link you posted goes to a screenshot of the forum message, not the "devices in range" screen. This screen has the title "Entire Bluetooth Neighborhood".

Re: Device Manager entries

I have the same driver entries as you do for the Device Manager so I think that's OK.

Re: concerns

My two main concerns right now are that all your device services are listed as "secure connection required" in the provided services screen. That shouldn't matter since the WiiMote connection doesn't use any of the services, but it's different from my system.

Also, you have two entries in the HID Reader screen, one of which is an unnamed HID device. That's my other concern. Until I wrote the diagnostic code I won't be able to discern much more.

When you get a chance do post the "Devices In Range" screen".

[traynor]

http://www.flickr.com/photos/14246042@N07/2227224524/


http://www.flickr.com/photos/14246042@N07/2226433301/

I think maybe the hid reader is getting this id from here.(0000)


Regards,
Traynor

[wewell]

Robert,

Finally success. The problem was my Bluetooth stack which came with my Kensington USB 2.0 model 33348 dongle. upon research, I found that the latest shipping Widcomm Bluetooth stack frequently does not work with the Wiimote. It was recommended that I go to ftp://ftp.kensington.com/BT/kensingtonBTW%204.0.1.2400.zip and download this older stack which tested well with the Wiimote. This too, is a Widcomm Stack and it contains a Broadcom driver, for the dongle, which is version .1400. My current Broadcom driver was version .1700

I deleted my current Bluetooth software, and downloaded this older version of the Widcomm Bluetooth Stack and installed. Robodance now recognizes the Wiimote and i'm having a blast checking it out. it's working just fine.

I got my information from the following sight; www.wiili.org/index.php/Compatible_Bluetooth_Devices which provides excellent information on internal and external compatible Bluetooth devices that have been tested with the Wiimote. Hopefully, this will be helpful to some of you.

Robert, thank you for your help and patience with this problem.

[roschler]

Wewell,

No, thank you! You just saved me a bunch of time.

Well I'm both happy and worried. Did they happen to say if there was a way to fix things for the newer stacks? Or that the newer stacks just won't work with the WiiMote?

It looks like I'm destined for a bunch of Bluetooth forum hops to investigate this. I'll be sending out a message to the Robodance list telling people about what you found.

That makes sense because although I am running a slightly newer stack on one system, they're all pretty much older WIDCOMM stacks.

[traynor]

I went out and bought the the same usb adapter 2.0 (Kensington) that wewell had suggested. I loaded the same drivers, and everything works well now.

Regards,
Traynor

P.S. Thanks to everyone for this help. I am really enjoying it.

[roschler]

Traynor,

I'm so happy to hear that! That confirms the issue and I'm glad that now we have a solution thanks to Wewell.