dLoad accel / Load accel factor tables functions? | AEM
3 posts / 0 new
Last post
chubbs
Offline
Last seen: 1 month 3 days ago
Joined: 08/31/2016 - 07:34
dLoad accel / Load accel factor tables functions?

Previously in another thread it was recommended that zeroing out these tables may fix an issue that seemed like ignition break up around 5-5500RPM. It did resolve this issue for me, but I have a few questions.

What are the functions of these tables? From what i'm understanding in the description in the software, these tables basically control how much fuel is added for initial large throttle % increases, so the car doesn't go insanely rich. 

What i'm really trying to figure out, is How / What do these tables effect  high in the RPM range? For a few years they were set to the AEM default, and had no issues. One day, they randomly caused an issue in the backround. Now they're zeroed out, and it seems like the only effect they've had was clearing up that issue. Nothing else can be visually felt / seen effect wise.

These are the default settings:
https://imgur.com/wtz2IEq

chubbs
Offline
Last seen: 1 month 3 days ago
Joined: 08/31/2016 - 07:34
Bump this up. Still curious

Bump this up. Still curious what these functions do

AEM_NS
Offline
Last seen: 2 hours 10 min ago
Joined: 06/06/2014 - 09:31
They're acceleration

They're acceleration enrichment tables that are based on delta MAP. There's no way that a table setting can not be working and be fine and then all of a sudden induce a problem. It the table setting was there and it created a problem, then it was always there. Perhaps you never specifically noticed it. Or something else actually changed without you realizing it. Accel enrichment is usually handled on either by delta TPS or delta MAP and typically the Series 2 base cals were all setup as dTPS so the dMAP tables should have been zeroed out. If some weren't, it was by mistake and you can tell that those aren't intentional values because those table typically never have flat values in them. If zeroing out the tables fixed your problem, great. I wouldn't over think it. Without seeing specific data showing a problem, I can't guess or assume what was actually happening so we'll just chalk this one up as a win for being something simple.