Wiimote - Revision history

MakoBot: Robot: Cosmetic changes

2012-03-04T04:20:11Z

Robot: Cosmetic changes

MakoBot: Removed 'Template:' prefix from template includings and/or changed external-link into internal-link

2011-06-10T23:48:10Z

Removed 'Template:' prefix from template includings and/or changed external-link into internal-link

Makopoppo at 10:07, 3 January 2011

2011-01-03T10:07:51Z

Makopoppo at 09:10, 3 January 2011

2011-01-03T09:10:09Z

Makopoppo at 08:13, 3 January 2011

2011-01-03T08:13:11Z

Makopoppo: Wiimote was replaced with wiimote plus, probably compatible with old one

2011-01-03T06:50:40Z

Wiimote was replaced with wiimote plus, probably compatible with old one

Ideia Boa at 00:43, 22 May 2009

2009-05-22T00:43:58Z

Phrearch: small fix

2009-01-07T15:46:13Z

small fix

Phrearch: structured text

2009-01-07T15:43:01Z

structured text

Phrearch at 15:36, 7 January 2009

2009-01-07T15:36:35Z

@@ Line 3: / Line 3: @@
 <br />
-==Overview==
+== Overview ==
 You can use the Wiimote(Plus) and the nunchuck for controlling the viewer. Using a wiimote, one has a powerful freehand 3d-controller which has all the options to navigate freely when in a presentation situation. The software used is [http://abstrakraft.org/cwiid/ cwiid]. Cwiid lets you control the accelerometer, the ir-camera, and every button on the wiimote and nunchuck through the use of config-files. The hardware used: 1 Wiimote(~40 euro), 1 nunchuck(~20 euro), 1 wireless wiibar(~15 euro), and a bluetooth dongle(~10 euro).
-==Procedure==
+== Procedure ==
 * Install the bluez libraries (libbluetooth3 and libbluetooth-dev)
 * Run the bluetooth daemon
@@ Line 19: / Line 19: @@
 make install
 </source>
-*Or you can simply download wminput and wmgui via apt-get or so.
+* Or you can simply download wminput and wmgui via apt-get or so.
 <source lang="bash">
 apt-get install wminput wmgui
@@ Line 28: / Line 28: @@
   vi /usr/local/etc/cwiid/wminput/opensim
 </source>
-===Wiimote-Only===
+=== Wiimote-Only ===
-There are basically 4 essential keys that the viewer uses, but the wiimote interface is not really suited to control 4 buttons within the hand's normal reach. So - lets have a look at that configfile again - you can see that the right mouse-button is out of alignment with your normal handposition on the wiimote. You normally won't use that button(option menu) as often as the other onces. The buttons within reach are all configured to control the way you position the camera.  A-Button is mouse leftclick(select object, select pivot-point), The B-Button is yaw, and digital-down is pitch.
+There are basically 4 essential keys that the viewer uses, but the wiimote interface is not really suited to control 4 buttons within the hand's normal reach. So - lets have a look at that configfile again - you can see that the right mouse-button is out of alignment with your normal handposition on the wiimote. You normally won't use that button(option menu) as often as the other onces. The buttons within reach are all configured to control the way you position the camera. A-Button is mouse leftclick(select object, select pivot-point), The B-Button is yaw, and digital-down is pitch.
 <source lang="bash">
 #ir_ptr
@@ Line 42: / Line 42: @@
 </source>
-===Wiimote-Nunchuck===
+=== Wiimote-Nunchuck ===
 With a nunchuck we can relieve the moving-controls to the analogue controller. Also, the down-button linked to left-ctrl is somewhat a hack. It works, but it's not the most natural approach possible. The wiimote-nunchuck configuration:
 <source lang="bash">
@@ Line 49: / Line 49: @@
 Plugin.ir_ptr.X = ~ABS_X
 Plugin.ir_ptr.Y = ~ABS_Y
-Wiimote.A       = BTN_LEFT
+Wiimote.A = BTN_LEFT
-Wiimote.B       = KEY_LEFTALT
+Wiimote.B = KEY_LEFTALT
-Nunchuk.C       = KEY_LEFTSHIFT
+Nunchuk.C = KEY_LEFTSHIFT
-Nunchuk.Z       = KEY_LEFTCTRL
+Nunchuk.Z = KEY_LEFTCTRL
-Wiimote.Up      = KEY_PAGEUP
+Wiimote.Up = KEY_PAGEUP
-Wiimote.Down    = KEY_PAGEDOWN
+Wiimote.Down = KEY_PAGEDOWN
-Wiimote.Left    = KEY_LEFT
+Wiimote.Left = KEY_LEFT
-Wiimote.Right   = KEY_RIGHT
+Wiimote.Right = KEY_RIGHT
-Wiimote.Plus    = BTN_RIGHT
+Wiimote.Plus = BTN_RIGHT
-Wiimote.Minus   = KEY_B
+Wiimote.Minus = KEY_B
-Wiimote.Home    =KEY_M
+Wiimote.Home =KEY_M
-#Wiimote.1      = KEY_PROG1
+#Wiimote.1 = KEY_PROG1
-#Wiimote.2      = KEY_PROG2
+#Wiimote.2 = KEY_PROG2
-Plugin.nunchuk_stick2btn.Up     = KEY_UP
+Plugin.nunchuk_stick2btn.Up = KEY_UP
-Plugin.nunchuk_stick2btn.Down   = KEY_DOWN
+Plugin.nunchuk_stick2btn.Down = KEY_DOWN
-Plugin.nunchuk_stick2btn.Left   = KEY_LEFT
+Plugin.nunchuk_stick2btn.Left = KEY_LEFT
-Plugin.nunchuk_stick2btn.Right  = KEY_RIGHT
+Plugin.nunchuk_stick2btn.Right = KEY_RIGHT
 </source>
 ''Notice the Plugin.nunchuck_stick2btn, which is only in the git-version of cwiid.''

@@ Line 1: / Line 1: @@
 __NOTOC__
-{{Template:Quicklinks}}
+{{Quicklinks}}
 <br />

@@ Line 68: / Line 68: @@
 Plugin.nunchuk_stick2btn.Right  = KEY_RIGHT
 </source>
-''Notice the Plugin.nunchuck_stick2btn, which is only in the svn-version of cwiid.''
+''Notice the Plugin.nunchuck_stick2btn, which is only in the git-version of cwiid.''
 * Load the uinput kernel module

@@ Line 7: / Line 7: @@
 ==Procedure==
-* Install the bluez libraries
+* Install the bluez libraries (libbluetooth3 and libbluetooth-dev)
 * Run the bluetooth daemon
 * Download and compile cwiid from git
@@ Line 13: / Line 13: @@
 git clone https://github.com/abstrakraft/cwiid.git
 cd ./cwiid
-atlocal
+aclocal
 autoconf
 ./configure
 make
 make install
 </source>
- Or you can directory download wminput and wmgui via apt-get or so.
+*Or you can simply download wminput and wmgui via apt-get or so.
 * Make a new configuration file for wminput, and fill with the wiimote-only or wiimote-nunchuck(prefered) setup

@@ Line 9: / Line 9: @@
 * Install the bluez libraries
 * Run the bluetooth daemon
-* Download and compile cwiid svn
+* Download and compile cwiid from git
 <source lang="bash">
-svn co http://abstrakraft.org/cwiid/svn/trunk cwiid
+git clone https://github.com/abstrakraft/cwiid.git
-cd /cwiid
+cd ./cwiid
-autoreconf
+atlocal
-./configure --libdir=/usr/lib
+autoconf
 make
 make install
 </source>
 * Make a new configuration file for wminput, and fill with the wiimote-only or wiimote-nunchuck(prefered) setup
 <source lang="bash">

← Older revision		Revision as of 00:43, 22 May 2009
Line 1:		Line 1:
		+	__NOTOC__
		+	{{Template:Quicklinks}}
		+	<br />
		+
	==Overview==		==Overview==
	You can use the Wiimote and the nunchuck for controlling the viewer. Using a wiimote, one has a powerful freehand 3d-controller which has all the options to navigate freely when in a presentation situation. The software used is [http://abstrakraft.org/cwiid/ cwiid]. Cwiid lets you control the accelerometer, the ir-camera, and every button on the wiimote and nunchuck through the use of config-files. The hardware used: 1 Wiimote(~40 euro), 1 nunchuck(~20 euro), 1 wireless wiibar(~15 euro), and a bluetooth dongle(~10 euro).		You can use the Wiimote and the nunchuck for controlling the viewer. Using a wiimote, one has a powerful freehand 3d-controller which has all the options to navigate freely when in a presentation situation. The software used is [http://abstrakraft.org/cwiid/ cwiid]. Cwiid lets you control the accelerometer, the ir-camera, and every button on the wiimote and nunchuck through the use of config-files. The hardware used: 1 Wiimote(~40 euro), 1 nunchuck(~20 euro), 1 wireless wiibar(~15 euro), and a bluetooth dongle(~10 euro).