So I was using the library and I was happy with it, when out of the blue it starts throwing exceptions after it pairs with a Wiimote. I think maybe it’s my code, so I try the example app and it still happens. I didn’t even reboot between when it was working perfectly fine and when not, and I didn’t do anything bluetooth or wiimote related to affected it, so I’m stumped.

The IDeviceProvider is discovering…
A device has been found.
Connecting to the device…

Unhandled Exception: System.InvalidOperationException: Received an output report
!
at WiiDeviceLibrary.ReportWiimote.ParseReport(Byte[] report)
at WiiDeviceLibrary.ReportDevice.OnReportReceived(Byte[] report)
at WiiDeviceLibrary.ReportDevice.OnReadReport(IAsyncResult result)
at System.Runtime.Remoting.Messaging.AsyncResult.SyncProcessMessage(IMessage
msg)
at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMe
ssage msg, IMessageSink replySink)
at System.Runtime.Remoting.Proxies.AgileAsyncWorkerItem.DoAsyncCall()
at System.Runtime.Remoting.Proxies.AgileAsyncWorkerItem.ThreadPoolCallBack(Ob
ject o)
at System.Threading._ThreadPoolWaitCallback.WaitCallback_Context(Object state
)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, C
ontextCallback callback, Object state)
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_Thre
adPoolWaitCallback tpWaitCallBack)
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)

In my own code the exception is thrown right after I call IDeviceProvider.Connect with the Wiimote’s IDeviceInfo.

Tried pairing the Wiimote with a Wii and then back to the PC, tried popping the Wiimote batteries, tried unplugging and replugging my bluetooth dongle, tried restarting the Windows Bluetooth helper service… nothing.

Any help would be appreciated. This is a great library you guys have made here.

I’ve solved the mystery. Apparently if I have one of my USB hubs connected… it doesn’t matter if the bluetooth dongle is plugged into it or elsewhere… the exception occurs. Unplug it and everything works.

Actually it seems to be happening randomly now whenever I SetReportingMode… maybe it’ll crash, maybe not! Who knows!

Hi Dan,

First: sorry for the wait, we should really have some sort of notification when people comment on this site.

It really surprised me that you ran across the ‘Received an output report!’. When I added that exception I presumed no one was ever going to see that, because it would be almost impossible. I think one of the usb-devices (or hub) was registered as HID-device with the same Id’s as the Wii-devices have. WiiDeviceLibrary thought one of those devices was a Wii-device and tried to connect. The Wiimote normally sends and receives ‘reports’ and identifies the report-type with a single byte. This byte is checked by WiiDeviceLibrary. If it receives a byte that corresponds with a report-type that would normally be SENT to the Wiimote instead of RECEIVED it raises the exception you described.
I might just remove the exception and just try to disconnect the device, since raising an exception on a thread that is not managed by the user could cause great annoyances.

The TimeoutException is raised for WriteMemory and ReadMemory when there is no resulting-report sent back to confirm the operation succeeded (or failed) within 5 seconds.
We tested and covered calling Wiimote-methods directly from the Update-eventhandler. This should be no problem.
Though, invoking a call on the GUI-thread and at the same time blocking the Update-thread (which is what the ‘Invoke’ method does) -could- result in problems.

I can’t really clearly state where the problem lies without some more information. It would be great if you could send us a portion of your code so we can analyse, test and debug using that.
You can email me or Maato at info@softwarebakery.com.

That is an interesting usecase. You might be able to redirect references from libbluetooth.so.3 to libbluetooth.so.2 by using Mono’s configuration in your app.exe.config. If you try this, be sure to use WiiDeviceLibrary.Bluetooth.Bluez.BluezDeviceProvider directly instead of DeviceProviderRegistry.
We’ll try it here later this week if mono’s redirection will work.

Don’t forget to also thank Maato , he doesn’t comment much but did a lot of work and testing too, especially BlueZ support.

I’ve been looking at Motion Plus support, though I can’t say it’s implemented in a few minutes in the current framework. At the moment school takes a lot of time, which doesn’t give me enough to setup the test-environment and implement the support. It would be a great addition though!

To not forget the feature I’ve added it to the issue-tracker: http://code.google.com/p/wiidevicelibrary/issues/detail?id=13 . If there are any other requests (or issues) please also add it to the issue-tracker.