BrianPeek.com

Hi everyone, I've got a real big error. I connect my Wiimote with a motorola stick and try to start the Wiimote Test or other Wiimote Programms, but everytime my PC shutdown without any warning. If I unplug the Wiimote, I only get an error, that says my Wiimote isn't connected. I use Blue Soleil 5.2.227.1 for connecting. Can anybody help me? Mfg, Martek

I am having the same problem... I have tried two different dongals and both BlueSoleil and Widcomm BlueSoleil allows me to connect to the wiimote and then reboots when I launch the program. WidComm doesn't seem to let me connect the wiimote - it asks for the security id (and when I leave it blank it complains) Any help would be appreciated.

For WIDCOMM, go to the following link and update to the latest drivers/stack and it should have an option to skip the security step:

http://www.broadcom.com/products/bluetooth_update.php

Hi everyone, i have the same problem to, i am using BlueSoleil 6.0.223.0 on Windows Server 2008, the 5.x driver was unable to connect to my wiimote and the WiimoteTest.exe was unable to found any wiimotes with the driver version that came with the dongle ( 3.6 ), the 3.6 was just perfect on XP.

I am trying to debug the Lib and i found one interesting thing:

When i was debugging the app, that aways hang in MultipleWiimoteForm_Load{ wm.Connect(); }, i stepped in every function call of the WiimoteLib and nothing happened, after exiting Connect() i played the app ( continuous operation mode, no steps ) and then it hanged. My knowledge of programing isn't so good so i can only guess that the Library is trying to poll data that is not yet avaliable, making the system crash.

It seems everyone that's having this issue is using BlueSoleil.  Anyone managed to track down the exact line it's crashing on?

I don't have a dongle that uses BlueSoleil so I have no way of reproducing this...

 Debugging the application the problem is in:

wm.SetReportType(InputReport.IRAccel, true); --> SetReportType(type, IRSensitivity.Maximum, continuous); --> EnableIR(IRMode.Extended, irSensitivity); --> WriteData(REGISTER_IR, 0x08); --> WriteData(address, 1, new byte[ { data }); --> WriteReport(); --> mStream.Write(mBuff, 0, REPORT_LENGTH);

But one odd thing keeps happening: if i just play the application, with the Wiimote connected, the wm.Connect(); raises a "Error reading data from Wiimote...is it connected?"exception. If i put a breakpoint before this function and step over it, it succeeds. I've put a simple log before every function call in the WiimoteLib to tell me what function is the problem, in wm.SetReportType(), if i step over it, my computer crashes(none of the internal functions are called), if i step-in this function, it crashes in mStream.Write(mBuff, 0, REPORT_LENGTH);

 Hi again, found new stuff, i have monitored "mBuff" in WriteReport, these are all the values in mBuff:

 //connect

23 0 0 0 22 0 7 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

21 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

//inside set report

19 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

26 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

22 4 176 0 48 1 8 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

22 4 176 0 0 9 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

22 4 176 0 26 2 64 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

22 4 176 0 51 1 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

22 4 176 0 48 1 8 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

18 4 51 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

//Set Leds

17 16 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

 

The values starting with "22 4 176 0" crashes the system.

After skipping all mStream.Write calls with these value, the application runs normally.

 

i hope i have helped.

More information:  after a system reboot, the application doesn't show the wiimote IR and Acceleration information anymore, buttons are ok and set tumble and leds still work.

With the nunchuck plugged the Library raises an "Error Reading data" exeption, plug it after the initialization also.

 Errata: the crash code is actually 22 4 , the 176 value changed to 164 with the Nunchuk.

To everyone that's posted here with the BSOD issue, please take a look at this post and follow through to the survey if it applies to you.  Thanks!

Well, after a few responses on the survey, it appears everyone is running BlueSoleil.  Someone also pointed me at a few links on www.wiimoteproject.org and it appears that BlueSoleil is actually aware of the issue and working on a fix.

So, I guess hang tight until BS gets a patch out to fix this issue...