|
||||||||
|
||||||||
| Cette page est aussi disponible en français | ||||||||
| Project overview | [hide] |
Someone requested that I convert an Intellivision 1 controller to USB. The result
can be seen on the picture on the left. As usual, everything is open-source so you'll
find schematics and source code on this page.A fun part of this project is the fact that I've had no choice but to figure out how the controller worked by myself. I did some research, but could not find any pertinent information about how it worked. But fear not! I have taken the time to create an how it works section to detail my findings. The key features of the result are:
|
| Schematic | [hide] |
Here is the schematic:![]() A table matching pin numbers to wire colors is given in the how it works section. Important: Keep in mind that the pin numbers are for Intellivision 1 controllers only! At the moment, I have no idea what the pinout for other similar controllers would be. If you wish to try a different controller, I suggest that you use the information in the how it works section and compare with your controller. Be sure to contact me with your results! Component list:
For the USB connection, just strip the USB cable and solder the wires directly to the board. USB uses standard wire colors:
|
| Programming the microcontroller | [hide] |
| A microcontroller is a component which must be programmed in order to do
something useful. So here is the hexfile which must be flashed into the microcontroller: intellivusb-1.0.hex Many microcontrollers have what is called 'Fuse bytes'. In the case of the ATmega8, there are two bytes: The high byte, and the low byte. Those bytes are used to configure some aspects of the microcontroller. What type of clock to use? Crystal? Resonator? Internal RC clock? Allow programming via ISP? It's very important to set the fuses to the right values. Using the wrong values can render your MCU unusable. For this project, here are the appropriate fuse values: high byte = 0xc9, low byte = 0x9f For details about how to program an AVR, visit my AVR programming page. |
| Source code | [hide] |
| The source code is released under the GPL license and compiles with avr-gcc. To prevent conflicts,
please do not distribute modified version where the USB report descriptor has
been modified without replacing the USB Vendor ID and Product ID by yours. intellivusb-1.0.tar.gz |
| Circuit board for surface-mount version | [hide] |
The surface-mount version uses my Multiuse PCB2 circuit.
Here's what it looks like:
|
| How it works | [hide] |
| I tried to find information about the controller on the net before beginning
this project but I could not find anything useful. So I had no other choice than
to figure out how the controller worked by myself, which was quite fun. Here's how
it works (at least to my understanding). The controller has 12 buttons organized in a way similar to a telephone keypad, 4 buttons on the sides (The top buttons on each side perform the same function), and a rotating disc. The rotating disc and the 12 'telephone' buttons cannot be used at the same time. The controller I used (Intellivision 1) had 9 wires and a connector meant to be connected directly to the console's main board. Here's the wire number/color relation table:
Considering that only 9 wires are used without electronic components inside the controller, it is obvious that the buttons are organized as a matrix. This means that they must be scanned in software. Here's a table I built showing which wires are used: ![]() The disc is capable of 16 different directions. The current direction is output using 6 wires (#2 to #6, #1 as common). As you can see, these are in conflict with the 'telephone' buttons. This is why the 'telephone' buttons and rotating disc are not usable together. Notice also that there is always only 1 bit of difference between adjacent directions. Does it remind you of Grey code?
![]() The middle direction is encoded simply by leaving wires #2 to #6 not connected with #1.
|