What happens at peak load?

Reply Subscribe

Thread Tools

Search this Thread

Jun 25, 2009 | 06:12 AM

#46

raasfaas

Thread Starter

Evolved Member

iTrader: (30)

Joined: Oct 2006

Posts: 780

Likes: 0

From: Fl/Jam

Quote:

Originally Posted by burnzy

it would be from your meth i' presume, especially if it's an on/off kit and not progressively tracking your IDCS, even with the HFS-6 I find I have to lean out progressively as the meth comes on, it pretty much lowers AFRs a full point. No way will the afrmap match your afrs with meth as the ecu doesn't track the meth idcs.

Well it's the AEM system so it is progressive, but it doesn't track idc it tracks boost. It starts spraying at a user preset boost level and progressively builds up to full spray by another user preset max boost level. But I think I would have to agree with you, I've been doing some further testing and tuning and it does seem as if its meth related.
The problem I was having with the afrmap was that it wasn't tracking my fuel map (not the actual afr) I dunno if it was an endian issue or what but since I upgraded to the latest version of ecuflash it now tracks fine.

Jun 25, 2009 | 06:40 AM

#47

wreckleford

Evolved Member

iTrader: (2)

Joined: Jun 2003

Posts: 1,171

Likes: 11

From: Jamaica

Quote:

Originally Posted by raasfaas

The problem I was having with the afrmap was that it wasn't tracking my fuel map (not the actual afr) I dunno if it was an endian issue or what but since I upgraded to the latest version of ecuflash it now tracks fine.

What version of ECUFLash were you using? I would be surprised if it was an ECUFlash issue as the logging is done in EvoScan.

Jun 25, 2009 | 07:00 AM

#48

evo8426

Evolved Member

iTrader: (27)

Joined: Jan 2006

Posts: 4,248

Likes: 9

From: Charlotte, North Carolina

...nevermind...someone posted a response similar without me noticing

Jun 25, 2009 | 07:52 AM

#49

raasfaas

Thread Starter

Evolved Member

iTrader: (30)

Joined: Oct 2006

Posts: 780

Likes: 0

From: Fl/Jam

Quote:

Originally Posted by wreckleford

What version of ECUFLash were you using? I would be surprised if it was an ECUFlash issue as the logging is done in EvoScan.

Originally I was on 1.29a, then switched to 1.35...now I'm on 1.41
I was wondering if it was an endian issue, because in 1.29a (after you brought it to my attention that they weren't coinciding) the endian for afr in my base xml (among a few other items) from the install was set to "big" and all the rest were "little" so I never bothered to change them I just decided to upgrade to a later version which worked...so I just assumed it was an ecuflash issue.