Author Topic: Keyboard Emulator (Read 7829 times)

slinger · « **on:** March 15, 2003, 02:12:38 pm »

I've recenty built a DIYS keyboard emulator and I'm thiniking of making it open source, I was curious how many of you are able/would be willing to make thier own boards?

Features:
32 buttons (can go higher if needed, up to 96)
no ghosting
Keyboard in and out
userdefined keys
user set repeat rate
low parts count (30)

Let me know if you're interested

Ron

Xphile · « **Reply #1 on:** March 15, 2003, 04:35:37 pm »

open source? like 'free plans on a webpage' open source?

heck, more options is always a good thing..:-)

slinger · « **Reply #2 on:** March 15, 2003, 04:51:21 pm »

Quote from: Xphile on March 15, 2003, 04:35:37 pm

open source? like 'free plans on a webpage' open source?

heck, more options is always a good thing..:-)

Yes open source like free plans, when I was first starting to build this thing I noticed that there wasn't really a lot out there that was free, So I figured I'd make one!

The only thing is that's it's in Rev 1 so there might be problems that I don't know of yet, but being open source maybe others can find and fix them as well.
If there is enough interest I'll set up a webpage for the circuit.
Also if there are other options you'd like to see added then let me know, I have lots of program space still available!

It's based on a PIC 16F874 and the development software is free from microchip.

anthony691 · « **Reply #3 on:** March 15, 2003, 05:00:25 pm »

Cool, go for it.

IG-88 · « **Reply #4 on:** March 15, 2003, 08:53:50 pm »

Absolutely man! Free good, learning good, can't lose!

_Iz- · « **Reply #5 on:** March 15, 2003, 09:40:08 pm »

I would be incredibly interested in seeing it.

Mamezilla · « **Reply #6 on:** March 15, 2003, 10:52:29 pm »

Me too.

BobA · « **Reply #7 on:** March 15, 2003, 10:56:03 pm »

I would be very interested in seeing an open source unit become available. Gives everyone more options.

BobA

OSCAR · « **Reply #8 on:** March 15, 2003, 11:09:45 pm »

This would be a nice contribution, I love seeing projects like this! There is a similar project, http://surf.to/buttonbox, but I have seen very few projects that use a ButtonBox.

I remember one time someone made a handful of ButtonBox's and offered them for sale on the Buy/Sell board, but it seems they only received negative feedback for their effort. Not that this has to do anything with your post, I'm just throwing it out there, FWIW....

Tiger-Heli · « **Reply #9 on:** March 17, 2003, 06:55:23 am »

Would like to see details on this.

A few random thoughts - one of the big drawbacks (guessing?) is that the cost to make a single PCB will be much greater than the cost to make PCB's in bulk.

You might contact Druin at http://members.rogers.com/druins22/ls30/ for advice/hints. He is currently only selling completed units, but he used to be selling kits for the rotary encoders.

Also, the I-PAC and KeyWiz are both selling well, so there is a market for completed encoders.

FWIW

slinger · « **Reply #10 on:** March 17, 2003, 11:24:00 am »

I realize that but I'm not thinking of the average joe here I'm pointing towards those that have the knowledge and material to make thier own boards already, I'm affereing the design and software, they will also have to program the Micro on thier own.

But if people are willing I can get a run of boards made up and it would be cheaper, I may even be able to program the chips for them if they prepay everything, not sure if the cost of that would make it worth it or not.

I have the circuit on a breadboard right now and it works fine, I've already designed the PCB and I'll make it tonight, I'll also try and get the Website up and running tonight if I have time
Ron

rampy · « **Reply #11 on:** March 17, 2003, 12:05:01 pm »

Hey,

I just wanted to throw in my encouragement as well... I think another keyboard emulator is a "good thing" and an "open source" DIY was is great as well.

I'm certainly "able" to do a simple circuit (either on breadboard or a one-off home brew etching =P)

At the moment I don't have a need as I have a keywhiz that I need to integrate into my system...

But in the future who knows... even as just a documentation project it would be cool. *shrug*

rampy

Generic Eric · « **Reply #12 on:** March 17, 2003, 06:45:26 pm »

I would be interested.

Howard_Casto · « **Reply #13 on:** March 18, 2003, 03:47:19 pm »

Don't ask, just post it!

But if you want to know the truth oscar is probably right. It's not a matter of can it be done, it's a matter of does the time and money involved in making one outweight just forking over about 40 bucks to get one premade that you know is going to work. (i know my electronic builds are always a little shakey) You might get 2 or 3 people to actually build one if your luck. But others might learn from the schematics.

SirPoonga · « **Reply #14 on:** March 18, 2003, 03:59:19 pm »

Since he hasn't replied yet, I smell vaporware.

rampy · « **Reply #15 on:** March 18, 2003, 04:21:10 pm »

Quote from: SirPoonga on March 18, 2003, 03:59:19 pm

Since he hasn't replied yet, I smell vaporware.

.... bah! shouldn't you be moderating stuff or something? Nobody calls your "FE" vaporware =P We're all just patiently waiting for your "graphics" guy to do his part. (I know my analogy is a little off - i just think duke nuke 'em forever is vaporware... flying cars are vaporware... it hasn't been *that* long since he posted the initial query. If you look at all of his posts it's not unreasonable to think that he created a keyboard emulator *shrug*

I think any info released publically about what he's found/created would be of value to teh community.

Rampy

slinger · « **Reply #16 on:** March 18, 2003, 05:30:50 pm »

No, it's not vapourware!

The circuit is built and programmed on a breadboard at the moment and works quite well.

I etched the PCB last night, it needs a bit of tweeking (I'm not going to post the PCB without knowing if I made it correctly!! as I stated in one of my posts!)

Plus remember I do work for a living and only have a small amout of free time each day, I will set up the website tonight though, and supply some details of the board.

If I can populate it and prove my PCB design works then that will go up tonight as well.

Ron

BobA · « **Reply #17 on:** March 18, 2003, 06:00:13 pm »

Way to go Slinger. Still looking forward to seeing the info.

BobA

SirPoonga · « **Reply #18 on:** March 18, 2003, 06:40:41 pm »

Quote from: rampy on March 18, 2003, 04:21:10 pm

Quote from: SirPoonga on March 18, 2003, 03:59:19 pm
Since he hasn't replied yet, I smell vaporware.

.... bah! shouldn't you be moderating stuff or something? Nobody calls your "FE" vaporware =P We're all just patiently waiting for your "graphics" guy to do his part. (I know my analogy is a little off - i just think duke nuke 'em forever is vaporware... flying cars are vaporware... it hasn't been *that* long since he posted the initial query. If you look at all of his posts it's not unreasonable to think that he created a keyboard emulator *shrug*

I think any info released publically about what he's found/created would be of value to teh community.

Rampy

Whoa, rampy, take a fricken pill

I wasn't serious. Want to check out my setup wizard for my FE?

slinger · « **Reply #19 on:** March 18, 2003, 07:56:51 pm »

OK here is the vapourware.....

http://home.cogeco.ca/~ron.hayes/main.html

Click on the Projects folder on the right hand side and choose Keyboard Emulator.

For now I ask that you just review the infomation until I can verify that everything is working correctly (unless you want to take that chance!)

I have to drill the board and populate it still before I can test it

SirPoonga · « **Reply #20 on:** March 18, 2003, 08:20:56 pm »

Cool, btw, I fixed the link for you.

rampy · « **Reply #21 on:** March 18, 2003, 09:39:34 pm »

Quote from: SirPoonga on March 18, 2003, 06:40:41 pm

Whoa, rampy, take a fricken pill I wasn't serious. Want to check out my setup wizard for my FE?

*cough* yeah... I ... uh.. knew that. yeah. ha.... er... so how about them mets? These aren't the droids you are looking for...

Thanks for posting the plans, and keep us posted on how the maiden etching / build goes.

Rampy

zorg · « **Reply #22 on:** March 19, 2003, 04:09:52 am »

Quote from: slinger on March 18, 2003, 07:56:51 pm

http://home.cogeco.ca/~ron.hayes/main.html

Click on the Projects folder on the right hand side and choose Keyboard Emulator.

hummm could you please post a direct link ?
I don't (and I could not) use flash

Thanks
Eric

slinger · « **Reply #23 on:** March 19, 2003, 06:46:04 am »

It's not flash it's java.

You can't view it? I think you need to rethink your browser!

Here's the link anyways
http://home.cogeco.ca/~ron.hayes/keyemu.html

Edit: SirPoonga, fixed the link. auto link has issues with ~, click on help above (next to search) to learn how to use the url tag.

zorg · « **Reply #24 on:** March 19, 2003, 07:38:36 am »

Quote from: slinger on March 19, 2003, 06:46:04 am

It's not flash it's java.

You can't view it? I think you need to rethink your browser!

Here's the link anyways
http://home.cogeco.ca/~ron.hayes/keyemu.html

Thank's for the link.
I guees my browser (mozilla) could hanle all kind of pluggins

Eric

Tiger-Heli · « **Reply #25 on:** March 19, 2003, 07:44:10 am »

Hi Slinger,

I took a cursory look at your project, but I'm no electronics expert, so take all my comments with a grain of salt.

Just looking at the circuitry, the PCB design looks very similar to the layout of the buttonbox, as shown here: http://w1.132.telia.com/~u13205992/buttonbox/bbox2/pictures.htm
Note: I said SIMILAR, I realize the actual compnents used are different and am NOT accusing you of copying their design. Mainly I wanted to point out for others that your design will probably have the same features (and drawbacks) as building a ButtonBox.

Other Comments - I notice your design uses Matrix Mode. I am familiar with this from keyboard hacking and usually (with keyboards), you are limited to the number of rows in the matrix (without ghosting/blocking). I.E. a 16x8 matrix keyboard has 16 available key assignments. Since you and ButtonBox both say there are no blocking problems in matrix mode, I assume you have a solution that avoids this.

Most users are more familiar with using direct mode encoders. There is no real problem with Matrix Mode, except, you have to convert things yourself (i.e. input 11 means I want to connect Row 2 and Column 3, etc.)

I realize you are still trying to get the prototype developed, but once this is done, could you post details on how to get 96 inputs with the unit.

Also, I think these would be much more successful if they were available pre-assembled, FWIW!!!

Anyway, thanks for posting the details and I look forward to more information as it becomes available.

slinger · « **Reply #26 on:** March 19, 2003, 06:11:43 pm »

Quote from: Tiger-Heli on March 19, 2003, 07:44:10 am

Hi Slinger,

I took a cursory look at your project, but I'm no electronics expert, so take all my comments with a grain of salt.

Just looking at the circuitry, the PCB design looks very similar to the layout of the buttonbox, as shown here: http://w1.132.telia.com/~u13205992/buttonbox/bbox2/pictures.htm
Note: I said SIMILAR, I realize the actual compnents used are different and am NOT accusing you of copying their design. Mainly I wanted to point out for others that your design will probably have the same features (and drawbacks) as building a ButtonBox.

Other Comments - I notice your design uses Matrix Mode. I am familiar with this from keyboard hacking and usually (with keyboards), you are limited to the number of rows in the matrix (without ghosting/blocking). I.E. a 16x8 matrix keyboard has 16 available key assignments. Since you and ButtonBox both say there are no blocking problems in matrix mode, I assume you have a solution that avoids this.

Most users are more familiar with using direct mode encoders. There is no real problem with Matrix Mode, except, you have to convert things yourself (i.e. input 11 means I want to connect Row 2 and Column 3, etc.)

I realize you are still trying to get the prototype developed, but once this is done, could you post details on how to get 96 inputs with the unit.

Also, I think these would be much more successful if they were available pre-assembled, FWIW!!!

Anyway, thanks for posting the details and I look forward to more information as it becomes available.

My design was made completely from scratch, the reason they look simular (in components not traces) is that you need certain hardware to do the job and we both use those (uC,Max232,headers)

I'm acutally not using a matrix, there are currently 4 common line and 8 data lines (4x8=32) each common line is turned on the the data is scanned seperately then turned off and the next common line is turned on, and so on.

how do I get 96 inputs? there are 8 extra I/O lines unused (actually 9 but that one is open collector) so 4 that I am using + the extra 9 (4+8*8=96), I don't need that many so you are free to edit the PCB to do this yourself.

I couldn't care less how successful it is I built it for my own purposes and not for anyone else. I decided to make it open source, if you want it make it(and edit it)make it, if you don't then just browse.

I'm a little busy right now but I hope to do more on it soon, I only posted the info becasue everyone wanted to see it, I make no claims as to it's functionality yet, the first board had a few errors on it but I fixed them, also my first board didn't turn out as expected the transparency lifted from the board during exposure and the lines became a little fuzzy, so I'm going to make another.

Another thing about the software, I remember that the type-o-matic delay is not set up but is there and the Keyboard in is wired but not polled (the routines are there though)

DJ Gary-N · « **Reply #27 on:** March 19, 2003, 06:46:43 pm »

I do alot of circuit board etching. and would love to have plans to build something like this. So I would be Interested in seeing a schematic and parts list. That would be cool.

Grasshopper · « **Reply #28 on:** March 19, 2003, 07:01:13 pm »

Quote from: slinger on March 19, 2003, 06:11:43 pm

I'm acutally not using a matrix, there are currently 4 common line and 8 data lines (4x8=32) each common line is turned on the the data is scanned seperately then turned off and the next common line is turned on, and so on.

I'm a bit confused, I thought that was how a scanning matrix worked.

Anyway that point aside, your circuit looks very interesting. The more alternatives that builders have the better.

I have been toying with the idea of building a ButtonBox. However I've been put off by the price and difficulty of obtaining the Atmel chip that Leif uses in his design. If I ordered the components from abroad (I live in the UK) over the internet then I believe the total cost would be cheaper than an Ipac but the savings aren't huge.

I have a few questions.

Is the PIC chip you use significantly cheaper than the Atmel, and can it be programmed directly from the parallel port?

Also I'm sure a lot more people would be interested in building the circuit if you designed a layout that could be used with standard stripboard. I doubt many people would want to go to the expense of getting their own board etched.

SirPoonga · « **Reply #29 on:** March 19, 2003, 08:02:55 pm »

Quote from: slinger on March 18, 2003, 07:56:51 pm

OK here is the vapourware.....

http://home.cogeco.ca/~ron.hayes/main.html

Click on the Projects folder on the right hand side and choose Keyboard Emulator.

For now I ask that you just review the infomation until I can verify that everything is working correctly (unless you want to take that chance!)

I have to drill the board and populate it still before I can test it

Could you give suggestions or point to a howto to transfer your plans to pc board:)

Tiger-Heli · « **Reply #30 on:** March 19, 2003, 10:25:31 pm »

Quote from: slinger on March 19, 2003, 06:11:43 pm

My design was made completely from scratch, the reason they look simular (in components not traces) is that you need certain hardware to do the job and we both use those (uC,Max232,headers)

I realize there will be some common components. What I noticed was the physical layout (shape of the PCB, position of the processor and header and LED relative to each other) and the use of matrix mode seemed similar to the ButtonBox. Of course, I've seen other people come up with ideas that were mine originally without my having said anything previously about my ideas, so it happens. . . didn't mean to offend you . . .

Quote

I'm acutally not using a matrix, there are currently 4 common line and 8 data lines (4x8=32) each common line is turned on the the data is scanned seperately then turned off and the next common line is turned on, and so on.

Errmm- as Grasshopper said, what do you mean you aren't using a matrix? It says right on the circuit 1-4 X-Axis, 19-26 Y-Axis, sounds like a matrix to me.

What I mean by matrix is a circuit where each button is connected to one Row pin and one Column pin (or in your terminology, one common line and one data line). The button box and the Hagstrom encoders allow this mode, and I believe the X-Arcade uses it, so it is workable. This is opposed to direct mode used by the I-PAC and KeyWiz (and others) where one terminal of each input goes to a unique encoder input and ALL second terminals go to the SAME Common (GND) terminal.

Quote

how do I get 96 inputs? there are 8 extra I/O lines unused (actually 9 but that one is open collector) so 4 that I am using + the extra 9 (4+8*8=96), I don't need that many so you are free to edit the PCB to do this yourself.

That much I figured. What I meant is that when you or someone with more electronics knowledge than myself has time, it would be nice if they posted what terminals connected to what pins on the microcontroller to make 96 inputs work.

Quote

I couldn't care less how successful it is I built it for my own purposes and not for anyone else. I decided to make it open source, if you want it make it(and edit it)make it, if you don't then just browse.
I'm a little busy right now but I hope to do more on it soon, I only posted the info becasue everyone wanted to see it . . .

Fair enough. Thanks for making the details of your design available. Sorry if I sounded overly critical of your project earlier. I wasn't meaning to be. There are all levels of people on this board, anywhere from "What's a keyboard encoder, and why would I want one?" to "Why is your software written in VB and would you like me to convert it to C++ and add these neat features in while I'm at it?" I'm somewhere in the middle, but I thought pointing out matrix mode and comparing it to the buttonbox would put it on the map for people considering your project instead of an I-PAC/KeyWiz/MK40/Hagstrom, without having to de-cipher the circuitry for themselves.

slinger · « **Reply #31 on:** March 19, 2003, 10:41:40 pm »

I'm glad you mentioned that!

I had figured a way around that but I didn't implement that for the sake of simulation, but I'll add it back in and revise the website.

What I did to take care of that was to not have the inputs set as inputs all the time but to set them as Hi-z, if there is no ground other than the one in use then ghosting cannot happen.

Sorry but I wasn't offended at all, just stating how I felt about it.
As for the matrix, it isn't really a matrix since only one gnd line is active at one time it's more like an addressed buss.

I will post more details for upgrading the PCB on my websitte when I get more time, but I'd suggest that anyone willing to, downloadf the datasheet from Microchip and look to see what pins are free(I didn't hook them up because I didn't feel like finding a route for the extra pins if I didn't need them

Some of the things I'd like to hear back from you guys is what things you'd like to see added to the design. One of the things I forgot to mention is that you don't need any special software to configure it, you talk to the chip through any terminal program and send the value to the chip.(need to send hex though)

slinger · « **Reply #32 on:** March 19, 2003, 10:55:41 pm »

Quote

Quote

Could you give suggestions or point to a howto to transfer your plans to pc board:)

Load the board into Winboard print it out on a transparency, place this over your presensitized board, expose it to florecent light for 5min/side then develop and etch, drill and populate.

Tiger-Heli · « **Reply #33 on:** March 19, 2003, 11:11:50 pm »

Quote from: slinger on March 19, 2003, 10:41:40 pm

I'm glad you mentioned that!
I had figured a way around that but I didn't implement that for the sake of simulation, but I'll add it back in and revise the website.

Mentioned what??? And what did you figure a way around, and what are you adding to the website???

Quote

What I did to take care of that was to not have the inputs set as inputs all the time but to set them as Hi-z, if there is no ground other than the one in use then ghosting cannot happen.
Sorry but I wasn't offended at all, just stating how I felt about it.
As for the matrix, it isn't really a matrix since only one gnd line is active at one time it's more like an addressed buss.

You lost me on the Hi-z and only one ground stuff, but that's okay. I see what you mean about an addressed buss vs. a matrix.

One problem I will have is that I really need something with direct mode (i.e. a common input for all GND terminals). Can your design be modified to support this? And I assume you are limited to 32 inputs in this mode?

EDIT: For those who are wondering why I need direct mode - Matrix mode works fine for a large control panel on an arcade cab. I am building removable panel using DB25 connectors. In direct mode, I can pass 24 inputs through the DB25 cable. In Matrix mode, I have to allow for 8-row pins so I only have 17 inputs to pass through the remaining pins. There are other obstacles, but that's the highlights.

Quote

One of the things I forgot to mention is that you don't need any special software to configure it, you talk to the chip through any terminal program and send the value to the chip.(need to send hex though)

Cool, I meant to mention earlier that it says RS-232 on the PCB, so I assumed it uses the serial port. I'm sure many people would like more details on what information you send and structure/format, etc?

SirPoonga · « **Reply #34 on:** March 19, 2003, 11:15:58 pm »

Quote from: slinger on March 19, 2003, 10:55:41 pm

Quote
Quote

Could you give suggestions or point to a howto to transfer your plans to pc board:)

Load the board into Winboard print it out on a transparency, place this over your presensitized board, expose it to florecent light for 5min/side then develop and etch, drill and populate.

Can you get all this (and the chips and whatever) at radio shack? Dop they have a kit that explains what you just said?

Sorry,m I am an electronics n00b, but I like futzing with this stuff. I;d like to make custom hardware as I can make the software easily enough.

slinger · « **Reply #35 on:** March 20, 2003, 06:39:49 am »

Don't know if radio shack has that stuff or not, I stay away from that place! Waaaaay too expensive, find an electronics store in your area or go to www.mgchemicals.com

Hi-z mean high impedence meaning not an input nor an output, almost like floating with a high resistance.

all you need to do is send the hex byte "0xFF"(255) through the serial port and the chip will send the menu back

Tiger-Heli · « **Reply #36 on:** March 20, 2003, 07:21:42 am »

Quote

quote author=OSCAR link=board=1;threadid=5689;start=0#38631 date=1047787785]
I remember one time someone made a handful of ButtonBox's and offered them for sale on the Buy/Sell board, but it seems they only received negative feedback for their effort. Not that this has to do anything with your post, I'm just throwing it out there, FWIW....

Not hi-jacking the thread here (I hope), but . . .

The only Buy/Sell/Trade post I could find was this one http://www.arcadecontrols.org/yabbse/index.php?board=2;action=display;threadid=1891;start=0

The "negative feedback" came b/c the guy was selling a buttonbox with Jamma connector for 100 Euro's without the designer's permission (for about $30 in electronic components.)

Not that I'm a huge buttonbox fan, but I wanted to point out that the bad press concerned the seller and his methods, and not the operation and function of the buttonbox itself.

Grasshopper · « **Reply #37 on:** March 20, 2003, 02:41:45 pm »

Slinger,

The following link gives a detailed explanation of why ghosting occurs with a scanning matrix.

http://www.dribin.org/dave/keyboard/

I'm 90% certain that your board will suffer from ghosting unless diodes are used. However presumably blocking would not be a problem as that feature is deliberatly built into the software of most keyboard encoders. Fortunately ghosting is the easier of the two problems to solve.

Personally I could live with a scanning matrix if the components are cheap (I'm going to check out the PIC prices in a minute). However circuits that don't use a matrix are generally better for the following reasons:

1. Because all the switches share a common ground there is less wiring to do.

2. Non-matrix circuits can be used with optical controls.

My suggestions for desirable features are as follows:

1. Design a stripboard layout.

2. Use direct mode instead of a matrix (better still offer a choice as with the ButtonBox).

3. Use the cheapest, most easily available components possible. This is the main flaw of the Buttonbox.

4. Incorporate a keyboard pass-through. If you don't want to use up any PIC inputs then perhaps you could incorporate Stephan Hans circuit into your own.

Keep up the good work! I wish I had the knowledge to design a circuit.

Tiger-Heli · « **Reply #38 on:** March 20, 2003, 03:46:01 pm »

This time, I probably will hijack the thread . . .

Quote from: Grasshopper on March 20, 2003, 02:41:45 pm

Slinger,
The following link gives a detailed explanation of why ghosting occurs with a scanning matrix.
http://www.dribin.org/dave/keyboard/
I'm 90% certain that your board will suffer from ghosting unless diodes are used. However presumably blocking would not be a problem as that feature is deliberatly built into the software of most keyboard encoders. Fortunately ghosting is the easier of the two problems to solve.

I would have to agree, although I'm not sure how the hi-z stuff factors into it.

Quote

Personally I could live with a scanning matrix if the components are cheap (I'm going to check out the PIC prices in a minute).

I was just on microchip's website and it looks like they provide free sample chips (up to five different kinds and up to three of each kind per month). Of course this might not last if everyone from this board orders a microcontroller sample

Quote

3. Use the cheapest, most easily available components possible. This is the main flaw of the Buttonbox.

I checked digi-key yesterday and they had all the Buttonbox components for about 75% of the prices shown on the buttonbox site.

Quote

4. Incorporate a keyboard pass-through. If you don't want to use up any PIC inputs then perhaps you could incorporate Stephan Hans circuit into your own.

Errrm, he does - didn't you see the Key IN and Key OUT connections on the circuit board.

Now my questions for all the electronics gurus on the board (I e-mailed the ButtonBox designer, but he hasn't gotten back to me):

The Button Box with the Atmel chip provides 32 inputs, but only 27 are supported in direct mode as shown on his site. Does anyone know how to make the other five inputs work? Does anyone know if it would be possible to design an encoder like the button box, but using two Atmel chips for 64 inputs?

Ideally (really pushing my luck here) anyone know how to make a circuit using two of the PIC processors mentioned on Slinger's site for as many direct-mode inputs as possible???

Grasshopper · « **Reply #39 on:** March 20, 2003, 04:03:51 pm »

Quote from: Tiger-Heli on March 20, 2003, 03:46:01 pm

Errrm, he does - didn't you see the Key IN and Key OUT connections on the circuit board.

You're right! I hadn't bothered clicking on the thumbnail of the circuit board picture because Slinger's site is so slow.

With regards to the Atmel chips, they can be bought fairly cheaply here.

http://www.futurlec.com/

However I'd rather buy locally if at all possible.

Has anyone on this board had a dealings with Futurlec?

Also Tiger-Heli, can you give me digi-key's web address please.


Main	Restorations	Software	Audio/Jukebox/MP3	Everything Else	Buy/Sell/Trade
Project Announcements	Monitor/Video	GroovyMAME	Merit/JVL Touchscreen	Meet Up	Retail Vendors
Driving & Racing	Woodworking	Software Support Forums	Consoles	Project Arcade	Reviews
Automated Projects	Artwork	Frontend Support Forums	Pinball	Forum Discussion	Old Boards
Raspberry Pi & Dev Board	controls.dat	Linux	Miscellaneous Arcade	Wiki Discussion	Old Archives
Lightguns	Arcade1Up	Try the site in https mode		Site News


Unread posts \| New Replies \| Recent posts \| Rules \| Chatroom \| Wiki \| File Repository \| RSS \| Submit news