Reconfigurable gaming input device: Difference between revisions
m (X(I/O) Reconfigurable Gaming Input Device moved to Reconfigurable Gaming Input Device: Don't put /'s in address names, it creates a page called X(I which is orphaned.) |
m (Reconfigurable Gaming Input Device moved to Reconfigurable gaming input device: Lower case) |
||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 8: | Line 8: | ||
Evanwyk has done some ridiculous stuff with minimalist electronics (pins on a micro sensitive enough to print capacitive sensors straight on the pcb, etc) and might be another good person to hit for tech advice once you have an idea of what you want to build. |
Evanwyk has done some ridiculous stuff with minimalist electronics (pins on a micro sensitive enough to print capacitive sensors straight on the pcb, etc) and might be another good person to hit for tech advice once you have an idea of what you want to build. |
||
== Interested parties == |
|||
* [[User:Abarry|Andy Barry]] - potential project for POE class at [http://www.olin.edu Olin College] |
|||
* [[User:Mchua|Mel Chua]] - willing to serve as OLPC contact, fascinated by the idea of physical reconfigurability using household objects. |
|||
[[Category:Hardware ideas]] |
[[Category:Hardware ideas]] |
||
Latest revision as of 05:19, 3 September 2008
Introduction
The reconfigurable gaming input device would be shipped in kit form, with instructions on how to assemble the device from components. It would most likely be made of a microcontroller (ie PIC or AVR) with a USB interface. The microcontroller would support multiple modes of input. The directions would show different ways to configure the buttons/potentiometers to create a game pad, joystick, or other input device.
The physical hardware might consist of household objects. So a stick of wood could become part of a joystick. A book with buttons attached could be the makings of a gamepad.
The idea is to give the user as much flexibility in the creation of the gaming device as possible, while keeping the cost minimal. You would have to program in a lot of flexibility into the code (different modes, etc. for different devices), make it low-power, rugged, kid-proof, etc. and come up with a good gallery of sample devices and configurations you could build with this kit - I think the last 2 or so weeks of the project term should be spent just using the finished kit and coming up with crazy things to do with it (possibly recruiting a couple of local needham middle schoolers for the ride).
Evanwyk has done some ridiculous stuff with minimalist electronics (pins on a micro sensitive enough to print capacitive sensors straight on the pcb, etc) and might be another good person to hit for tech advice once you have an idea of what you want to build.