Author Topic: WiimoteConnect UPDATE(0.5.9) now with multi wiimote support!  (Read 185668 times)

Offline apdewith

  • *
  • Posts: 25
  • Karma: +0/-0
    • View Profile
« Last Edit: July 19, 2008, 02:31:07 AM by apdewith »



Offline chappie

  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
I unzipped the wii remote connect.rar and ran the .exe however still getting message that Wii remote not detected.  is there any additional configuration i need in order to get this to work?  i'm running XP.



Offline TheVirtualGadget

  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Hey,

In addition to the paypal link, maybe you can link the words WiimoreConnect to the current version or link to a page with the different versions listed. That way anyone who wants the current release just has to find any message by you.

The sig gets applied dynamically as the page is loaded on many forum software apps so it would even update old posts. that should save you a small amount of time.

As far as hardware is concerned, do you use a notebook or a desktop?
thanks?



Offline vbcrayon

  • *
  • Posts: 13
  • Karma: +0/-0
    • View Profile
Hi,

Very nice program! But I'd like to give you two suggestions.
1 - Could you program a connection looping? Your program would stay on this looping till a sucessfully connection.
2 - Is it possible your program detect that connection is already OK? To prevent errors in already established connections.

Another question is: are you planing to provide the source codes for the your program?
« Last Edit: October 01, 2008, 02:58:13 PM by vbcrayon »



Offline JoriQ

  • *
  • Posts: 19
  • Karma: +0/-0
    • View Profile
Program works great on my SLOW work PC running XP (microsoft dongle for BT).  The only thing is that it runs the program (Smoothboard) too fast.  The connection has not been completed yet and it runs the program.  So the icons come up in the system tray, but the program doesn't finish starting up.  When I hover over the icons they disappear (cause the program isn't really running).  Then it connects, I run the program manually and everything is fine.

I have been using the wiiboard for a bit, and I just found this program.  It makes connecting so easy, I real feel that it makes the whole project more manageable, and I'm a computer person, so if non-computer people were to use this, I would expect even more so. 

In high school I can't come in in the morning, hook it up and use it all day.  I am constantly hooking it up and unhooking it, so this will make my life so much better.

Thanks so much!

---------------------
JQ


Offline thex

  • *
  • Posts: 83
  • Karma: +8/-0
    • View Profile
Sorry for not posting here this long. I was busy with another project.

I am going to fix the starting function and add multi wiimote support as soon as I find some time.

Thanks for the donation of 40 to the project by John Cumings. I will use this money to buy a second wiimote for developing the multi wiimote support.

So feel free to donate, donations keep projects like this running.

thex

Please donate via paypal to the WiimoteConnect project

project thread!


Offline benpaddlejones

  • Support Admin
  • *
  • Posts: 1178
  • Karma: +49/-0
    • View Profile
    • Inter.Connect.Ed
Thex
Welcome back!

I hope your other project was sucessful, this is a massive request for help that would really push the wiimoteproject forward and respect (hopefully $$$) to you.

I posted this just after you went on holidays:
thex
Check out my post: http://www.wiimoteproject.com/wiimote-and-bluetooth-connectivity/finally-a-fix-for-bluesoleil-usb-bluetooth-stop-bluesoleil-crashing-your-comp!/.

I'm hoping you may be able to use this to get widdcom on your system and get WiimoteConnect working with Widdcom, without having to buy a new dongle?

Benpaddlejones  ;D

I rember you saying you couldn't modify to incorporate widdcomm becuase you didn't have a working widdcomm dongle. The above should fix that.

If you read my post: http://www.wiimoteproject.com/project-ideas/programmer-need-wiimote-connection-utility/ This project really needs a connection utility that works with all three stacks. Bluesoleil can be downloaded from http://www.bluesoleil.com, you already have windows BT working and the above will get you access to widdcomm.

A universal windows BT application would mean a massive amount to this project, and really push it forward removing the last barrier to mass uptake.

benpaddlejones :)


See my full profile and links on my Google Profile: http://www.google.com/profiles/benpaddlejones


Offline thex

  • *
  • Posts: 83
  • Karma: +8/-0
    • View Profile
Reply #52 on: November 11, 2008, 10:49:51 AM
New release!
http://www.2style-graphics.de/wiiconnect/WiimoteConnect-0.5.9.zip

I bought a second Wiimote from the donation and implemented the multi wiimote support. It works great and solid here. You can also connect one Wiimote after the other because the connection of already connected Wiimotes is kept alive while connecting new ones.

Concerning the other BT stacks, it will take to implement that, so dont except an update soon but i will be working on that in the future.

thex

Please donate via paypal to the WiimoteConnect project

project thread!


Offline benpaddlejones

  • Support Admin
  • *
  • Posts: 1178
  • Karma: +49/-0
    • View Profile
    • Inter.Connect.Ed
Reply #53 on: November 11, 2008, 03:41:36 PM
Love ya work thex.
 :D   :D   :D   :D   :D


benpaddlejones


See my full profile and links on my Google Profile: http://www.google.com/profiles/benpaddlejones


Offline polaxgr

  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Reply #54 on: November 20, 2008, 10:30:53 AM
hi i am total new on this..i just baught bluetooth usb adaptor , cause my pc didnt have VT , and it came with BTsoleil programme, i cant connect the wii remote to it and ur programme pops up problems...any help? about microsoft .net framework is the problem..
« Last Edit: November 20, 2008, 10:32:39 AM by polaxgr »



Offline Metacore

  • *
  • Posts: 4
  • Karma: +0/-0
    • View Profile
Reply #55 on: January 01, 2009, 04:46:58 PM
I know the thread is kinda old by now, but I really wanted to mention this, and figured it shouldn't go in "project ideas" since the project already exists.

First, I'd like to thank Thex for making life for all of us a little easier by making this little app, so thanks. With that being said, it still wasn't what I expected when I used it, but came very close. What I am trying to do is have my media center PC that's hooked up to my TV always be ready to connect to the wiimote so I don't have to touch anything but the wiimote itself to connect it. I figure that although my setup may be kind of rare, this idea could still benefit enough people to be considered for the WiimoteConnect app.

Essentially, I propose the addition of a "catch-all" mode that would be constantly looking for a wiimote signal. All it really needs to do is "press" the connect button every set amount of time(either user configured, or subtract the time it takes for the wiimote to be connected from the time the wiimote is discoverable after a single press of the 1 and 2 buttons for the maximal, and therefore optimal, time. If it changes each time you connect, simply assume it is always the longest time to play it safe). Some more small modifications would have to be made, which would be to disable the popup notifications when in this mode(only when not in the tray, since those balloon notifications disappear after a couple of seconds anyway) and have the option for an audio notification. Ideally, it would be a PC beep by default with an option to point to a .wav file(this way you have .wav functionality without bloating the download by packaging a .wav file).

There, that's it, not a lot of changes and it would be moving the program to what I see is it's next logical step(complete automation). If this still does not seem like enough, you can always try pairing the Wiimote using the new found information that "The required PIN is the hosts's Bluetooth address, backwards (last byte first), in binary (6 bytes). Most current Bluetooth implementations don't deal with this correctly, as they usually consider the PIN to be a regular ASCII string (no 00 bytes, etc)." -benpaddlejones's summary of the information found here: http://wiibrew.org/wiki/Wiimote#Bluetooth_Communication . I don't know if you could pass any information you want as a PIN through the API you use, or if the limitation is in the stack itself though...

Just as a side note, the whole idea that this was even practical came from an existing feature in GlovePIE that always looks for a connection, but is only compatible with BlueSoleil, (which in my case only connects to the wiimote, but does not work with GlovePIE). I'd also like to bring to the attention of anyone that reads this and uses the app for a purpose similar to mine: If you want want disconnect the wiimote for any reason, simply hold the power button for about a second or two. If you have a Wii in the room you don't have to worry, since it won't turn on a powered down wii, nor will it shut off an already running wii(if you need to do either as well as dissconnect the wiimote, just press the power button again).



Offline benpaddlejones

  • Support Admin
  • *
  • Posts: 1178
  • Karma: +49/-0
    • View Profile
    • Inter.Connect.Ed
Reply #56 on: January 01, 2009, 09:02:33 PM
Metacore
I'm currently in the other end of Australia. When I get home in a few days I will be playing with this. If my understanding is correct we may no longer need a connection application We will be able to sync with the wiimote.

benpaddlejones :)


See my full profile and links on my Google Profile: http://www.google.com/profiles/benpaddlejones


Offline thex

  • *
  • Posts: 83
  • Karma: +8/-0
    • View Profile
Reply #57 on: January 02, 2009, 03:32:41 PM
Hey metacore, i already had that idea myself but didn't find the time to do it jet. I may take a look at it next few weeks.

As far as i understand:
- search for wiimotes every X miliseconds/seconds
- connect to new wiimotes (don't disconnect allready connected ones)

Problems I see:
- Discovery takes few seconds so it cant be run every x ms/s
- Wiimote is only in sync for 20 secs

Solutions (i thought about while writing here)
- Learn a WiiMote (know Bluetooth mac)
- Try to only connect to known wiimotes
- should be very fast!

I think after my examns in february I'll rewrite all my code because it is some kinda dirty ;)

Sad that nobody is donateing :( only recived one donation so far and used it to buy a second wiimote for development...

Thx thex

have i put the version wit learned wiimotes online? think not.. wil do that these days too...

Please donate via paypal to the WiimoteConnect project

project thread!


Offline thex

  • *
  • Posts: 83
  • Karma: +8/-0
    • View Profile
Reply #58 on: January 24, 2009, 02:40:45 PM
Hey,
I just read the other posts concerning automatic wiimote connection.
If anybody wants to check out my attempt on autoconnect you have to do this:

1. download attachement
2. extract it
3. run it
--on first start to learn the wiimotes--
4. go to settings
5. click the learn button
6. put wiimotes into discovery mode
7. klick ok

after a few seconds it should display how many wiimotes it found.

8. klick ok
9. klick ok to close settings

from now on if you start programm and klick the "a" button the programm searches for wiimotes every 20 seconds!

So if you have tho programm running in the background all you have to do is to continiously press a+b and the wiimote will connect.
To disconnect it turn the wiimote off.
Press a+b again to connect it again.

this is really just a try, i want to know if that method works before i implement it better!

Not implemented jet:
- start programms in learned/automatic mode
- automatic mode on startup
- variable scan interval
« Last Edit: January 25, 2009, 06:08:26 AM by thex »

Please donate via paypal to the WiimoteConnect project

project thread!


Offline wyx2000

  • *
  • Posts: 4
  • Karma: +0/-0
    • View Profile
Reply #59 on: January 25, 2009, 12:01:38 PM
I am using Vista 64, I do use MS stack. My bluetooth is 350 which is not in the compatible list. So I thought I had to use BlueSoleil to play with Dolphin (I assume you know the WII emulator). But later I found BlueSoleil has some problem for me. So I uninstalled it and reinstalled the VISTA default stack.

Now on my device manager, under Bluetooth Radios, I have two items :
  Dell Wireless 350 Bluetooth
  Microsoft Bluetooth Enumerator

So I think I am using the default MS statck.

I tried both your original 0.5.9 and the 0.5 debug. Both gave me "No wiimote found!" .