Wiimote Project
Hardware Support => Bluetooth & Connectivity Knowledge Center => Topic started by: thex on February 16, 2009, 03:33:06 PM
-
Hello,
new thread new version.
Works with MS BT-stack and Windows Vista/XP
if you don't have the XP stack follow this tutorial to use it.
http://www.shootingsoftware.com/Widcomm.htm (http://www.shootingsoftware.com/Widcomm.htm)
done:
- start app on connect
- glove pie starter
- automatic removal from known devices list
- tray icon (startup send to tray now in settings)
- autoconnect on startup
- multiple wiimote detection
- autoconnect to wiimotes
- autokill started programms
- some bugs fixed
todo:
- other BT stacks
download it here:
http://2style-graphics.de/wiiconnect/WiimoteConnect-0.6.zip (http://2style-graphics.de/wiiconnect/WiimoteConnect-0.6.zip)
constructive critics welcome
thex
-
Ouahh ! Felicitation, it seems to work super well (automation in the ignition) As said it "dsgclan", damage for the first message of connection, but it's a great job :-)
EDIT : Configuration: I chose every 2 seconds: super
I was continuiing testing adn of course 2s is too short
For memory : between 12000 and 15000
my configuration doesn't suffer from apps
PS : I am always OK for a translation in French
-
Nice to hear that it is working :)
2 seconds my be a bit short because the process takes some time but it should work as i placed the discovery processes in different threads. Take a look if the app eats to much memory or so.
thex
-
Hi thex,
Any change that you will publish the code under an open source license?
If not, we have a peace of hardware that would finalize the automatic connection...see http://www.wiimoteproject.com/bluetooth-and-connectivity-knowledge-center/wiiscan-version-0-8-trayicon-and-hardware-spec/msg8614/#msg8614 (http://www.wiimoteproject.com/bluetooth-and-connectivity-knowledge-center/wiiscan-version-0-8-trayicon-and-hardware-spec/msg8614/#msg8614). The hardware here is currently in the final test phase, but as the source is open you could easily integrate it you self in you code later...but what I am suggesting is some sort of collaboration.
Regards
.carsten
-
Hi, I don't know yet if I'll release it as open source.
I read the post you pointed out but I don't get what your "Device" does...
is it for BT connectivity? why properitary hardware if any dongle fits?
Or does it "press" the sync button over an usb io card?
Or what does it??
-
Hi thex,
Or does it "press" the sync button over an usb io card?
Well, I was maybe a little unclear in the post, but what the "device" does is to automatically powering the wiimote on (and off). Yes, this will be like "pressing the sync button" using a software function call, so that the last part of the connection sequence can be made fully automatic.
The wiimote in my setup gets power from the computer USB line and currently I support two methods for autopowering on:
- USB hub mode (turning the entire PC USB hub system off and on!)
- using a USB io card for external powerswitching.
The first mode is not so nice, in the sense that all devices on the USB gets powered off and on---this includes the BT dongle, and leads to some Windows Plug-and-Play problems. Hence the need for the second solution.
But I guess you know all about the troublesome MS BT stack and the annoying interference from the MS "Plug-and-Play" system?
Regards
.carsten
-
Great job, any chance of a 64-bit build of this project and a link to download it? Thanks.
-
I can translate it into German
-
It isn't thought to be translated yet. And by the way I'm from germany myself ;)
thex
-
Hello,thex!
Your software is so good to use!
But,i have some problems:
A、
when connecting, what measures can be taken so that i don't necessary to press the wiimote keys 1 and 2,so the software can be automatically connected to the wiimote?
B、
In your software, it have a learn mode,it tell me:when i use this mode,wiimote which are already listest in the bluetooth settings dialog will be learned even if not in discovery mode.
but when i use this mode,i must press wiimote key 1&2 to let wiimote go to discovery mode,if i haven't do this,the software can not connect the wiimote.
Please give me a answer,thanks!
-
concerning A:
The only other way to put the Wiimote in discovery mode is the red button in the battery tray. You can put a little block there to press it continously. If you then use an external powersource to power the wiimote, the wiimote will enter discoverymode as soon as power is connected.
See: http://www.wiimoteproject.com/wiimote-whiteboard/ceiling-mounting-and-remote-syncing/
concerning B:
I don't really get the problem.
When learning a Wiimote it has to be in discovery mode or it has to be listed in the Bluetooth devices list to get recognized.
Thats how it works, there is no other way except you could enter the Bluetooth MAC address by hand ;)
thex
-
Hi,
I am having problem with WiiMoteConnect working with WiinRemote.
In WiiMoteConnect -> Settings, I have:
- search for WiiMotes and connect them all
- 10 interval seconds
- start autoconnect on startup
- autokill prog
- connect on startup
- clear wiimote on connect
I press 1&2 on my WiiMote.
Windows Vista says "Your devices are ready to use". Then a window pops up and says "You must restart your computer to apply these changes".
WiiMote Connect says "1 WiiMote/s successfully connected"
But the blue light on the WiMote is still flashing.
And in WiinRemote the title bar says "Error(2) The system cannot find the file spe ..."
By the way, I have managed to connect my WiiMote before using the old way of clicking Bluetooth Devices and adding manually.
If anyone can let me know what I am doing wrong, I am all ears.
Thanks!
-
hi Thex, I got time this weekend to test your new V0.6, it works nearly perfect! when I have my wiimote learned by the software it connects to PC very fast and it never fails (in the last version occassionally it fails on the first 1 or 2 attemps to connect).
Now I can see only 2 improvements it can use, I believe you already know them and hopefully working on them already?
1) the software does not start with windows:
If I press down 1 and 2 permanently and have you software start with windows and auto-connect, the wiimote can be connected fully automatically.
2) the pop up message to ask user to turn on the sync mode of wiimote.
I have a question, you said "The only other way to put the Wiimote in discovery mode is the red button in the battery tray." and you refered to the post of "cumings" on pressing down the red sync button, but why do we have to press down the red button to enter sync mode for only 15 seconds, while we can press down the 1 and 2 buttons to enter sync mode forever? "cumings said in the post that the problem of pressing down 1 and 2 buttons permanently is they could be picked up by another PC, that's maybe the case for a building with multiple wiimotes installed, but for individual user like me, it is not a problem at all, right?
-
@iceman321
The autoconnect feature requires to have the Wiimotes learned.
If the LEDs on your wiimote keep flashing after 20 seconds your Wiimote is definitely connected. I would recomend not to test with the WiinRemote software, you better use the tool provided with the WiimoteLib (see it attached).
@dsgclan
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.
thex
-
Hi Thex,
I installed BlueSoleil 3.xx, but it didn't work. So I uninstalled it.
In my frustration last night, I installed the WidComm bluetooth drivers using MSI StarKey. I got the WiiMote to connect by using the bluetooth setup wizard as described in http://www.wiili.org/index.php/How_To:_Widcomm
If I want to use WiiMoteConnect 0.6 should I uninstall the WidComm driver and hope that the Windows Vista bluetooth driver gets reinstalled. Then I can use WiiMoteConnect 0.6 again?
I remember before that when I used WiiMoteConnect 0.6 previously it said "4 WiiMote/s connected" but I only had 1 WiiMote on sync mode.
Can you let me know if WiinRemote does not work with WiiMoteConnect 0.6 ?
Thanks!
-
iceman321
Remove all bluesoleil & widcomm (Bluesoleil v3 will bluescreen anyway).
Follow this: http://www.shootingsoftware.com/Widcomm.htm
Enjoy thex's wonderful work!
benpaddlejones
-
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!
-
ok, now I understand ;)
I'll definitely add it in the next version.
thex
-
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
-
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
-
Thanks for the donation,
it would be great if the error gets fixed.
maybe just put a try cache block arround it and restart your whole app as a first fix.
but at the moment the workaround i posted should work, but the nag screen then will be a "pain in the **LOVE**" ;)
thex
-
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
-
Can you help? I've installed 0.6 but it won't find my wiimote (no wiimotes found) although the thing is connected - using MS BT on vista home premium with a bluetooth dongle. currently I have to remove the wiimote from bluetooth places in order to connect it again, which is the reason for your program, I think? Can't get 0.6 to learn my wiimote, presumably for the same reason it won't find it in the first place?
Adam
-
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!
-
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!
It seems if I tick the "clear wiimotes on connect" check box, the false error message has never happened, could this have something to do with it? anyway, this is not an important issue.
I'm curious "clear wiimotes on connect" is for?
-
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
-
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
No, thats not jet supportet. But you cold create a batch file which starts several applications but they wil not be closed whenn all wiimotes are disconnected.
thex
-
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.
-
hey, i'll definitely check that out and may implement it in the next version. I'll try it on my eepc which is running Widcomm.
thex
-
Hi, I have an interesting problem. Using the standard Vista Bluetooth I am able to seamlessly connect with my Wiimote, but the computer receives no input (though it did work on two very brief occasions). I have spent many hours trying to resolve this mystery, but to no avail. Almost all online tutorials go straight from making the connection to using the remote in GlovePIE or some alternative. I have already done plenty of research on building a sensor bar, but there would be no point unless I could get the remote working in the first place.
That is why I was hoping WiimoteConnect would fix my connection issues. Unfortunately, it doesn't seem to be able to find the Wiimote, no matter what I try. Is this because I am using Vista x64, is there some other issue?
I should probably note that I have installed and uninstalled both Bluesolei and Widcomm, and then used two registry cleaners. I also looked at http://www.shootingsoftware.com/Widcomm.htm, but I find the instructions very confusing. He wants me to go into the device manager, find the bluetooth device (how?), and then what? I'm not sure if his instructions will solve my issue though, because my the Stack is certainly the default Microsoft one and seems to be working correctly.
Thank you for reading this loong post :D. I would appreciate any suggestions or advice about fixing this issue. I also have a Webcam, TeamViewer, and AIM if anyone is ambitous enough to help guide me through one of those.
-
Maybe you tried this already, in glovepie there is is the option troubleshooter>bluetoothfix. Actually it only solves the problem when it is within glovepie.
If you are not shure if the wiimote is connected: when the msstack recognizes the wiimote you can see a tooltip that a hid-device is installed and if it is connected the syncblinking will continue and does not stop after a period of time; When it is connected the blinking stops when a program takes control over the wiimote.
-
I have the bluetooth device and wiiconnect hooking up to smoothboard working on my Vista desktop, but I can't duplicate it on my Vista laptop.
I can get the wiimote to hookup to smoothboard working but wiimoteconnect won't learn my device. I've looked through the solutions on this thread and tried them with no luck. So, I'm wondering what information I need to provide so I can get WiiConnect working.
Thanks
Dale
-
Hello,
most of the problems seem to be caused by the 64Bit systems. WiimoteConnect is not working with them yet!
I'm currently looking to fix that but I don't have a 64Bit machine running here to test.
thex
-
My HP touchsmart is a 64 bit machine. I know its not the same but I would be willing to help you test.
Thanks
Dale
-
Ok, I now implemented the new version of the dll which I use to acces the bluetoothstack as far as I know it now should work with 64 Bit machines.
Please somebody with a 64bit machine and a 64bit Windows test this version!
thex
-
Hi Thex-
Great Job, its working on my 64 touchsmart
Thanks
Dale
-
Maybe you tried this already, in glovepie there is is the option troubleshooter>bluetoothfix. Actually it only solves the problem when it is within glovepie.
If you are not shure if the wiimote is connected: when the msstack recognizes the wiimote you can see a tooltip that a hid-device is installed and if it is connected the syncblinking will continue and does not stop after a period of time; When it is connected the blinking stops when a program takes control over the wiimote.
Thanks for replying elypter. Unfortunately, I have already tried the bluetoothfix which often helps me connect the Wii remote. The hid-device is installed, the lights stop blinking, and bluetooth devices says it is connected, but the computer doesn't recieve any input in Glovepie or WiinRemote. Is there any special .PIE file I should open? I usually try out several of them.
@ Thex
I just tried out the 64 bit version, and it works great! It makes establishing a connection a lot easier. So far, though, I still don't seem to be receiving input in my programs despite the connection. It seems like the problem lies elsewhere. Could it be my RocketFish bluetooth dongle? It was the only one available at Best Buy. There was a short time where the connection seemed to be working though, so this leads me to believe otherwise.
Thanks for the support Thex :D
Edit: I tried it out again a few seconds after posting. Once again WiinRemote was receiving all of my button presses, but as soon as I went to the preferences menu to change cursor movement to motion sensor it stopped working. Odd. >.<
-
Thex,
I realize you plan on adding support for other bluetooth stacks, but I'm wondering if you've looked at them already and it's not possible with their apis, or if you just haven't gotten around to it yet.
In particular I'd like support for Widcomm. I downloaded the sdk, but I'm just a lowly web developer and have no idea where to start.
-
Hi Thex
This is what I receive when I click "Connect" on an XP machine. I don't have any problem connecting on this machine otherwise, just when I try to use Wiiconnect. I can use java and smoothboard no problem. Here's a screenshot
thanks
Dale
-
Didn't your read the error message? It clearly says that the bluetooth Stack on your machine isn't supported. So you seem to have a Widdcom or Bluesoleil stack but for wiimoteconnect you need the Microsoft stack.
thex
-
mystre
Didn't your read the error message? It clearly says that the bluetooth Stack on your machine isn't supported. So you seem to have a Widdcom or Bluesoleil stack but for wiimoteconnect you need the Microsoft stack.
Thex's frustration comes from this is about the 100th time this question has been posted.
Thex
have you thought about setting up a softwrae manual in the Wiimoteproject WIki? This could guide users and you can send them there for self-guided problem solving?
benpaddlejones :)
-
I'm just talking to a professor of our universety if i could use wiimoteconnect as a universety project, if so, i wil be forced to produce some kind of manual ;)
thex
-
I teach k-6, and I understand the frustration of having the same questions asked over and over. :)
I've been at this for 2 months, and I've setup 8 other teachers without any failure due to responses I've read on this forum, and so I really appreciate it. I apologize for the redundancy but all the different stacks, drivers, and poking around areas of the computer I've never worried about before gets confusing. As for myself, I more of a visual person-so a 45 second screencast that shows me, for example, how to get rid of an unwanted bluetooth stack, is more effective than a 1 1/2 pages of text.
As for the problem I described above on the XP machine, I used a different bluetooth device and everything worked fine.
Have a great night everybody
Dale
-
I have discovered an issue with using WiimoteConnect. The number of disconnected HID devices is increasing every time the Wiimote is reconnected. You can see how many unused devices are installed by doing the following in a batch file.
SET DEVMGR_SHOW_NONPRESENT_DEVICES=1
START DEVMGMT.MSC
Device manager will open. Then select View->Show Hidden Devices
Non present devices are shown with greyed out icons.
I currently have 130 non present "HID-compliant game controller" devices
Also quite a few "Bluetooth HID Device" entries.
I initially found them in the registry.
Is there any way for your application to clean up these devices?
-
Hi thex,
I came to Wiimote Connect as I was searching for a program that support autoconnect. But I have a big problem with it - hope this is new for you, I didn´t find anything about it:
The Wiimote connects perfectly with the pc. The lights on the wiimote keeps flashing, and also in the "Systemsteuerung" (don´t know the engish word, sorry) the Wiimote is connected. But I cannot get any data from the Wiimote. WiinRemote just says "Disconnected" and GlovePie just doesn´t get any data. But GlovePie can turn on and off the lights on the Wiimote. :o
What is going on here? Is there a way to get it running?
My system: WinXP, Sp3, 32 Bit and MS Stack, of course ;D
Edit: I forgot: I had the recent Bluesoleil installed before. With bluesoleil Glovepie worked with my Wiimote. Then I removed bluesoleil in order to use WiimoteConnect and switched back to the ms stack.
Thanks
Stepko
-
I have the same issue as Stepko. I tried out Bluesoleil on my Thinkpad T43 and it worked fine but then the trial expired. I uninstalled Bluesoleil and experimented with the default BlueTooth package that comes with my T43. I can successfully connect the WiiMote via WiiMoteConnect but none of the apps seem to work.
WiinRemote thinks it is connected but it does not receive any data, and WiimoteWhiteboard does not detect a WiiMote. GlovePie in Wii Test mode can change the 4 blinking lights of the WiiMote so that there are only 2 solid lights in the middle, but besides that nothing else works.
Any suggestions would be much appreciated.
-
Hey Thex!
I'm not sure if this is the right place o ask this, but here goes...when I try to connect my Wiimote, I get different results every time. It occasionally connects, but the next time I try to connect it it takes about 30 minutes to get it up and running. The Wiimote goes into discovery mode when I press the sync button. Windows finds it, starts to install it, but then the remote turns back off, and Windows stops installing it. All the while, I am running WiimoteConnect to try and get that to connect to it. I'm not sure what I am doing wrong, and I can't find anywhere a distinct set of instructions on what to do at this point. What buttons do I press when? ::sigh::
Anyway, thank you ahead of time for your help! Great program (when I can get connected!).
Sean
-
Great work!
I'm with Dell Inspiron 1720, BCM2045 built in device and your method worked for me just fine. Bluesoleil, that limits to only one device is the past, crawling Dell web sites in hope I will find something that will let me use the hardware they sold me is the past.
-
Amazing program Thex! I just donated (even navigating the German language Paypal) :D
I've been promoting your work, and Boon Jin's, to teachers in my school board. Due to restrictions on running exe's (that haven't been board licensed/approved) from network drives, the best solution has been to put all the software on a USB flash drive.
Is it possible (in v.0.6.0, or a future version) to put a "relative path" into the "run programme" field? (so it will connect to Smoothboard.exe, on the USBdrive, no matter what drive letter is assigned)
Is it possible to keep the current "Wiimote Connect" settings in a file on the USBdrive? It seems to lose the settings with different PC's or different USBdrives (although maybe this is in how I distribute the files to teachers in other schools, as a zipped folder).
Thanks for all your work!
Ron
Upper Canada District School Board
Windows XP PC's, MS Bluetooth stack exclusively
-
Hello again thex,
I won't ask for your source code (enough others are doing that), but could you please clarify any limitations on the executable file. You've generously offered to share it, but what rights would you like to retain? For example, if working with colleagues can I transfer it from a USBdrive to other PC's, or vice versa (without downloading directly), keeping all files unaltered and giving you credit?
Might I recommend that you license it with "Creative Commons"?;
http://creativecommons.org/about/licenses (http://creativecommons.org/about/licenses)
I'd hope that you choose an accommodating license, such as "Attribution Share Alike".
Cheers,
Ron
-
Excellent work Thex!
It' works flawlessy with my setup. Also I found that MS stack is more stable than Blusoleil.
Also it works perfectly in Windows Seven RC too! ;D
-
Hehe, you are going to like this one, thex. I just tried to run WiimoteConnect on a x64 machine, and it could start but kept crashing after pressing the "connect" button. Basically, it complains about an unhandled exception as the program attempts to read or write protected memory. See the quotation below for more info about it. I skipped the "Loaded assemblies" section. Bug me if you'd like to see it.
I tried to get an x64 InTheHand.Net.Personal.dll, which I supposedly got from here (http://www.alanjmcf.me.uk/temp/32feet%20Win32%20for%20x64%20test%20r51350.zip), and place it near the *.exe. But then WiimoteConnect failed to use it.
Now the questions. :) Is the problem truly due to the x64 machine? If yes, can you build WiimoteConnect for it? :)
The first error report:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at InTheHand.Net.Bluetooth.NativeMethods.WSALookupServiceBegin(Byte[] pQuerySet, LookupFlags dwFlags, Int32& lphLookup)
at InTheHand.Net.Sockets.BluetoothClient.DiscoverDevices(Int32 maxDevices, Boolean authenticated, Boolean remembered, Boolean unknown)
at InTheHand.Net.Sockets.BluetoothClient.DiscoverDevices()
at WiimoteConnect.frm_main.btn_connect_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
-
I am at a loss, I have a computer that connects the wiimote perfectly, but I am installing a new computer and having issues with the wiimote connecting to it. I am using the same bluetooth radio, but the new computer will not keep the wiimote connected. When using wiimote connect it finds the wiimote but says "not all wiimotes connected successfully" I have looked everywhere but cannot find what I am doing wrong.
-
Since they still didn't fix the board (http://www.wiimoteproject.com/comments-and-feedback/please-fix-this-due-to-my-desktop-theme-i-have-to-write-black-on-black/), I will keep this short.
My experience with this software was that i have to push synchronization buttons on both Wii Remotes, slightly before I click the "Connect" button of the application. Just in case it is needed, I also press both synchronization buttons slightly after I clicked the "Connect" button.
While establishing the connections, it may happen that one of Wii Remotes stops blinking. In that case, it needs synchronization button to be pressed again and immediately. In some cases, this saves you from repeating the whole process.
Should it happen that all or some of Wii Remotes fail to connect successfully, you'll have to repeat the process. Press synchronization buttons of both Wii Remotes and then click the "Connect" button in the application.
Frustrating at times, but it still works better than nothing.
-
WiimoteConnect works well for getting the wiimote connected easily and quickly. I love the autoconnect!
I'd like to find a way to easily DISCONNECT though. I'm setting this up for a classroom teacher who had the remote stuck to the bottom of the ceiling mounted projector. To connect, a yard stick is used to press the 1 and 2 buttons.
Solutions I can think of now:
1. Use the wiimote power button: not possible to do with the yardstick since power button is too small
2. Disconnect USB bluetooth: not possible since it's in the back of the PC
3. Open the MS Bluetooth window by double clicking the system tray icon, then clicking the wiimote under devices, then clicking the Remove button.
#3 is the only workable one right not, but I want to make disconnecting as easy and fast as possible to prevent the battery in the wiimote from running down. What I don't like about #3 having to teach to go to one spot to connect, then somewhere else to disconnect.
Would it be possible to add a disconnect function to WiimoteConnect?
-
Anybody tried WiimoteConnect in Windows 7 x64? Do you need GlovePie?
-
Anybody tried WiimoteConnect in Windows 7 x64? Do you need GlovePie?
I tried it with the latest version of WiiConnect, but I couldn't get the Wiimote to connect. Windows once found the Wiimote as BT-device, but lost it's connection afterwards. GlovePie isn't working too.
The only thing I found to work, is SmoothBoard.
-
Anybody tried WiimoteConnect in Windows 7 x64? Do you need GlovePie?
I tried it with the latest version of WiiConnect, but I couldn't get the Wiimote to connect. Windows once found the Wiimote as BT-device, but lost it's connection afterwards.
Pair it one more time (so Windows finds the drivers faster), or keep pressing buttons 1 & 2, and it won't lose connection, though the LEDs will keep blinking. That doesn't mean it isn't useless: Connected, but pretty much useless.
The only thing I found to work, is SmoothBoard.
That's encouraging. Will give it a try, though from what I've heard, SmoothBoard doesn't work in Win7. Do you have the x64 flavor?
-
Anybody tried WiimoteConnect in Windows 7 x64? Do you need GlovePie?
I tried it with the latest version of WiiConnect, but I couldn't get the Wiimote to connect. Windows once found the Wiimote as BT-device, but lost it's connection afterwards.
Pair it one more time (so Windows finds the drivers faster), or keep pressing buttons 1 & 2, and it won't lose connection, though the LEDs will keep blinking. That doesn't mean it isn't useless: Connected, but pretty much useless.
The only thing I found to work, is SmoothBoard.
That's encouraging. Will give it a try, though from what I've heard, SmoothBoard doesn't work in Win7. Do you have the x64 flavor?
Windows doesn't recognize is anymore. Seems like it did only the first time, but maybe if I delete the controller from the system-manager. When using SmoothBoard, it installs the drivers every time! It connects and Windows finds the device and installs it.
-
Smoothboard's SmoothConnect indeed works in Windows 7 64-bit and other 64-bit/32-bit windows platforms.
(http://www.smoothboard.net/files/screenshots/SmoothboardonWindows7.jpg) (http://www.smoothboard.net)
I am using Windows 7 64-bit. :)
Regards,
Boon Jin
-
Smoothboard's SmoothConnect indeed works in Windows 7 64-bit and other 64-bit/32-bit windows platforms. I am using Windows 7 64-bit. :)
Thanks. Would you mind giving us some details and/or screenshots about the particular BT stack and drivers you're using, and perhaps some details about your BT dongle?
Many thanks again.
-
Smoothboard's SmoothConnect indeed works in Windows 7 64-bit and other 64-bit/32-bit windows platforms. I am using Windows 7 64-bit. :)
Thanks. Would you mind giving us some details and/or screenshots about the particular BT stack and drivers you're using, and perhaps some details about your BT dongle?
Many thanks again.
Sure. I will do it later when I have the time.
Regards,
Boon Jin
-
hey,
sorry to all of you who had some problems.
I dodn't get any notifications for new posts and so I didn't check this thread.
I will read through the posts and clarify if there is sth when i have some time
Regards thex
P.S.: Boonjin How did you implement Bluetooth? InTheHand?
-
Is there a way that so when the WiimoteConnect sees a connection it runs a application. ? As well if it sees that a wiimote is not connected that runs a application ??
-
Hi all,
I've been trying to connect using WiimoteConnect but so far haven't had any luck. Windows recognises the Wiimote, and using the remote by manually running a GlovePIE script works fine, but WiimoteConnect doesn't acknowledge the connection - I get "No Wiimote found".
I've tried using both connection methods under "settings", and have tried the other options ("clear wiimotes on startup" and "autokill prog" - I'm curious to know what those do by the way), but no luck.
I'm running Vista 64 with the MS BT stack. I saw the posts in April about a 64-bit version; is the link at the top of this thread updated with that version, or is there a separate file somewhere that I can't find?
Thanks for any ideas, and thanks Thex for your hard work.
Sam
-
Hey Sam,
if you see the post while you're logged in, you can see an attached file to it.
And i must say it works on Windows 7 x64, thanks a lot!
but just one thing...
i'm trying to run GlovePIE script's directly from Wiimoteconnect but no luck. What should i write in the box field for it? just eh script name? or name + whole path? or even name+ path after glovepie.exe?
-
Hello all,
This is my first post on this forum so I would like to say good work !!!
Now, regarding WimoteConnect-0.6 operating in Windows 7-64bit, I have the same problem as mentioned above (see Sam's post). The application brings a panel with the message "No Wimote found!". SmoothConnect works fine but it will be nice if we can have a stand-alone connector.
If you guys are busy just give us some clues how you implemented it so we can carry on your work.
I'm not sure how cuba managed to work it out. Maybe he can provide us his system's specs to compare it with ours.
My specs are:
O/S: Windows 7 Home operating in 64bit
BT: Dell Wireless 370 Bluetooth Mini-card (Widcomm 6.20.9600) with MS Bluetooth enumerator.
Thanks
Dion
-
Hi Thex, you guys are awesome. Excellent software.
Of late, I get this error when I click on Connect. Any idea how I could resolve and make it work?
************** Exception Text **************
System.IO.FileNotFoundException: Could not load file or assembly 'InTheHand.Net.Personal, Version=2.2.0.0, Culture=neutral, PublicKeyToken=ea38caa273134499' or one of its dependencies. The system cannot find the file specified.
File name: 'InTheHand.Net.Personal, Version=2.2.0.0, Culture=neutral, PublicKeyToken=ea38caa273134499'
at WiimoteConnect.frm_main.btn_connect_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
-
I have the same issue as Stepko. I tried out Bluesoleil on my Thinkpad T43 and it worked fine but then the trial expired. I uninstalled Bluesoleil and experimented with the default BlueTooth package that comes with my T43. I can successfully connect the WiiMote via WiiMoteConnect but none of the apps seem to work.
WiinRemote thinks it is connected but it does not receive any data, and WiimoteWhiteboard does not detect a WiiMote. GlovePie in Wii Test mode can change the 4 blinking lights of the WiiMote so that there are only 2 solid lights in the middle, but besides that nothing else works.
Any suggestions would be much appreciated.
I seem to have a similiar problem but I didn't see a response. I seem to connect but I don't ever see and data flow to wiinremote. I am using the MS stack but I haven't ever used the Bluesoleil stack. I had wiinrmote working with the widcomm stack. I uninstalled the widcomm software. If it connects properly should the leds on the wiimote stop flashing?
-
I seem to have a similiar problem but I didn't see a response. I seem to connect but I don't ever see and data flow to wiinremote. I am using the MS stack but I haven't ever used the Bluesoleil stack. I had wiinrmote working with the widcomm stack. I uninstalled the widcomm software. If it connects properly should the leds on the wiimote stop flashing?
Hi,
Have you tried using Smoothboard to test your Wiimote's connection?
Regards,
Boon Jin
-
Hi Thex ! Hi everyone !
I'm using wiimoteconnect in my school and it works so well !!
But I have a problem with the settings file : when I change user, the program lose its settings. I know why : the settings file is saved in the user's appdata directory.
Is it possible to save the settings file in the same directory of the .exe, or add a parameter in the command line to tell the program where to find its settings.
Thanks a lot. It's a very good job !
Welloum.
-
I have been using this, but I think the .net framework got updated now it crashes... here is my error
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.Configuration.ConfigurationErrorsException: Configuration system failed to initialize ---> System.Configuration.ConfigurationErrorsException: Root element is missing. (C:\Documents and Settings\Administrator\Local Settings\Application Data\Lukas_Reinhart\WiimoteConnect.exe_Url_eh0tsoiphnyml4nl44vry45upz1cf4in\0.6.0.0\user.config) ---> System.Xml.XmlException: Root element is missing.
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.ThrowWithoutLineInfo(String res)
at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
at System.Xml.XmlTextReaderImpl.Read()
at System.Xml.XmlTextReader.Read()
at System.Configuration.XmlUtil..ctor(Stream stream, String name, Boolean readToFirstElement, ConfigurationSchemaErrors schemaErrors)
at System.Configuration.BaseConfigurationRecord.InitConfigFromFile()
--- End of inner exception stack trace ---
at System.Configuration.ConfigurationSchemaErrors.ThrowIfErrors(Boolean ignoreLocal)
at System.Configuration.BaseConfigurationRecord.ThrowIfParseErrors(ConfigurationSchemaErrors schemaErrors)
at System.Configuration.BaseConfigurationRecord.ThrowIfInitErrors()
at System.Configuration.ClientConfigurationSystem.OnConfigRemoved(Object sender, InternalConfigEventArgs e)
--- End of inner exception stack trace ---
at System.Configuration.ClientConfigurationSystem.OnConfigRemoved(Object sender, InternalConfigEventArgs e)
at System.Configuration.Internal.InternalConfigRoot.OnConfigRemoved(InternalConfigEventArgs e)
at System.Configuration.Internal.InternalConfigRoot.RemoveConfigImpl(String configPath, BaseConfigurationRecord configRecord)
at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object& result, Object& resultRuntimeObject)
at System.Configuration.BaseConfigurationRecord.GetSection(String configKey, Boolean getLkg, Boolean checkPermission)
at System.Configuration.BaseConfigurationRecord.GetSection(String configKey)
at System.Configuration.ClientConfigurationSystem.System.Configuration.Internal.IInternalConfigSystem.GetSection(String sectionName)
at System.Configuration.ConfigurationManager.GetSection(String sectionName)
at System.Configuration.ClientSettingsStore.ReadSettings(String sectionName, Boolean isUserScoped)
at System.Configuration.LocalFileSettingsProvider.GetPropertyValues(SettingsContext context, SettingsPropertyCollection properties)
at System.Configuration.SettingsBase.GetPropertiesFromProvider(SettingsProvider provider)
at System.Configuration.SettingsBase.GetPropertyValueByName(String propertyName)
at System.Configuration.SettingsBase.get_Item(String propertyName)
at System.Configuration.ApplicationSettingsBase.GetPropertyValue(String propertyName)
at System.Configuration.ApplicationSettingsBase.get_Item(String propertyName)
at WiimoteConnect.frm_main.frm_main_Load(Object sender, EventArgs e)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
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.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3082 (QFE.050727-3000)
CodeBase: file:///c:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
WiimoteConnect
Assembly Version: 0.6.0.0
Win32 Version: 0.6.0.0
CodeBase: file:///C:/Program%20Files/WiimoteConnect-0.6/WiimoteConnect.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3082 (QFE.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
************** 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.
-
Hallo, sorry for my english (I`m from spain)
I'm traying to connect wiimote to my asus T91 (from the Asus eeePc family) with Windows XP, but I have this error when I run wiimoteconnect 0.6:
"Unhandled exception has occurred in your application. If you click Continue .....32feet.NET doe not support the Bluetooth on this device"
I have tried with an external Bluetooth (Trust) but it still doen't work.
Can you help me, please.
Thanks
-
When I run the Wiimote Connect (obviously). It says:
(http://dc174.2shared.com/download/R1mMbWpa/B00000001.bmp?tsid=20120326-011354-b499165b)
How can I solve this?
Or is that the, "other BT stacks" on your to do list?
-
sera que me pueden ayudar a interactuar una bateria bluethoot con el bluethoot incorporado en una hp pavilion dv4-1623la que pena la molestia ademas que aca ya no se ende el control primero de la wii aca ya solo se consigue el wii motion plus inside en que termina en tr al intentarlo enlazar y solo funciona con la smothboard air presentando serios ino¿convenientes
-
sera que me pueden ayudar a interactuar una bateria bluethoot con el bluethoot incorporado en una hp pavilion dv4-1623la que pena la molestia ademas que aca ya no se ende el control primero de la wii aca ya solo se consigue el wii motion plus inside en que termina en tr al intentarlo enlazar y solo funciona con la smothboard air presentando serios ino¿convenientes
With the Wii Remote Plus, you may use the Toshiba Bluetooth Stack with the special compilation of Smoothboard 2 or the new Smoothboard Air with Duo.
You may find more info here:https://docs.google.com/document/pub?id=1X_Q7_Da4-g2l6AaHgHZTrdzyAuPuM6UmU8zeK6aUG-k (https://docs.google.com/document/pub?id=1X_Q7_Da4-g2l6AaHgHZTrdzyAuPuM6UmU8zeK6aUG-k)
Regards,
Boon Jin
-
the link at op is broken. does anyone know where i can download wiimoteconnect0.6 from? thx!
yantz