[simpits-tech] Marv: driving DBQ gauges??

[Gene Buckle]

> EPIC ties together inputs/outputs and transducers of
> various sorts together in ways that would only be
> possible with phidgets by writing code for the phidgets
> that replicates much of what EPIC EPL does already.
>
This doesn't make any sense to me.  EPL doesn't provide anything special
that can't be done with the same ease in another environment.

> Our analysis is that the extra
> coding/testing/integration work involved in using
> phidgets far outweighs any initial cost saving you
> might realize in buying hardware.
>
I think the word I'm looking for here is "poppycock". :)

Starting from a pure input standpoint, you're already $350 ahead with the
255 input Phidget. (They're $50).  With EPIC, you have to write programs
for EPIC in EPL as well as for the PC.  With Phidgets, you only write on
the PC.  An EPL/PC solution is _more_ expensive to deal with, especially
when looking at the total cost to build a solution.

I own both the ISA and USB EPIC boards as well as a host of their
peripheral boards.  I also work with some of the Phidgets that are
available.  There is _no_ way you're going to tell me (or anyone else that
can think) that a total EPIC solution is cheaper than the same solution
implemented in Phidgets.  (ok, technically it's possible, but it involves
hiring a prima-donna programmer that's charging FAR more than he's worth)



 > Tight integration is important because Falcon4 SP3, our
> software of (no- ;) choice at present, has some serious
> gaps in the way analogs, button inputs, lamp outputs
> and shared memory data are managed.  These gaps require
> some "papering" over with code bound to the
> simulator...that's harder to do if your various I/O
> systems are not controlled from the same code (or code
> that at the least has other means to share "event"
> handling).

You'll maintain two code bases (EPL and host pc) with EPIC, and one
codebase with Phidgets.  You're not losing any "integration" by using a
Phidget.  If someone is telling this, they're blowing smoke up your butt.

BTW, Falcon is a _very_ poor example.  It's shared memory area is a kludge
at best.  If you _must_ use Falcon, download the source code (it's still
floating around out there) and implement *correct* interfacing support.

BTW, Both Battle of Britain and MiG Alley from Rowan Software have been
released in source form so they'd both be great candidates for adding
cockpit integration routines to support both Phidget and EPIC solutions.



 > Hence my question of Marv (or anyone else
;)...has > anyone already thought about how to hook servos up to
> an EPIC??
>
Grab a PhidgetServo.  Add the code to your existing host pc code.  Done.
Hell, Robert Favre could add phidget support to his MFD program in
seconds and for that matter so could you.  It already talk to Falcon4 and
is freely downloadable from the ftp site.

g.