I have a MY04 with Kraftwerks C38 kit and an AEM Series 2, eTuned by Jeff Evans. He supplied me with tunes on 1v24 firmware, as he said the O2 feedback is iffy on 2v02. Well I decided I wanted to try it anyway, as it added the engine protect features, and I had added in oil temp & pressure sensors to my setup. Sure enough, he was right, and occasionally my idle AFR's would jump up into the 16s for no apparent reason, and would sometimes go very lean while cruising (with cruise control on the interstate, for example), again into the 16s as I recall. Well i went back to the 1v24 firmware the next day after I first noticed this happening, and the problem was immediately resolved.

Has anyone else experienced this when running 2v02 firmware? I'm extremely disappointed with AEM, as they apparently have announced they are no longer working on the Series 2 development, so this is an open issue that won't be addressed (this according to Jeff Evans). I want to contact them about it directly, but haven't found the time yet. In the mean time it would be nice to have an angry mob behind me to hopefully get this issue addressed.

For anyone that is running a series 2, please let me know if you did or did not experience this when running 2v02 firmware, and also if you are DBW or non-DBW (I am non-DBW, for reference).

 

I have tuned about 30 Series IIs on the new 02v02 firmware and have never had this issue, including most being set up with flex fuel and engine protection strategies. Nothing changed regarding O2 feedback with the new update. Please post a datalog of this happening to we can review and it and determine the real cause. This log would of course need to be on 02v02 firmware.

 

That's interesting, thanks for the feedback. When I spoke with Jeff Evans about this a few months ago, he said he's seen it numerous times but it's hit & miss between cars/EMS's. But as stated above, the exact same tune on 1v24 never exhibits the issue, even when downgrading the EMS immediately after seeing it happen and continuing on the drive.

Once I find some time, I'll swap back to 2v02 and try to catch it on a datalog. It's one of those things that's intermittent, which makes it difficult. Seems to happen more on longer drives.

I'm also going in for a proper dyno tune on Monday, and will speak with that tuner about the issue as well to see what he thinks.