Wiimote Project

Hi Thex,

"I will add the "autostart with windows" option, it's not a big thing. I don't know why you want that message go away as it is helpfull if you only got that 20 seconds to sync. Maybe I'll add an option to disable it."

---- I want it be removed because if I get my wiimote already learned, and tape down the 1 and 2 buttons permanently, the wiimote stays in sync mode permanently (the power is not a problem as I'm powering it with a AC power supply), so all I need to do now is just start my pc, and click on your wiiconnect, then wait the wiimote to be connected automatically, it's wonderful! when you add the autostart feature, it is completely automatic, need no human intervention at all, isn't it?

Thanks for making the great software and listening to us!

Hi thex and other experts!
I find a terrible problem!
When the wiimote connect to the PC(i use windows bluetooth stack and wiimoteconnect0.6),and the smoothboard(the version is Smoothboard_1_0_Setup) have already normal running,i cut the wiimote power,the smoothboard will makes error,and show a menu(detail in attach files),and when i click a ok of this menu,the PC will suddenly become Blue Screen,and restart at once.
But,When the wiimote connect to the PC,and the smoothboard have not running,i cut the wiimote power,everything is ok.
Why is there such a phenomenon?
what a happen?
i guess the problem is smoothboard.not is wiimoteconnect0.6
please give me a answer,thank you very much!

Hey,
I already expierienced this behaviour except the bluescreen. It's a problem with the client apps, not with wiimoteconnect. They don't handle a wiimote ,connected while their software is running, right.

The workaround is to use my app to start the client software and check the autokill option. as soon as a wiimote is connected my software will start the client app and if there is no wiimote connected it will kill the app and start it again when the wiimote is connected again.

thex

Hi Thex,

Thanks for your great releases for WiimoteConnect.

I have just donated to your project.
Although I am using Bluesoleil, my father solely uses your application. It works well for him.

Regarding the error, it looks like the error is caused by Brian Peek's WiimoteLib component. I will see whether I can handle the issue in the next release.

Regards,
Boon Jin

Hello Thex,
Carsten wrote:

Hi thex,

Any change that you will publish the code under an open source license?

Our schools are also interested to get an answer to Carstens question.
Would it be possible to give us an answer?
Kind regards,
Dirk

hi Thex,

I've had a little issue with the V0.60 on my VISTA laptop, after the wiimote is learnt by V0.60, and when I connect to the wiimote, sometimes it says "no wiimote found" when the wiimote is actually already found and added, so it reports false error message.

Could this be my computer or the software? I guess it has something to do with the software because the v0.59 has always been correct on the pop up message, when it's connected it never says "no wiimote found".

Thank you for looking into this!

Is there any way to get the program to open more than one application when it starts up?

For example, I would like it to start smoothboard and Linkystivity presenter. Can I put a comma or semicolon between file paths?

Thanks,
Tyler

For everyone who wants to use wiimoteconnect AND the widcomm stack there is a simple solution:
1.use the taskmanager to kill bttray.exe
2.remove the bluetoothdevice from the list in the devicemanager(if the driver is not certified copy the hardware_id before(follow the tutorial mentioned in the first post))
3.replug the device
4.let windows install the drivers automatically
5.use wiiconnect
6.optionally remove bttray.exe from start>run>msconfig>startup

Now you are able to switch between ms-stack and widcomm stack without rebooting reinstalling or repluging.
msstack:
kill bttray
"C:\WINDOWS\system32\rundll32.exe" bthprops.cpl,,BluetoothAuthenticationAgent"
widcomm:
kill rundll32.exe
"%ProgramFiles%\WIDCOMM\Bluetooth Software\bttray.exe"

@thex :Maybe you can add a bluetoothstack-switch feature to the next version

edit: sorry, i found out that switching is only that easy in one way (ms stack 2 widcomm). To switch from widcomm to msstack you need to do the driver reinstall procedure (step 2-4). I tell you when i find out how to solve that.