Return-Path: Received: from corpprd-pxy2.canfor.ca ([198.162.160.3] verified) by logan.com (CommuniGate Pro SMTP 4.3c2) with ESMTP id 796503 for flyrotary@lancaironline.net; Wed, 16 Mar 2005 15:50:17 -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 MAA12308 for ; Wed, 16 Mar 2005 12:49:25 -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_01C52A69.A3C51828" Subject: RE: [FlyRotary] Re: EC2 auto program Date: Wed, 16 Mar 2005 12:49:25 -0800 Message-ID: <091A2D42FAF91A41B84750D269FC97E72B3135@canformail1.canfor.ca> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [FlyRotary] Re: EC2 auto program Thread-Index: AcUqRHoKU+A+mDl6RVG92JaCZDXksQAIsPIg From: "Bartrim, Todd" To: "Rotary motors in aircraft" This is a multi-part message in MIME format. ------_=_NextPart_001_01C52A69.A3C51828 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Tracy; This is great news for those yet to begin programming (and those still struggling with it). If I understand your description correctly; *=09 The current EC2 chip will not have to be updated, so long as we are already using the previously latest version which allows manual programming via the EM2. *=09 The current EM2 chip will have to be updated to allow for auto programming calculations If this is the case then I will still take the "cold start chip" when you have it ready, but if this is not the case and the EC2 chip also needs to be changed then I'm willing to wait until you can produce a single EC2 chip with both of these functions. In any event, you can sign me up for one of the new EM2 chips. I'm currently quite happy with my EC2 programming, however the new "cold start chip" will require reprogramming so I'd be more than happy to be a beta tester for the auto programming feature. =20 Todd (can Guinea Pigs fly?) (hoping a datalogging output is not far behind) =20 The good news is that this approach will allow current EC2s to auto program if it is connected to an EM2 with the new feature. Old EM2s will be upgradeable to auto program. =20 ------_=_NextPart_001_01C52A69.A3C51828 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message
Hi=20 Tracy;
    This is great news for those yet to = begin=20 programming (and those still struggling with it). If I understand your=20 description correctly;
  • The current=20 EC2 chip will not have to be updated, so long as we are already using = the=20 previously latest version which allows manual programming via the=20 EM2.
  • The current=20 EM2 chip will have to be updated to allow for auto programming=20 calculations
If=20 this is the case then I will still take the "cold start chip" when you = have it=20 ready, but if this is not the case and the EC2 chip also needs to be = changed=20 then I'm willing to wait until you can produce a single EC2 chip with = both of=20 these functions.
    In any event, you can sign me up for one of the new EM2 = chips. I'm=20 currently quite happy with my EC2 programming, however the new "cold = start chip"=20 will require reprogramming so I'd be more than happy to be a beta tester = for the=20 auto programming feature.
 
Todd    (can Guinea Pigs = fly?)   =20 (hoping a datalogging output is not far behind)

 
  The good news is that this approach will allow current = EC2s to=20 auto program if it is connected to an EM2 with the new feature.  = Old EM2s=20 will be upgradeable to auto program.
 
------_=_NextPart_001_01C52A69.A3C51828--