Main > Main Forum
Idea for serial connection between control panel and controller module
(1/2) > >>
jjhlk:
(Too verbose? I need to be because I can't explain things very well otherwise. I need the context.)

So I'm thinking about the electronics I'll use when I rebuild my control panel. In the past I swapped out the IPAC for a messy PSOne Controller hack, and it was a huge hassle. And now I can't use the panel on my PC without another one. So I'm going to make the controller interface a module that'll sit outside of the control panel, and they'll communicate with some sort of cable.

But I'm not sure what cable. A parallel port (DB25) seemed good, because I need exactly 25 wires for the microswitches and ground. However, apparantly DB25 cables don't necessarily have 25 wires, and now that I think about it, if I want my interface modules to work on new control panels I might build in the future, I should use a technology with more than 25 connections.

A serial connection seems good. I could use USB or ethernet cable to connect the panel and module.

I'm not entirely sure about the technology. I guess I'll have the interface module generate a clock frequency down the cat5/usb, and the panel will poll each microswitch in turn using a counter and multiplexer, once per sync signal (using the clock). The problem is that I'll need way too many logic gates.

Is there a microcontroller or fpga I should be using instead? And with 24+ microswitches and the counter bits going to the multiplexer, I'll still need to build the multiplexer with logic gates won't I?

Also, to use a USB cable with only the hacked-PSX-PCB/IPAC, will I be able to generate a strong enough signal?

Is this a bad idea? In my ignorance, am I missing something? The parallel port idea is looking boring and unfutureproof now, but it'd be a lot easier.

I suppose I could look for alternate parallel cables... but I need to scratch this itch for a little while first. Maybe IDE cable actually...

Thanks to anyone who can help or bother to read this.
KenToad:
Do you mean for a modular control panel, not sure if I completely get what the dilemma is.  If you're going modular, I used two parrallel port interfaces on my CP for my bartop, basically one parrallel port per player.  Hope that helps.  Good luck.

Cheers,
KenToad
NoOne=NBA=:
If you use 25-pin SCSI cables, they really do HAVE 25 wires.

The easy way to wire it would be to use one half of the SCSI cable to wire the controls, leave that stick out of the control box, wire the other half to the I-pac,  leave it stick out of a project box, and then connect the two with a Female-Female connector.

That way you don't have to worry about soldering all the wires onto a female surface mount jack.

I just did a stand-alone CP that I used a SCSI cable on.
I happened to have an old SCSI card laying around that had the female end complete with ribbon cable though.


Alternately, you could use one 15-pin cable for each player, but getting ones with 15 wires in them might be a problem.

Another solution would be to use an IDE cable to wire all your controls to, and get a KeyWiz Eco w/IDE header on it.
tivogre:
I used 4 DB25 connections.  They connect to 4 parallel extension cables with one end cut off.  All of them had exactly 25 wires:

jjhlk:
Alright, I'm just going to use one DB25 per player. Lousy cables with <25 connections shouldn't even be a problem since my players currently have only 12 microswitches each. For some reason I really wanted to have both players on the same DB25, which is retrospect is a terrible idea...

Still, if anyone has ever used a serial connection between their control panel and the modular interface (eg. PSX hack, IPAC, DC hack, etc), I'd like to hear about it.
Navigation
Message Index
Next page

Go to full version