AEM 30-71XX Infinity Stand-Alone Programmable Engine Mangement System Full Manual User Manual

Page 263

Tuning Guide

257

When ModeSwitch =1 the ECU will blend between IgnMap_1 (the top table ModeSelect_Ign
gets used when the FlexContent is low), and IgnMap_1 (from the bottom table,
ModeSelect_IgnBlend when FlexContent is high). In other words, there won't be any blend, it will
use the main IgnMap timing values regardless of flex fuel content.

When ModeSwitch = 2 the ECU will use blend between IgnMap_2 (the top table ModeSelect_Ign
gets used when the FlexContent is low), and IgnMap_2 (from the bottom table,
ModeSelect_IgnBlend when FlexContent is high). Again, there won't really be any blending here,
because we've told it to use the same map in both conditions.

When ModeSwitch =3 the ECU will blend between IgnMap_2 (from the top table,
ModeSelect_Ign which gets used when FlexContent is low), and IgnMap_3 (from the bottom
table, ModeSelect_IgnBlend when FlexContent is high). You can put the most aggressive timing
numbers in IgnMap_3, and that timing map will only get used if the ModeSwitch = 3 and the
FlexContent is high.

There are similar tables for LambdaTargets, you can adjust these if you want to run more
aggressive lambda targets depending on ethanol content or other variables.