« previous next »
Pages: 1 2 3 4 5 6

Author Topic: WiimoteConnect 0.6 (support for autoconnect)  (Read 238878 times)

Offline Stepko

  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Reply #45 on: May 05, 2009, 02:26:42 PM
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
« Last Edit: May 05, 2009, 02:59:05 PM by Stepko »


Offline achillez

  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Reply #46 on: May 11, 2009, 06:56:45 PM
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.


Offline yokokingdommusic

  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Reply #47 on: May 14, 2009, 01:42:32 PM
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


Offline Misha

  • *
  • Posts: 29
  • Karma: +0/-0
    • View Profile
    • CPP TEA
Reply #48 on: May 21, 2009, 04:05:58 AM
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.

++

Offline Ron F

  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
Reply #49 on: June 06, 2009, 01:22:04 AM
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


Offline Ron F

  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
Reply #50 on: June 09, 2009, 07:11:17 PM
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

I'd hope that you choose an accommodating license, such as "Attribution Share Alike".

Cheers,
Ron


Offline Daws

  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Reply #51 on: June 21, 2009, 05:03:47 AM
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


Offline Misha

  • *
  • Posts: 29
  • Karma: +0/-0
    • View Profile
    • CPP TEA
Reply #52 on: July 02, 2009, 03:35:51 AM
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, 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)

++

Offline mcram

  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
Reply #53 on: August 07, 2009, 04:59:14 PM
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.


Offline Misha

  • *
  • Posts: 29
  • Karma: +0/-0
    • View Profile
    • CPP TEA
Reply #54 on: August 09, 2009, 07:02:31 AM
Since they still didn't fix the board, 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.

++

Offline jvolzer

  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Reply #55 on: August 31, 2009, 11:41:27 AM
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? 


Offline Aqualung

  • *
  • Posts: 8
  • Karma: +0/-0
    • View Profile
Reply #56 on: November 08, 2009, 02:42:46 PM
Anybody tried WiimoteConnect in Windows 7 x64? Do you need GlovePie?


Offline amelsfort

  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Reply #57 on: November 16, 2009, 04:58:42 AM
Quote from: Aqualung on November 08, 2009, 02:42:46 PM
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.


Offline Aqualung

  • *
  • Posts: 8
  • Karma: +0/-0
    • View Profile
Reply #58 on: November 16, 2009, 09:00:18 AM
Quote from: amelsfort on November 16, 2009, 04:58:42 AM
Quote from: Aqualung on November 08, 2009, 02:42:46 PM
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.
Quote
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?


Offline amelsfort

  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Reply #59 on: November 16, 2009, 10:20:28 AM
Quote from: Aqualung on November 16, 2009, 09:00:18 AM
Quote from: amelsfort on November 16, 2009, 04:58:42 AM
Quote from: Aqualung on November 08, 2009, 02:42:46 PM
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.
Quote
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.


Pages: 1 2 3 4 5 6
« previous next »