AEM Base Calibration and Startup Procedures
So, I am working on my base cal so I can tackle the 9 Hour drive to the tuner (That is if Mase doesn’t come to town first), and I have a few questions.
Here is the startup procedure I have used so far with the addition of testing all the electrical and the mechanical including setting the FPR........ But if you have any tips I would appreciate any info you have.
(1) Adjust the
a.) I/J Batt Offset
b.) Change the Coolant temp Calibration
c.) Calibrate all the extra sensors I added/changed
(2) Rescale my break points
(3) Build a base map which has been interpolated from the base map and other fuel and Ignition tables
(4) Set the Throttle Position min & Max
(5) Checked the Timing and adjusted for 0deg both at low and high RPM to ensure no drift
(6) Adjust the idle
(7) Monitor AFR’s while raising and lowering the RPM w/o load and appleid scalars to the base map
So far the car runs and drives at no load acceptably but not loaded and since I am a one man crew I would like to try and use the AUTO map for my first ruff in then commandeer someone to drive the car while I street tune the fuel.
Problem is I cannot get the Automap to work, the AEM instructions are vague on the topic so if anyone has experience with it pointers would be great. Here is a how I have set up the Automap function based on the instructions, as I drive it does populate the Log table however I cannot seem to figure out how to get it to make changes to the fuel map even with the use of the "Program Changes Feature".
I am also struggling to understand the “Automapping Initialize” parameters.
They never explain what the “Target Accuracy” they explain what is does but do not give a unit reference. So if I have 0.5 in there does that mean that it will only make changes over 0.5 ms to my I/J Pulse Width or does that mean that it will only make changes if the error is more than 0.5%..............
The same goes for the control logic, based on the equation below what units is “Change”, is that Pulse Width Percent…..
Change = (Target Value – Log Value) * Error Multiplier + Error Additive
Here is the startup procedure I have used so far with the addition of testing all the electrical and the mechanical including setting the FPR........ But if you have any tips I would appreciate any info you have.
(1) Adjust the
a.) I/J Batt Offset
b.) Change the Coolant temp Calibration
c.) Calibrate all the extra sensors I added/changed
(2) Rescale my break points
(3) Build a base map which has been interpolated from the base map and other fuel and Ignition tables
(4) Set the Throttle Position min & Max
(5) Checked the Timing and adjusted for 0deg both at low and high RPM to ensure no drift
(6) Adjust the idle
(7) Monitor AFR’s while raising and lowering the RPM w/o load and appleid scalars to the base map
So far the car runs and drives at no load acceptably but not loaded and since I am a one man crew I would like to try and use the AUTO map for my first ruff in then commandeer someone to drive the car while I street tune the fuel.
Problem is I cannot get the Automap to work, the AEM instructions are vague on the topic so if anyone has experience with it pointers would be great. Here is a how I have set up the Automap function based on the instructions, as I drive it does populate the Log table however I cannot seem to figure out how to get it to make changes to the fuel map even with the use of the "Program Changes Feature".
I am also struggling to understand the “Automapping Initialize” parameters.
They never explain what the “Target Accuracy” they explain what is does but do not give a unit reference. So if I have 0.5 in there does that mean that it will only make changes over 0.5 ms to my I/J Pulse Width or does that mean that it will only make changes if the error is more than 0.5%..............
The same goes for the control logic, based on the equation below what units is “Change”, is that Pulse Width Percent…..
Change = (Target Value – Log Value) * Error Multiplier + Error Additive
i know this is not perfect, but i didnt use the automap feature. i did however use closed loop on the wideband and set target afrs at my load breakpoints. i then would watch the o2 feedback, and if i saw it adding fuel, i would look at what load and rpm and i would add some fuel so it wasnt. same if it was taking fuel away.
like u said though, get a friend to drive it. so much easier that way. well that or just rent some dyno time at a loading dyno and then your set!
like u said though, get a friend to drive it. so much easier that way. well that or just rent some dyno time at a loading dyno and then your set!
Originally Posted by camuman,Nov 5 2009, 09:43 AM
Well that or just rent some dyno time at a loading dyno and then your set!
Well here is what I got back from AEM so it sounds like there may be some issues.
2. Quite a few tuners have reported the automap feature isn't as fast or safe as manually adjusting the fuel map. Don't forget that a misfiring engine will result in inaccurate AFRs. Some sort of update will be included in future versions of the AEMTuner software. Some people prefer to use the closed-loop O2 Feedback and apply the O2#1 FB Value percentage to the fuel map.
2. Quite a few tuners have reported the automap feature isn't as fast or safe as manually adjusting the fuel map. Don't forget that a misfiring engine will result in inaccurate AFRs. Some sort of update will be included in future versions of the AEMTuner software. Some people prefer to use the closed-loop O2 Feedback and apply the O2#1 FB Value percentage to the fuel map.
I talked to them and I have decided to get rid of the idea of using the Auto tune to change the map and just do it myself. Since I work in Lambda this is easy enough using Excel or I believe there is a math feature I can work with also.
Trending Topics
Originally Posted by dsddcd,Nov 6 2009, 01:16 PM
Well here is what I got back from AEM so it sounds like there may be some issues.
2. Quite a few tuners have reported the automap feature isn't as fast or safe as manually adjusting the fuel map. Don't forget that a misfiring engine will result in inaccurate AFRs. Some sort of update will be included in future versions of the AEMTuner software. Some people prefer to use the closed-loop O2 Feedback and apply the O2#1 FB Value percentage to the fuel map.
2. Quite a few tuners have reported the automap feature isn't as fast or safe as manually adjusting the fuel map. Don't forget that a misfiring engine will result in inaccurate AFRs. Some sort of update will be included in future versions of the AEMTuner software. Some people prefer to use the closed-loop O2 Feedback and apply the O2#1 FB Value percentage to the fuel map.
I love their response, it basically says "don't use it cause it doesn't work right"...
For the dyno tune, make sure the dyno is capable of holding a steady load. If it isn't, part throttle tuning will never be as good or as accurate as it should be. Dyno Dynamics, Mainline Dynolog, DynaPack, Superflow, Land and Sea, and Mustang dynos are all capable of holding a load (plus others I probably haven't listed). Some newer Dynojet dynos are also load holding dynos. Dyno Dynamics and DynaPack are quite nice to work with, but Mustang or Superflow dynos will work in a pinch (with a good operator).
Tim
Tim
Thread
Thread Starter
Forum
Replies
Last Post
amdaman
S2000 Forced Induction
12
Jun 11, 2015 08:34 PM











