Steve, I chose not to tune the EC2 that way (using either mode 6, or 2) for that exact reason - I couldn’t tell what the computer was doing.
If the method works, I suppose one could argue who cares – I certainly don’t know what the table looks like for my Ford Escape.
I used Mode 3 to set injector flow rate (above staging) as per the manual, then made manual adjustments to every data point using Mode 1 – the result is my MCT table looks like a saw-tooth waveform, i.e., 2 non-linear
rising slopes either side of staging with an obvious correction just above staging.
I may try your method – I can always go back to what I have now – Ed’s little device makes it pretty easy to do MCT entries.
Jeff
|
From:
|
"Steven W. Boese" <SBoese@uwyo.edu>
|
|
Subject:
|
RE: [FlyRotary] Re: More staging and tuning
|
|
Date:
|
Thu, 10 Mar 2011 10:35:14 -0700
|
|
To:
|
Rotary motors in aircraft <flyrotary@lancaironline.net>
|
|
|
|
|
Jeff,
I have been using the default MCT with no changes.
You are correct about the effect of the different modes on the MCT. That last sentence could have been worded
better:
The only difference in using the second method is that just a few minor corrections (if any) to the default
table seem to be needed after these initial two or three adjustments.
Steve
|
From: Jeff Whaley
Sent: Thursday, March 10, 2011 11:44 AM
To: 'Rotary motors in aircraft'
Subject: Re: More staging and tuning
Steve, or Bill:
When using the “simplified” #2 method (restore defaults, mode 3 below staging, mode 6 above staging, mode 2 at idle, then mode 1 or 9) what does your resulting MCT table look like? Is it simply a flat line at or near zero (default) for
all data points?
As I understand it the EC2 will not change MCT displayed values when using Modes 3, 6 or 2 … but will start showing MCT corrections with Modes 1 or 9.
Jeff
|
From:
|
"Steven W. Boese" <SBoese@uwyo.edu>
|
|
Subject:
|
RE: [FlyRotary] Re: more staging and tuning
|
|
Date:
|
Thu, 10 Mar 2011 01:13:29 -0700
|
|
To:
|
Rotary motors in aircraft <flyrotary@lancaironline.net>
|
|
|
|
|
Al,
I apologize for the long posts.
In my opinion, the short answer to your question is YES.
The EC2 has the versatility to be tuned in a number of ways. It appears to me, at least, that a significant
part of the MCT corrections needed is the result of injector lag time. There are at least two ways of dealing with this.
One is to experimentally determine this for each address in the table. This can be difficult since there are
a lot of addresses and the corrections can be very different for adjacent addresses. In addition, some of this tuning can only be done in flight. Some users have more difficulty with this than others. This may be because of the individual user or the individual
equipment configuration or both. At any rate, it seems to be a recurrent problem.
A second way to deal with injector lag is by including it in the calculation of the injector pulse width. Doing
so removes much of the MCT adjustments that are needed throughout the table and also removes the discontinuities. This calculation is not difficult as demonstrated by the effectiveness of the hardware addition that I made which has no intelligence.
Either method requires adjustments with modes 2,3 and, in some cases, 6. The only difference in using the second
method is that the entire table is nearly correct after these initial two or three adjustments.
Steve
|