Received-SPF: none
 receiver=logan.com; client-ip=68.230.241.31; envelope-from=dale.r@cox.net
From: Dale Rogers <dale.r@cox.net>
To: "Rotary motors in aircraft" <flyrotary@lancaironline.net>
Subject: Re: [FlyRotary] Re: copy A to B on EC-2    was Re: Disappointing
Date: Fri, 4 Feb 2005 11:47:55 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Message-Id: <20050204164755.QJED7567.fed1rmmtao08.cox.net@smtp.west.cox.net>


> 
> From: "Russell Duffy" <13brv3@bellsouth.net>
> Date: 2005/02/04 Fri AM 09:06:55 EST
> To: "Rotary motors in aircraft" <flyrotary@lancaironline.net>
> Subject: [FlyRotary] Re: copy A to B on EC-2    was Re: Disappointing
>  Day
> 
>     IIRC, you had one of the earlier versions of the EC2 as well, but also
> installed the update chips? So I would assume that the update chips do allow
> this transfer function, or is there more to it as Tracy's e-mail sort of
> indicates?  
>  
>  
> Hi Todd,
>  
> Tracy did tell me that very old EC-2's didn't have the link between to the
> controller, so they wouldn't perform this function.  Later units just need
> the new software.  My EC-2 is from Feb 2002, and it does seem to perform
> this function.  
>  
> I have to admit that I've never found controller B to just magically run
> like controller A when I've done this.  There will be some diff just because
> of the temp sensor in A, that doesn't exist in B.  The only way to eliminate
> that would be to tune A when the OAT is at whatever the fix temp value Tracy
> sets for B.   The last time I tried this, it seemed to work better than it
> ever has, but it still didn't seem like the injector flow rate settings came
> over.  Tracy said it was an all or nothing function, and that it should
> either work, or not.  
>  
> I'll be really interested to hear how this works for others.  For the
> record, my number one feature request for the EC-2 is to be able to save all
> the programming parameters for each controller.  I'd like to be able to save
> them to laptop, Ipaq, memory stick, etc, then restore them as needed.
> Getting the MAP table just right can be a fiddly affair sometimes, and I
> find myself hesitant to try to make a "quick touch up" for fear that I'll
> screw something else up in the process.  Knowing that you can backup and
> restore the data would be nice.   
>  
> Cheers,
> Rusty (assuming the rotors arrive, I'll be ready to reassemble this weekend)
> 

Hmmm,

   Dunno how hard it is to implement a USB interface, but 
a "write to port" function would be nice, so that the map(s) 
could be saved.  Even better if there was a way to specify 
file names, so that more one could save more than one map 
per "memory stick" - even if the options were only a toggle 
through, say, "MAP.01, MAP.02 ... MAP.nn".

Dale R.