Hi, Everyone...I am in a bind. Ever since I decided not to use EPIC for my 777 overhead panel, I am have some trouble finding a robust solution to interface roughly 95 switches to the simulator.I have FDS 777 overhead panels, all fully wired to EPIC, but I do not want to tackle all the programming. I have hit my limit. I would rather re-wire the whole lot to a simple interface rather than deal with the idiosyncracies of EPIC.I am using PM's PMSystems software to drive the overhead on a dedicated system.I am going to use Phidgets 64-LED output module because it has grown more robust with the interface software and is fairly easy to implement.However, the INPUT side of Phigets is somewhat lacking, providing only 8 or 16 switch inputs per card, which is a really expensive solution considering 2/3 of that card will remain un-used.What I am hoping for, are some ideas that will allow for an easy interface to the overhead and something that will talk directly to FSUIPC like the Phidgets software does.Any help, ideas, or beer is greatly appreciated!

You might want to consider the 256 input Beta Innovations "Gamma Ray" at http://www.betainnovations.comLeo's written a nifty software interface app for it that should allow you to do anything you need.Richard

PHCC will interface 1024 switches for ya if you need ..

Hi,I originally used EPIC USB, and currently have IOCards (which works great). The problem with most of these systems when you have vast amounts of switches, and even more outputs, is wiring termination.This is where Phidgets seems to win (the Flight Deck Solutions system also seems to have the same major benefit) because they have individual terminal blocks for each wire.Trying to connect 64+ wires to a single 40pin IDE type header is a complete nightmare and creates a mess. Error detection is also made harder because it is difficult to see quickly what wire goes where.That's why I'm seriously considering Phidgets before I go any further (see Jonathan Richardsons PM Systems connection video on the PM site). It may be an expensive solution, but the modularity and individual wiring benefits will, I think, make it worth the investment.I've not actually used the FDS G1 and other interface cards yet, but I've seen them. As I mentioned, they have the same benefit of the individual termination blocks and were designed specifically for flight sim use whereas Phidgets, for example, were not.CheersChris

IOCards have a solution for this problem...You can use "Connector Card" for outputs and inputs !http://www.opencockpits.com/images/connector.jpgIn this video you can look this solution. My cockpit is wired with those cards... I use 600 or more meters of cable in this moment !http://www.opencockpits.com/modules.php?na...p=getit&lid=234

>IOCards have a solution for this problem...>>You can use "Connector Card" for outputs and inputs !>Ferdie,Thanks for this - I wasn't aware that a Connector Card was available. I'll get hold of a few and see if it cleans things up a bit. I must say, SIOC is superb and makes relatively complex functions pretty easy to implements.CheersChris

That solution would be perfect if the device driver interfaced directly to FSUIPC. Beta Innovations products are really good, but they appear as nothing more than a big honkin' joystick in Windows (unless I am missing something...)

Also have a look at MJoy ahttp://www.mindaugas.com/products/MJoy16-C1/112 buttons, 8 axes, 10 bit resolution and you can do it yourself or buy it from that siteDan

Beta Innovations provides a choice of software that goes way beyond the "windows joystick" option. Keyboard Studio along with FSUIPC will most likely do anything you wish. The other option, BIFS is VERY easy to use and it works directly as a module within MSFS. I've used both and they work great.