[simpits-tech] Hagstrom vs Epic

Rob simpits-tech@simpits.org
Wed, 19 Feb 2003 11:42:44 -0500


This is a multi-part message in MIME format.

--Boundary_(ID_9zgxzCMRxn5sqqw6yHezjA)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT

Try FSBUS, Phidgets, InterfaceIT, plus a few other home breeds. All have thier advantages and disadvantages.
Thanks, Rob Archer

Home of the real 737SIM
USA
  ----- Original Message ----- 
  From: Kevin Foisy 
  To: simpits-tech@simpits.org 
  Sent: Wednesday, February 19, 2003 10:25 AM
  Subject: [simpits-tech] Hagstrom vs Epic


  Question for all of you...I'll be moving into the h/w stages of my flight deck soon.  Looking for advice on whether to go Epic or Hagstrom for interfacing.

  What are the pros and cons of each?  I've heard that Hagstrom will limit you quickly while Epic, although more complex will leave more doors open.  I'm a developer, so I'm not afraid of a little code but don't want to make a second career of writing code for Epic.

  I'm concerned with how I'll be able to link in things like annunciators, etc. without using something like Epic.

  Any advice?


  Thanks,
  Kevin

--Boundary_(ID_9zgxzCMRxn5sqqw6yHezjA)
Content-type: text/html; charset=iso-8859-1
Content-transfer-encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2600.0" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Try FSBUS, Phidgets, InterfaceIT, plus a few other 
home breeds. All have thier advantages and disadvantages.</FONT></DIV>
<DIV>Thanks, Rob Archer</DIV>
<DIV>&nbsp;</DIV>
<DIV>Home of the real 737SIM<BR>USA</DIV>
<BLOCKQUOTE dir=ltr 
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV 
  style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B> 
  <A title=kevin.foisy@Stealthbits.com 
  href="mailto:kevin.foisy@Stealthbits.com">Kevin Foisy</A> </DIV>
  <DIV style="FONT: 10pt arial"><B>To:</B> <A title=simpits-tech@simpits.org 
  href="mailto:simpits-tech@simpits.org">simpits-tech@simpits.org</A> </DIV>
  <DIV style="FONT: 10pt arial"><B>Sent:</B> Wednesday, February 19, 2003 10:25 
  AM</DIV>
  <DIV style="FONT: 10pt arial"><B>Subject:</B> [simpits-tech] Hagstrom vs 
  Epic</DIV>
  <DIV><BR></DIV>
  <DIV><SPAN class=253522015-19022003><FONT face=Arial size=2>Question for all 
  of you...I'll be moving into the h/w stages of my flight deck soon.&nbsp; 
  Looking for advice on whether to go Epic or Hagstrom for 
  interfacing.</FONT></SPAN></DIV>
  <DIV><SPAN class=253522015-19022003><FONT face=Arial 
  size=2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=253522015-19022003><FONT face=Arial size=2>What are the pros 
  and cons of each?&nbsp; I've heard that Hagstrom will limit you quickly while 
  Epic, although more complex will leave more doors open.&nbsp; I'm a developer, 
  so I'm not afraid of a little code but don't want to make a second career of 
  writing code for Epic.</FONT></SPAN></DIV>
  <DIV><SPAN class=253522015-19022003><FONT face=Arial 
  size=2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=253522015-19022003><FONT face=Arial size=2>I'm concerned with 
  how I'll be able to link in things like annunciators, etc. without using 
  something like Epic.</FONT></SPAN></DIV>
  <DIV><SPAN class=253522015-19022003><FONT face=Arial 
  size=2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=253522015-19022003><FONT face=Arial size=2>Any 
  advice?</FONT></SPAN></DIV>
  <DIV><SPAN class=253522015-19022003><FONT face=Arial 
  size=2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=253522015-19022003><FONT face=Arial 
  size=2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=253522015-19022003><FONT face=Arial 
  size=2>Thanks,</FONT></SPAN></DIV>
  <DIV><SPAN class=253522015-19022003><FONT face=Arial 
  size=2>Kevin</FONT></SPAN></DIV></BLOCKQUOTE></BODY></HTML>

--Boundary_(ID_9zgxzCMRxn5sqqw6yHezjA)--