Return-Path: Received: from corpprd-pxy2.canfor.ca ([198.162.160.3] verified) by logan.com (CommuniGate Pro SMTP 4.2.8) with ESMTP id 619741 for flyrotary@lancaironline.net; Mon, 24 Jan 2005 13:24:29 -0500 Received-SPF: none receiver=logan.com; client-ip=198.162.160.3; envelope-from=Steve.Bartrim@canfor.com Received: from canformail1.canfor.ca (canformail1.canfor.ca [199.60.193.29]) by corpprd-pxy2.canfor.ca (Build 103 8.9.3p2/NT-8.9.3) with ESMTP id KAA05860; Mon, 24 Jan 2005 10:23:36 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C50241.D1C927A8" Subject: RE: [FlyRotary] Re: datalogging Date: Mon, 24 Jan 2005 10:23:36 -0800 Message-ID: <0E7B1751E5E0EE4A8C265AEC3D2500F405924490@canformail1.canfor.ca> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [FlyRotary] Re: datalogging Thread-Index: AcUCPna3BSZAVraiQfSsoWnZZjXhwAAAZ+Qg From: "Bartrim, Todd" To: "Rotary motors in aircraft" , This is a multi-part message in MIME format. ------_=_NextPart_001_01C50241.D1C927A8 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I'm guessing that the most logical data point would be P3-7, P3-8 & = P3-14 on the EM2 to use for a serial connection. This should be the pins = to talk to the chip for programming purposes, but can we talk to the = chip for a data stream output? I know just enough about this to be = dangerous. The EM2 would be far more appropriate source of data than the EC2 as it = would give access to all of the EM2 data including A/S, Alt, OAT, VSI as = well as all engine parameters to allow for easy analysis of engine = performance compared directly against various flight configurations. Tracy seem to have just ignored these questions about datalogging on = the list and has never just said no, so I'm hoping that he's either = working on it or considering it. Probably doesn't want to announce it = until it's ready to avoid having all the anxious customers waiting for = it as happened with the EM2 release. Yeah, that's gotta be it,,, and the = first 2 already have Rusty and my names on them... Yeah that's = definitely gotta be it :-) Todd Bartrim (Datalogging... the request that won't go away :-) > Anybody know that data is on the wire(s) that connect the EC2 to the = EM2? Seems like a logical place for Tracy to put the output for data = logging. =20 >=20 > =20 >=20 > Tracy > -> you come up with the schema (serial bus data format) and = I> '> ll write the PC code to read the bus then store and display data.=20 >=20 >=20 ------_=_NextPart_001_01C50241.D1C927A8 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: [FlyRotary] Re: datalogging

        I'm guessing that the most = logical data point would be P3-7, P3-8 & P3-14 on the EM2 to use for = a serial connection. This should be the pins to talk to the chip for = programming purposes, but can we talk to the chip for a data stream = output? I know just enough about this to be dangerous.

        The EM2 would be far more = appropriate source of data than the EC2 as it would give access to all = of the EM2 data including A/S, Alt, OAT, VSI as well as all engine = parameters to allow for easy analysis of engine performance compared = directly against  various flight configurations.

        Tracy seem to have just = ignored these questions about datalogging on the list and has never just = said no, so I'm hoping that he's either working on it or considering it. = Probably doesn't want to announce it until it's ready to avoid having = all the anxious customers waiting for it as happened with the EM2 = release. Yeah, that's gotta be it,,, and the first 2 already have Rusty = and my names on them... Yeah that's definitely gotta be it = :-)

Todd Bartrim  (Datalogging...  the request that = won't go away :-)

    Anybody know that data is on the wire(s) that connect the = EC2 to the EM2? Seems like a logical place for Tracy to put the output = for data logging.=A0

    =A0

    Tracy – you come up with the schema (serial bus = data format) and I’ll write the PC code to read the bus then store = and display data.


------_=_NextPart_001_01C50241.D1C927A8--