VE Table
My VE table estimate using the estimator from the Megasquirt website:
[need to add table - it's not with me here.]
If anything, it's a little optimistic - which is no bad thing for a 1st attempt as it only means too much fuel.
etc...
A Lambda table has also been created, but obviously won't do anything until the wideband sensor is installed. Bought some bosses for the exhaust and lambda should go in this weekend.
Progress so far
Well, the car now runs, and it has taken me to work. Short 6 mile trip. Initial results are good. The fans come on when they should, the engine warms up at a sensible speed, hot start is excelent, the engine is reasonably smooth in operation, but could be better!
I got the wideband calibrated and turned on auto learning and this has done wonders for making the car work well. It's turned into a rather quick car now - but I still want more!
Bad points are:
- The coolant and intake temperatures are still a few degrees wrong (better than before, but still wrong) - Refined again now, and only 2 degrees "wrong" now at 60 degrees. I think I can live with this...
- The VE map is not at all refined, but is getting there with auto learning now turned on
- Idle settings are still very wrong - all help appreciated - now fixed
- Acceleration enrichment is not right - but is getting better
- Cold start is better than it was, but not perfect.
note
Keep in mind that the lambda table is always used in fuel calculations, but indeed _also_ for supplying the ego controller with target lambda values, be sure to fill it with sane values.
The reference table you created with VE estimator from Megasquirt site might be VE * Lambda, while ours is pure VE, it can be needed to divide the table you created by the lambda table you put to get an accurate estimate, however during the tuning session it is easily fixed.
Mine is definitely pure VE, I did check that. But it's going to need tuning anyway...
Back to: MembersPage/DavidBlades