X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Received: from [216.52.245.18] (HELO ispwest-email1.mdeinc.com) by logan.com (CommuniGate Pro SMTP 5.0.5) with ESMTP id 901636 for flyrotary@lancaironline.net; Mon, 26 Dec 2005 08:46:24 -0500 Received-SPF: none receiver=logan.com; client-ip=216.52.245.18; envelope-from=wschertz@ispwest.com Received: from 7n7z201 (4Cust3.VR1.CHI6.broadband.uu.net [63.13.186.3]) by ispwest-email1.mdeinc.com (Vircom SMTPRS 4.2.425.16) with SMTP id for ; Mon, 26 Dec 2005 05:45:29 -0800 X-Modus-ReverseDNS: OK X-Modus-BlackList: 63.13.186.3=OK;wschertz@ispwest.com=OK X-Modus-RBL: 63.13.186.3=OK X-Modus-Trusted: 63.13.186.3=NO Message-ID: <00fb01c60a22$99f8e7f0$0400000a@7n7z201> From: "William" To: "Rotary motors in aircraft" References: Subject: Re: [FlyRotary] Re: External datalogging, and other stuff Date: Mon, 26 Dec 2005 07:45:10 -0600 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00F8_01C609F0.4C394320" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 This is a multi-part message in MIME format. ------=_NextPart_000_00F8_01C609F0.4C394320 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MessageI don't know about the EFIS-lite version, but the Blue Mountain = EFIS-1 does provide data logging. Bill Schertz KIS Cruiser # 4045 ----- Original Message -----=20 From: Russell Duffy=20 To: Rotary motors in aircraft=20 Sent: Sunday, December 25, 2005 10:58 PM Subject: [FlyRotary] Re: External datalogging, and other stuff Perhaps this company will have something that you can use: http://www.pulseinstruments.com/acquisition/ Ben=20 Hi Ben, Best I can tell, these guys make units that are geared to testing in a = lab. I should have mentioned that I found a number of these types of = units, but I'm specifically looking for something that can mount in the = panel full time. My goal is to have it recording all the time, so it = won't miss anything. Once the initial flight testing is done, it will = just be there to help analyze anything abnormal. =20 As an example, a friend of mine has an RV-8, and a JPI engine monitor = that logs everything. On a recent flight, his engine went rough, and = lost some power for about 30 seconds, and none of the usual things = helped. Once the problem went away, all was well for the rest of the = flight. He downloaded the logs after the flight, and found that the = front two cylinders EGT went down during the time the engine went rough. = The only thing common to those two cylinders is the Lightspeed ignition = coil, and wiring. Sure enough, there was a bad connection on the coil. = Datalogging is your friend :-) Cheers, Rusty=20 ------=_NextPart_000_00F8_01C609F0.4C394320 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message
I don't know about the EFIS-lite = version, but the=20 Blue Mountain EFIS-1 does provide data logging.
Bill Schertz
KIS Cruiser # 4045
----- Original Message -----
From:=20 Russell=20 Duffy
Sent: Sunday, December 25, 2005 = 10:58=20 PM
Subject: [FlyRotary] Re: = External=20 datalogging, and other stuff

Perhaps = this company will=20 have something that you can use:
http://www.pulseins= truments.com/acquisition/
Ben 
 
Hi =20 Ben,
 
Best I can=20 tell, these guys make units that are geared to testing in a = lab.  I=20 should have mentioned that I found a number of these types = of=20 units, but I'm specifically looking for something that can mount = in the=20 panel full time.  My goal is to have it recording all the time,=20 so it won't miss anything.  Once the initial flight testing = is done,=20 it will just be there to help analyze anything=20 abnormal.  
 
As an example,=20 a friend of mine has an RV-8, and a JPI engine monitor that logs=20 everything.  On a recent flight, his engine went rough, and lost = some=20 power for about 30 seconds, and none of the usual things=20 helped.  Once the problem went away, all was well for = the=20 rest of the flight.  He downloaded the logs after the = flight, and=20 found that the front two cylinders EGT went down during the time=20 the engine went rough.  The only thing common to those two = cylinders=20 is the Lightspeed ignition coil, and wiring.  Sure enough, there = was=20 a bad connection on the coil.  Datalogging is your friend=20 :-)
 
Cheers,
Rusty=20
  
<= /BODY> ------=_NextPart_000_00F8_01C609F0.4C394320--