WiiMouse - Revision history

Lynch: /* Components */

2008-03-23T20:39:51Z

Components

Lynch: /* Components */

2008-03-23T20:38:39Z

Components

Lynch: /* Components */

2008-03-23T20:38:11Z

Components

MichaelKryger: /* Reflection and Future Changes */

2008-03-19T23:46:45Z

Reflection and Future Changes

MichaelKryger: /* Results */

2008-03-19T23:45:55Z

Results

MichaelKryger: /* Files */

2008-03-19T23:44:53Z

Files

MichaelKryger: /* Files */

2008-03-19T23:43:51Z

Files

MichaelKryger: /* Files */

2008-03-19T23:43:01Z

Files

MichaelKryger: /* Files */

2008-03-19T23:41:34Z

Files

MichaelKryger: /* The WiiMouse */

2008-03-19T23:39:14Z

The WiiMouse

@@ Line 129: / Line 129: @@
 <u>Notes</u>:
-More information on the accelerometers can be found [http://hades.mech.northwestern.edu/wiki/index.php/Accelerometers here] or [[Accelerometers|here]].
+More information on the accelerometers can be found [[Accelerometers|here]].
 More information on Xbee communication can be found [http://hades.mech.northwestern.edu/wiki/index.php/XBee_radio_communication_between_PICs here].

@@ Line 129: / Line 129: @@
 <u>Notes</u>:
-More information on the accelerometers can be found [http://hades.mech.northwestern.edu/wiki/index.php/Accelerometers here] or [Accelerometers|here].
+More information on the accelerometers can be found [http://hades.mech.northwestern.edu/wiki/index.php/Accelerometers here] or [[Accelerometers|here]].
 More information on Xbee communication can be found [http://hades.mech.northwestern.edu/wiki/index.php/XBee_radio_communication_between_PICs here].

@@ Line 129: / Line 129: @@
 <u>Notes</u>:
-More information on the accelerometers can be found [http://hades.mech.northwestern.edu/wiki/index.php/Accelerometers here].
+More information on the accelerometers can be found [http://hades.mech.northwestern.edu/wiki/index.php/Accelerometers here] or [Accelerometers|here].
 More information on Xbee communication can be found [http://hades.mech.northwestern.edu/wiki/index.php/XBee_radio_communication_between_PICs here].

← Older revision		Revision as of 23:46, 19 March 2008
Line 439:		Line 439:
	===Reflection and Future Changes===		===Reflection and Future Changes===

	Something to think about for future applications would be increasing the level of sophistication for positioning. While interpreting position based on acceleration is quite difficult, it would be possible to add other sensors to allow for a greater level of precision and positioning capability. One option may be to employ a MEMS gyrometer in a addition to the onboard accelerometer to interpret the pitch, roll, and yaw of the device. Of course, an obvious answer may be to use an approach similar to that of Nintendo and employ infrared sensing as a positioning tool. Generally speaking, the key to increasing the level of precision for the cursor on the Windows side is increasing the precision and data range of the positioning system used in the WiiMouse. With simple sensing based on changes in the gravitational component of acceleration, it will be quite difficult to increase the level of precision beyond what it currently is.		Something to think about for future applications would be increasing the level of sophistication for positioning. While interpreting position based on acceleration is quite difficult, it would be possible to add other sensors to allow for a greater level of precision and positioning capability. One option may be to employ a MEMS gyrometer in addition to the onboard accelerometer to interpret the pitch, roll, and yaw of the device. Of course, an obvious answer may be to use an approach similar to that of Nintendo and employ infrared sensing as a positioning tool. Generally speaking, the key to increasing the level of precision for the cursor on the Windows side is increasing the precision and data range of the positioning system used in the WiiMouse. With simple sensing based on changes in the gravitational component of acceleration, it will be quite difficult to increase the level of precision beyond what it currently is.

@@ Line 435: / Line 435: @@
 Overall, the final WiiMouse design offered a reasonably reliable human interface with Windows. Most users were quite capable of adapting to controlling the cursor with the device in a very short time, indicating the design was fairly intuitive. The end result was a mouse that functioned reliably and was capable of a reasonable level of precision.
-The decision to allow MATLAB to complete the number crunching for determining cursor position was perhaps the most important aspect of completing a functional mouse algorithm, as on PIC calculations resulted in great difficulty and egregious errors. Simplification of the system used to determine cursor movement also greatly aided in allowing for successfully implementing a WiiMouse.
+The decision to allow MATLAB to complete the number crunching for determining cursor position was perhaps the most important aspect of completing a functional mouse algorithm, as the PIC calculations resulted in great difficulty and egregious errors. Simplification of the system used to determine cursor movement also greatly aided in allowing for successfully implementing a WiiMouse.
 ===Reflection and Future Changes===

@@ Line 19: / Line 19: @@
 ==Files==
-Here is the code that was written for the Wiimouse. The c code should be programmed to the PIC, while wiimouse.m can be run in Matlab.
+Here is the code that was written for the Wiimouse. The c code should be programmed to the PIC. Wiimouse.m can be run in Matlab by typing 'wiimouse' into the command window, but it must be in the same folder as Wiimouse.fig.
 [http://hades.mech.northwestern.edu/wiki/images/1/12/Wiimouse.m Wiimouse.m]
 [http://hades.mech.northwestern.edu/wiki/images/6/6b/Wiimouse.fig Wiimouse.fig]

@@ Line 22: / Line 22: @@
 [http://hades.mech.northwestern.edu/wiki/images/1/12/Wiimouse.m Wiimouse.m]
 [http://hades.mech.northwestern.edu/wiki/images/6/6b/Wiimouse.fig Wiimouse.fig]
+[http://hades.mech.northwestern.edu/wiki/images/0/0b/Wiimouse.c Wiimouse.c]
 ==Electrical Design==