Author Topic: Possible to use 2 wiimotes?  (Read 28329 times)

Offline taitrt

  • *
  • Posts: 15
  • Karma: +1/-0
    • View Profile
on: January 28, 2008, 04:21:31 PM
So, I've started using the wiimote whiteboard in my classroom, and I love it.  However, some of my students do not fully comprehend the fact that the wiimote has to be able to see the IR pen.  Sometimes they stand in front of the wiimote and their writing gets broken up where the wiimote loses track of the IR reflection.

Would it be possible to use 2 wiimotes so even when they stood in front of one the other one would still be able to pick up the IR reflection?

I am not a programmer and don't claim to be, but this seems like a great idea that would make the wiimote whiteboard much more practical to use.



Offline Thisisjon

  • *
  • Posts: 20
  • Karma: +0/-0
    • View Profile
Reply #1 on: February 02, 2008, 05:58:43 PM
I would assume so. The program says wiimote (A), so I would think that you could easily have a wiimote (B). Youd probably have to calibrate each wiimote individually. As long as you dont move the wiimotes it should work. I'll try using 2 wiimotes soon and see if it works well.



Offline Thisisjon

  • *
  • Posts: 20
  • Karma: +0/-0
    • View Profile
Reply #2 on: February 04, 2008, 05:32:08 PM
An error occurs. :-[ But maybe someone could fix that, because using two wiimotes would be helpful



Offline gabort

  • *
  • Posts: 39
  • Karma: +3/-0
    • View Profile
Reply #3 on: February 04, 2008, 05:47:41 PM
You know, if we had a race for uninformative posts, that one is a favorite.

What error? When?

I think it would indeed be a nice thing if we could have two wiimotes, but I suspect that both controlers show up as one and the same thing in BlueSoleil... Could that be the source of your error?

I'm just wandering, since "an error" is simply impossible to fix.



Offline RiXtEr

  • *
  • Posts: 20
  • Karma: +1/-0
    • View Profile
Reply #4 on: February 04, 2008, 08:39:54 PM
Here is the start of a 2 wiimote whiteboard (hopefully there isn't anyone else working on this so I'm not reinventing the wheel). It errors out when you try to calibrate. I am not sure how to tackle that part of it yet. If anyone is able to help or give me some insight on that I would really appreciate it. This must be ran from within visual studio the compiled programs are Mr. Lee's work as is most of the source code. I am also planning on the wiimote software minimizing to tray and a single left click on that icon will make the next click a right click (that should solve the right click issue). I am looking for software to pull up an on screen keyboard as well if anyone has some suggestions.

Thanks for the wonderful work Johnny Lee.

http://www.weaubleau.k12.mo.us/~ricky.nance/wiimote/2wiimotes-whiteboard.zip
« Last Edit: February 04, 2008, 08:43:30 PM by RiXtEr »



Offline insomnia

  • *
  • Posts: 26
  • Karma: +3/-0
    • View Profile
Reply #5 on: February 10, 2008, 11:46:23 AM
You know, if we had a race for uninformative posts, that one is a favorite.

What error? When?

I think it would indeed be a nice thing if we could have two wiimotes, but I suspect that both controlers show up as one and the same thing in BlueSoleil... Could that be the source of your error?

I'm just wandering, since "an error" is simply impossible to fix.

both controllers show up as different divices ive had 3 controllers conected and it showed 3 different wiimotes.

for this to work you need to have 1 primary(active) and 1 secondary(passive) controller, if the 1st controller looses the IRled the secondary controller becomes active and reads the IRled. And when the 1st controller finds the led again the 2nd one becomes passive again.

you need to modify alot of the code to make this work, but it is possible.



Offline Thisisjon

  • *
  • Posts: 20
  • Karma: +0/-0
    • View Profile
Reply #6 on: February 11, 2008, 10:03:35 PM
any chance you could put that code up? because that could be really helpful.



Offline atomriot

  • *
  • Posts: 177
  • Karma: +16/-0
    • View Profile
Reply #7 on: February 11, 2008, 10:28:09 PM
any chance you could put that code up? because that could be really helpful.

dang, i cant even think of anything witty to say right now either

http://www.wiimoteproject.com/wiimote-and-bluetooth-connectivity/two-wiimotes-at-a-time-strange-behaviour-t244.0.html#msg1197

i have not tried this yet but they sound confident.

Details, details. Things to do. Things to get done. Don't bother me with details, just tell me when they're done.
--
James Lionel Price



Offline insomnia

  • *
  • Posts: 26
  • Karma: +3/-0
    • View Profile
Reply #8 on: February 12, 2008, 09:35:07 AM
any chance you could put that code up? because that could be really helpful.

dang, i cant even think of anything witty to say right now either

http://www.wiimoteproject.com/wiimote-and-bluetooth-connectivity/two-wiimotes-at-a-time-strange-behaviour-t244.0.html#msg1197

i have not tried this yet but they sound confident.

From what i have read this gives you two distinct wiimotes, but they both wil be sending pointer information, no you have to enable the second one when you first one loosses sight. And then you'll have a redundent wiimote settup.



Offline bytepusher

  • *
  • Posts: 2
  • Karma: +1/-0
    • View Profile
Reply #9 on: February 12, 2008, 01:47:10 PM
I was thinking about using two or more wiimotes in order to increase accuracy. I'm not sure if this would be the best algorithm, but why not average the position of the cursor between X number of wiimotes? Also, why not keep wiimote references in an array, so that we're not having abcd, but wiimote{{1,2,3,4}], so serious redundancy and accuracy can be achieved? I started looking through the code, but I'm new to C#(shouldn't be hard since I know C++ well).



Offline insomnia

  • *
  • Posts: 26
  • Karma: +3/-0
    • View Profile
Reply #10 on: February 12, 2008, 03:16:26 PM
I was thinking about using two or more wiimotes in order to increase accuracy. I'm not sure if this would be the best algorithm, but why not average the position of the cursor between X number of wiimotes? Also, why not keep wiimote references in an array, so that we're not having abcd, but wiimote{{1,2,3,4}], so serious redundancy and accuracy can be achieved? I started looking through the code, but I'm new to C#(shouldn't be hard since I know C++ well).

It's sound good, i was thinking of passive redundancy where the second wiimote stays passive till the first looses sight. But i think your solution will work better plus it has extra accuracy. It uses more CPU power but it wouldn't be much.

I started looking at the code myself i have little experience in C# but im learning pretty fast.



Offline RiXtEr

  • *
  • Posts: 20
  • Karma: +1/-0
    • View Profile
Reply #11 on: February 14, 2008, 03:06:31 PM
I was thinking about using two or more wiimotes in order to increase accuracy. I'm not sure if this would be the best algorithm, but why not average the position of the cursor between X number of wiimotes? Also, why not keep wiimote references in an array, so that we're not having abcd, but wiimote{{1,2,3,4}], so serious redundancy and accuracy can be achieved? I started looking through the code, but I'm new to C#(shouldn't be hard since I know C++ well).

Sounds like a good idea, did you check out the code I submitted in my previous post? Everything is there except the pointer calibration stuff (the main part I guess :D ). If someone could figure that out (or help me figure it out, I am a c# newbie too!) that would be very helpful. I have 4 wiimotes if someone needs a tester.



Offline insomnia

  • *
  • Posts: 26
  • Karma: +3/-0
    • View Profile
Reply #12 on: February 17, 2008, 11:14:01 AM
I was thinking about using two or more wiimotes in order to increase accuracy. I'm not sure if this would be the best algorithm, but why not average the position of the cursor between X number of wiimotes? Also, why not keep wiimote references in an array, so that we're not having abcd, but wiimote{{1,2,3,4}], so serious redundancy and accuracy can be achieved? I started looking through the code, but I'm new to C#(shouldn't be hard since I know C++ well).

Sounds like a good idea, did you check out the code I submitted in my previous post? Everything is there except the pointer calibration stuff (the main part I guess :D ). If someone could figure that out (or help me figure it out, I am a c# newbie too!) that would be very helpful. I have 4 wiimotes if someone needs a tester.

I've downloaded your code, checking it out now. Im gonna try so thing tonight/tommorow, i just need to setup a second wiimote for some testing(i dont know where to place it ;) ). But i hope i have some testing stuff finisched tomorrow.



Offline jon

  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
Reply #13 on: February 23, 2008, 04:18:12 AM
Just my 2 cents- but I think for having multiple wiimotes you would want all of them to calibrate simultaneously and you would want them both to be on at all times, this way one doesn't need to 'turn on' when one loses sight of the IR input.  Both inputs will, if calibrated correctly, map to the same point for both wiimotes- so the inputs should be the same. 

Looking at the source it seems the app tracks the state of the mouse clicks by changing the status of the IR state.  I think the difference here would be that the actual mouse state would be changed only when both wiimotes show dark or if either becomes lit (from a previous state of both dark).




Offline balam

  • *
  • Posts: 58
  • Karma: +1/-1
    • View Profile
Reply #14 on: March 10, 2008, 11:19:02 AM
did you made it work.
if so 2 wii will be amazing.