Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Metacore

Pages: 1
I happen to have the file, it does actually authenticate the wiimote, and it seems to be open source, so I hopefully it won't be a problem if I uploaded it...
That is both the binary, a sample version of Wiimote Whiteboard that WiiScanTray works with, and the source itself, if someone needs it. Maybe someone else can figure out what's going on, since it does seem to authenticate, but not reconnect when needed. One thing you need to note is the wiiscan.ini file, where the MAC address of the intended wiimote is. The current filter should match your wiimote, but might not.

Also, as far as the program's function, this is what it does in Windows 7 x64
GlovePIE's Auto-connect

Registered with WiiScanTray

While it works after after the initial connection, once it disconnects, it never becomes reconnected again, though it continues to show it as "Authenticated."  I'm not a developer, so I'm not really sure what it means, but I'm guessing there is more to creating a permanent connection then just authenticating it, so even with authentication(which this does seem to provide) you'd still need some kind of auto-connect feature. That's just a guess though, hopefully someone with an SDK can actually look at the nitty gritty and shed some light.

Don't forget that GlovePIE has an autoconnect feature built into it, that is only compatible with BlueSoleil. Once GlovePIE is running, just press 1+2 to connect, and you can press the power button on the wiimote to disconnect(this won't affect your wii in the area).

Another alternative that I have adapted is to set Thex's WiimoteConnect to launch a macro I made when it connects. The macro flips a variable in an automation script that presses the "Connect" button over and over at 10 seconds apart. What this does is have my computer always looking for a wiimote, and stop looking when it finds one. This sounds complicated and unnecessary, but after I set it up it just runs, and between the automation program and WiimoteConnect, it takes up maybe %1 of the CPU, which isn't too bad. Still, in the future, a permanent connection is really the only answer.

Is Thex here?

It was my understanding that WiimoteConnect uses the Windows bluetooth stack API(possibly a hacked version, as someone mentioned). I was wondering if maybe the API itself lets you pass a PIN in hex or binary, or if it is limited to ASCII as well.

Anyway, at the moment, passing a binary key through an existing stack seems like the only viable solution.
BlueSoleil seems perfect, since they have already shown they are willing to listen, and work toward making using the Wiimote easier to connect. In fact, they can build it into their Gamii add-on. Hopefully, if BlueSoleil were to do it, maybe other competitors would take notice, and at least allow it to be done through the API.

So, any response from them yet?

Bluetooth & Connectivity Knowledge Center / "Catch-all" mode?
« 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: . 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).

Pages: 1