No Wiimotes found in HID device list

[williamlweaver]

We are working on a new project based on the "LabVIEW interface to a Wii Remote ("Wiimote")" code available here: https://decibel.ni.com/content/docs/DOC-1353

We are using a new Wii MotionPlus remote with an older Bluetooth Dongle on Windows 7. The Wiimote pairs correctly with Win7 using the Add Device screen.

When we try to run the "WiimoteTest.exe" program provided in the WiimotLib_1.7 zip package, we receive the following error.

"No Wiimotes found in HID device list."

We've searched on this error but only could find links that are years and years old.

Anyone have advice for a modern configuration using Windows 7?

[MoviJOHN]

Either the new Wiimotes are not compatible with the old software, or you need to try a different BlueTooth dongle.  Some work, and others do not.  Even if the OS can see them.

[williamlweaver]

Thanks for the quick response MoviJOHN...

Rather than hit or miss with purchasing older Wii Remotes and finding an assortment of Bluetooth dongles to try, I wonder if it is worth our team's time to build a 2013 version of the LabVIEW driver for the Wii MotionPlus Remotes and any Windows 7 supported Bluetooth dongle...

Does anyone have any thoughts on why this project hasn't been updated in the past few years to keep up with the OS and LabVIEW 2012/2013?

Back in the day our research group created LabVIEW drivers for the Bluetooth LEGO Mindstorms robotics kit before the "official" toolkit was released.

I would be willing to dedicate our team's time but it's a bit of a let down after weeks of development to find out that others were concurently inventing the "Official" wheel.

Thoughts?

[MoviJOHN]

As with most things of this nature, it probably never acheived wide acceptance/use.  I used the toolkit for a while, but never found it to be very stable.

[williamlweaver]

So we have been tooling around with the Nintendo MotionPlus Remote, our new KINIVO WIDCOMM Bluetooth 4.0 dongle and the WimoteLib1.8 library from Brian Peek.

Same error persists...  "No Wiimotes found in HID device list".

We had a look at the source code in WimoteLIB1.8 and we found:

// VID = Nintendo, PID = Wiimote
private const int VID = 0x057e;
private const int PID = 0x0306;

And looking at our Bluetooth device list after pairing the MotionPlus Remote:

BTHENUM\{00001124-0000-1000-8000-00805f9b34fb}_VID&0002057e_PID&0330

...under "Hardware Ids" property of the Bluetooth HID Device.

I'm guessing the code is looking for a PID of 0x0306 and the MotionPlus has a PID of 0x0330

If we were to get a hold of a copy of C#, change the PID, and compile the WiimoteLib.dll with the new value...

Any advice on whether or not this might work? 

[williamlweaver]

[UPDATE]

Sorry for replying to my own post.

1. Installed Visual Studio 2013 Express
2. Modified PID = 0x0330
3. Built a new version of the WiimoteLIB.dll (1.8).
4. Placed the newest WiimoteLIB version in a fresh directory.
5. New vi.
6. Added a .NET Constructor Node and linked it to the WiimoteLIB.dll.
7. Connected Reference into a .NET Invoke Node and set the method to "Connect".
8. Ran vi.

Same error as before:

Still working on a connection with the a new Wii MotionPlus Remote...

[williamlweaver]

[UPDATE]

Thanks to http://wiibrew.org/wiki/Wiimote, we discovered that we were not correctly connecting the Wii Motion Plus via Bluetooth.

Even though the Wii Motion Plus permits Bluetooth discovery and pairing in Windows 7 by pressing the "1" and "2" buttons on the remote simultaneously (like with the original Wii Remote), after the 4 LEDs flash for a bit, the Wii Remote goes dark. Windows does not report a lost link, but the Wii Remote is no-longer powered and linked.

After linking the Wii Motion Plus Remote via Bluetooth using the Red "SYNC" button on the back of the remote, the 4 LEDs continue to flash after pairing the Wii Remote with Windows 7.

We modified the PID to = 0x0330 in the 1.7 version of the WiimoteLIB.dll as described in the previous post and built the .dll using 2013 Visual Studio Express.

After running the WiimoteTest.exe, the Microsoft .NET Framework throws a host of exceptions. The screen capture below does not show all of the information, only the top of the list:

After pressing continue, the Multiple Wiimote Tester UI loads and is displayed correctly, however, there are no readings from the Wii Remote displayed.

When the buttons are pressed on the Wii Remote, the check marks are correctly displayed (such as the A & B buttons, et. al.) and the Rumble actuates when the Rumble check box is clicked with the mouse.

No accelerometer values. No IR values. No Battery level.

Will continue debugging for the Wii Motion Plus remote.  

At least we are talking with the remote now...  

[williamlweaver]

[UPDATE]

It looks like the "old" TRENDNet TBW-101UB Bluetooth Dongle works just as well as the newer Kinivo BTD-400.

Our problem of no connectivity was due to pressing the "1 & 2" buttons simultaneously to add the device instead of pressing the red SYNC button on the back of the remote.

Both the TBW-101UB and the BTD-400 cause the WiimoteLib 1.7 TEST program to throw the following exceptions:

See the end of this message for details on invoking

just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************

WiimoteLib.WiimoteException: Error reading data from Wiimote...is it connected?

   at WiimoteLib.Wiimote.ReadData(Int32 address, Int16 size) in c:\Users\weaver\Desktop\WiimoteLib_1.7_src\WiimoteCS\WiimoteLib\Wiimote.cs:line 1196

   at WiimoteLib.Wiimote.ReadWiimoteCalibration() in c:\Users\weaver\Desktop\WiimoteLib_1.7_src\WiimoteCS\WiimoteLib\Wiimote.cs:line 933

   at WiimoteLib.Wiimote.OpenWiimoteDeviceHandle(String devicePath) in c:\Users\weaver\Desktop\WiimoteLib_1.7_src\WiimoteCS\WiimoteLib\Wiimote.cs:line 259

   at WiimoteLib.Wiimote.Connect() in c:\Users\weaver\Desktop\WiimoteLib_1.7_src\WiimoteCS\WiimoteLib\Wiimote.cs:line 136

   at WiimoteTest.MultipleWiimoteForm.MultipleWiimoteForm_Load(Object sender, EventArgs e) in c:\Users\weaver\Desktop\WiimoteLib_1.7_src\WiimoteCS\WiimoteTest\MultipleWiimoteForm.cs:line 59

   at System.Windows.Forms.Form.OnLoad(EventArgs e)

   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)

   at System.Windows.Forms.Control.CreateControl()

   at System.Windows.Forms.Control.WmShowWindow(Message& m)

   at System.Windows.Forms.Control.WndProc(Message& m)

   at System.Windows.Forms.Form.WndProc(Message& m)

   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************

mscorlib

    Assembly Version: 4.0.0.0

    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL

    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll

----------------------------------------

WiimoteTest

    Assembly Version: 1.5.2.0

    Win32 Version: 1.5.2.0

    CodeBase: file:///C:/Users/weaver/SkyDrive/GoogleDrive/APEX/04-GhostRider/WiimoteLib_1.7_src/WiimoteCS/Wiimote...

----------------------------------------

System.Windows.Forms

    Assembly Version: 4.0.0.0

    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e0...

----------------------------------------

System.Drawing

    Assembly Version: 4.0.0.0

    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/Sys...

----------------------------------------

System

    Assembly Version: 4.0.0.0

    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll

----------------------------------------

System.Configuration

    Assembly Version: 4.0.0.0

    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a...

----------------------------------------

System.Xml

    Assembly Version: 4.0.0.0

    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System....

----------------------------------------

WiimoteLib

    Assembly Version: 1.7.0.0

    Win32 Version: 1.7.0.0

    CodeBase: file:///C:/Users/weaver/SkyDrive/GoogleDrive/APEX/04-GhostRider/WiimoteLib_1.7_src/WiimoteCS/Wiimote...

----------------------------------------

************** JIT Debugging **************

To enable just-in-time (JIT) debugging, the .config file for this

application or computer (machine.config) must have the

jitDebugging value set in the system.windows.forms section.

The application must also be compiled with debugging

enabled.

For example:

<configuration>

    <system.windows.forms jitDebugging="true" />

</configuration>

When JIT debugging is enabled, any unhandled exception

will be sent to the JIT debugger registered on the computer

rather than be handled by this dialog box.

[CapnPez]

Hello, I am also trying to connect a newer Wiimote (used with a Wii U) to a Windows 7 machine, but have not found a way to do so yet. Have you had any further progress/success? I'm afraid my knowledge of building drivers is quite limited. Any help qould be greatly appreciated.

Thanks,

Pete

[williamlweaver]

Hi CapnPez,

Unfortunately, we are an undergraduate institution and I only have my senior research students for one to two semesters and then I lose them to graduation. We needed to move on with the research project, so we shelved the Wii Motion+ remotes for now with the hope that when a future project needs them, we can use a solution that has been developed by another lab.

We are just started a new Fall cycle of projects, so perhaps we will return to the Wii Motion+ as our students define their projects.

Best of luck!

-Bill  =]