| View previous topic :: View next topic |
| Author |
Message |
blubi
Joined: 19 Dec 2006 Posts: 1
Digg It |
Posted: Tue Dec 19, 2006 12:55 am Post subject: |
|
|
| m/s² ... it's an acceleration dude |
|
| Back to top |
|
 |
b
Joined: 21 Dec 2006 Posts: 3
Digg It |
Posted: Thu Dec 21, 2006 5:34 pm Post subject: does anyone know how he plots that data? |
|
|
hello everybody,
does anybody know how is he passing the wiimote data to that math library?
how do you pass bluetooth data to apps?
glovePie allows only emulation of keyboards and mouse movements and events. but how do you pass analog, numerical values (ie the acceleration values) for a math library to plot them out (or any other program)?
(sorry if I'm talking windowz)
thanks for your super work with this site
b. |
|
| Back to top |
|
 |
alecool
Joined: 11 Dec 2006 Posts: 18
Digg It |
Posted: Thu Dec 21, 2006 7:27 pm Post subject: |
|
|
You can use math functions in glovePIE. To get the acceleration datas of the wiimote, use RawforceX/Y/Z or RawAccX/Y/Z for the latest release of GlovePIE. You can use cosine and sine functions. I had send a message to the autor of glovePIE about this, the trigo functions use angles in degree when no Pi value is used in it.
Look at the script I posted some messages above.
To get the values in another program, I don't know how to do, but I know someone here did it, search with the keyword "excel", i'm sure you could find something. _________________ French wiimote-on-PC user, so excuse my poor language  |
|
| Back to top |
|
 |
b
Joined: 21 Dec 2006 Posts: 3
Digg It |
Posted: Thu Dec 21, 2006 11:54 pm Post subject: |
|
|
well Kenner suggested to use OSC to pass it to other apps...
and so I did...it works great
one thing wich i think is a bit limitating with the wiimote is the fact that the IR vision field is very restrictive...
do you have any idea on how that can be "extended"...maybe doing some calculations on direction+acceleration to calculate the new point "out of screen" or better said "out of IR field of vision" ???
cheers.
b. |
|
| Back to top |
|
 |
alecool
Joined: 11 Dec 2006 Posts: 18
Digg It |
Posted: Fri Dec 22, 2006 4:19 am Post subject: |
|
|
I read some days ago, before the IR datas were totally supported in GlovePIE, that there was several "windows" of caption for the IR points, 3 vertical windows and 4 horizontal windows, i guess. I wonder if they are all used in GlovePIE or if the datas are the one for one window.
I have made a small 3D program with a sphere moving like the wiimote, the datas are sent through the virtual joystick. And it is right that the IR caption is very restrictive since I can turn the wiimote of an angle of about 30 degrees before the first IR spot is out of range, what have some bad consequences. _________________ French wiimote-on-PC user, so excuse my poor language  |
|
| Back to top |
|
 |
Lykkeliten
Joined: 03 Jan 2007 Posts: 20
Digg It |
Posted: Sun Jan 07, 2007 8:37 pm Post subject: |
|
|
 |
|
| Back to top |
|
 |
alecool
Joined: 11 Dec 2006 Posts: 18
Digg It |
Posted: Wed Jan 10, 2007 9:27 pm Post subject: |
|
|
I guess you wonder why I used IR points instead of acceleration datas to detect the movements of the wiimote. The reason is quite simple : if you move your wiimote very slowly to the right, it won't detect any negative accel on the X axis, because it is moving too slowly to detect any acceleration. If you use IR points, you can detect any movement with any speed you want. Accel datas are good to detect pitch and roll (i guess, i always confuse the words), but not accurate enough to be used in positioning. _________________ French wiimote-on-PC user, so excuse my poor language  |
|
| Back to top |
|
 |
|