Project Honda Insight, Part 15 - Refining the on-road tune

Getting the car to drive really well

by Julian Edgar

Click on pics to view larger images

At a glance...

  • Wide-band closed loop and Quick Lambda
  • Acceleration enrichment
  • Filtering the MAP sensor signal to remove a flat spot

This series is based around a 2001 model hybrid Honda Insight.

The Insight remains one of the most aerodynamic and lightest cars ever made, with a Cd of 0.25 and a total mass of about 850kg from its 2-seater aluminium body.

The intent of the project is to turbocharge the engine, add water/air intercooling and programmable engine management, and then provide new high voltage batteries and a new electric motor control system.

The aim is to build a car with the best performance/economy compromise of any in the world.

The series so far:

Project Honda Insight, Part 1 – Introduction

Project Honda Insight, Part 2 – Fitting an Alternator

Project Honda Insight, Part 3 – Building an Airbox

Project Honda Insight, Part 4 – Intercooling Requirements

Project Honda Insight, Part 5 – Intercooling System #1

Project Honda Insight, Part 6 – Intercooling System #2

Project Honda Insight, Part 7 - Turbocharging

Project Honda Insight, Part 8 - Building the Exhaust

Project Honda Insight, Part 9 - First Electricals

Project Honda Insight, Part 10 - Alternator (again!) and beginning the MoTeC wiring

Project Honda Insight, Part 11 - New ignition system and cam sensing

Project Honda Insight, Part 12 - The MoTeC CRIP

Project Honda Insight, Part 13 - Idle Speed Control

Project Honda Insight, Part 14 – First road tuning of the MoTeC

This issue: Getting closed-loop fuelling up and running, tuning the acceleration enrichment, and ridding the car of a troublesome flat spot.

Last article in this series we got the car on the road and tuned the fuel, ignition, turbo boost and EGR. Now it’s time to get closed loop fuelling working, improve the acceleration enrichment and chase-down a full-throttle flat spot.

Closed loop

As described earlier, I chose to initially tune the car out of closed loop. That is, tuning was done using an external air/fuel ratio meter (a MoTeC PLM) and manually setting injector pulse-widths to give the required mixtures at different loads and engine rpm.

Taking this approach meant that the car wasn’t trying to correct mixtures at the same time as they were being set, and also allowed me to have a better ‘handle’ on what was going on at any one time.

But with the air/fuel ratios largely correct (within around 0.8 of an air/fuel ratio) across the normal driving range, it was time to fit the wide-band oxygen sensor and activate closed loop control.

A Bosch LSU4 sensor was fitted and wired to the ECU. It was calibrated in free air and then the car was started. The measured mixture values were close to that previously shown by the PLM – ‘close’ but not identical, since the PLM sensor has never been free-air calibrated.

A Lambda table was then constructed to show desired Lambda values at all engine loads and speeds. This table can be thought of as the ‘aim point’ – the values don’t have to be at Lambda 1 (ie stoichiometric) but instead can be richer at higher loads and leaner at low loads. Because a wide-band sensor is being used to provide feedback, the car will then maintain these air/fuel ratios – even if they’re not stoichiometric.

Lambda versus air/fuel ratio

MoTeC chooses to show the relative strength of the mixture by means of Lambda numbers, rather than air/fuel ratio.

A Lambda value of 1 equals a stoichiometric ratio, that is, the ratio of fuel to air that provides chemically the most complete combustion. With petrol as the fuel, this is the equivalent of an air/fuel ratio of 14.7:1.

Lambda values of less than 1 indicate rich mixtures; those of greater than 1 indicate leaner mixtures.

Using Lambda values rather than air/fuel ratio numbers works well if you are using different fuels that in turn have different stoichiometric ratios – stoichiometric remains at Lambda 1 irrespective of the fuel.

For petrol, the following conversion applies:

Lambda

AFR

0.70

10.3

0.75

11.0

0.80

11.8

0.85

12.5

0.90

13.2

0.95

14.0

1.00

14.7

1.05

15.4

1.10

16.2

1.15

16.9

1.20

17.6

1.25

18.4

1.30

19.1

1.35

19.8

1.40

20.6

1.45

21.3

1.50

22.1

1.55

22.8

1.6

23.5

One useful function of the MoTeC software is a ‘Quick Lambda’ function.

Once the Lambda chart has been completed, pressing ‘Q’ on the keyboard tunes the ‘live’ fuel site to the required injector pulse width to give the air/fuel ratio shown by the Lambda chart. The fuel map indicates the sites that have been tuned in this way, allowing the user to differentiate the sites tuned with Quick Lambda from those sites tuned manually.

When using Quick Lambda you need to be careful that the engine isn’t using acceleration enrichment (more on this in a moment) or is in injector over-run shut-off. However, outliers (where the fuel value is completely wrong) show up clearly on the 3D visual – sudden peaks or troughs in the 3D ‘topography’ are indicators of this type of error.

That said, as this chart of the Honda’s fuelling shows, engines do in fact require more variations in fuel through the range than you might first expect.

Quick Lambda was very effective, especially when tuning alone and/or at higher loads, where on the road, things start to happen more quickly. (Quick Lambda was the only tuning that I could easily do without pulling over to operate the laptop – just pressing a single button on the keyboard is easily and safely done while driving.)

With the Quick Lambda completed for most of the fuel sites, the rest could be manually set in accordance with the Quick Lambda values. With this done, the car then used the feedback from the oxy sensor to maintain air/fuel ratios as requested – ie it worked in closed loop.

The Lambda table was set to:

  • 0.85 (AFR = 12.5:1) to 0.8 (AFR = 11.8) at high loads

  • stoichiometric (Lambda = 1, AFR = 14.7:1) at the majority of loads and revs

  • 1.35 (AFR = 19.8:1) at low loads, high rpm.

Acceleration enrichment

Acceleration enrichment took a long time to get right. There were two reasons for this:

  • I initially had the tuning table parameters set wrongly and so I chased my tail for many hours.

  • I didn’t realise how wide the range of driving behaviours is that is influenced by acceleration enrichment.

The best approach to setting acceleration enrichment was to use a chart of MAP pressure versus engine speed. The enrichment applies only when the throttle is actually being moved (in contrast to just engine revs increasing) and the values in the chart are activated as the active load site passes through them. That is, during tuning, you need to watch both the speed of accelerator movement and what enrichment values are being passed through on the map during this foot movement.

I found that acceleration enrichment made a dramatic difference to a whole range of driving behaviours.

For example, when re-applying throttle in fifth gear cruising (eg backing off when driving down a hill and then re-applying throttle), acceleration enrichment at very low manifold pressures and relatively low revs was needed if a ‘lean jerk’ wasn’t to occur.

Another example of acceleration enrichment making a major impact on driveability was in the smoothness of gear changes, especially those made when driving the car hard.

Finally, more as you’d expect, acceleration enrichment made a large difference to the responsiveness of the engine. What I’d considered to be lag associated with the turbo spooling-up after a sudden throttle shift was actually more related to a short-term lean condition that made response doughy. In fact, to improve turbo response, increased acceleration enrichment was added at 100 kPa manifold pressure (ie atmospheric pressure) at 3000 and 4000 rpm to bring the turbo back onto boost faster.

In a way rather like the EGR covered earlier in this series, acceleration enrichment (at least on the little Honda) proved to be far more important to driveability than is often discussed.

Getting rid of the flat spot

After the Quick Lambda tune, the car drove very well, with smooth transitions between the differing air/fuel ratios.

However, there was a clear flat spot that occurred at just under 4000 rpm on full boost and at full throttle. The flat spot was particularly noticeable when passing other cars in third gear – it existed in the lower gears, but because the engine spent less time in that spot, it wasn’t as major a problem. (The car’s gearing is such that 4000 rpm is not usually accessed in 4th and 5th gears.)

Close analysis of the fuel and timing charts showed no major changes in numbers at this spot, while logging indicated that boost momentarily dropped at this point. Thinking it might be a boost control issue, I inserted extra sites at this point in the boost map and increased duty cycle. This stopped boost dropping but the flat spot remained.

People on the MoTeC discussion group then suggested it might be interference between the 100Hz sampling speed of the MAP sensor input and the resonant pulsing of the intake manifold. (At 4000 rpm there are 33.3 intake strokes per second, multiplied by 3 cylinders = 100Hz.)

While the ECU has user-adjustable filtering available on all inputs, the suggestion was that I leave electronic filtering at a minimum and instead fit a mechanical filter in the MAP sensor hose. I sourced a specific MAP sensor filter from wrecker and installed it. The problem immediately disappeared.

Conclusion

So does the car now drive perfectly in all conditions?

No!

What the tuning has shown me is that there’s a good reason why mapping a factory car might take a year and 20 engineers. Even after perhaps 40 hours of on-road tuning, I still occasionally meet situations that the car had not previously experienced where the tune could be improved.

However, what can be said is that in the vast majority of situations, the car now drives like a well-mapped standard car – and vastly better than a standard Insight running without its electric assist functional.

Next issue – the MoTeC electronic dash

Did you enjoy this article?

Please consider supporting AutoSpeed with a small contribution. More Info...


Share this Article: 

Copyright © 1996-2017 Web Publications Pty Limited. All Rights Reserved