ESKONF and disabling evap

Pages: 1 2 [3]

« previous next »

Author

Topic: ESKONF and disabling evap (Read 24548 times)

16g-95gsc

Full Member

Karma: +1/-1
Offline

Offline

Posts: 73

	Re: ESKONF and disabling evap « Reply #30 on: March 23, 2014, 11:39:44 AM »

Has anyone identified what adjustments are necessary to remove the N80 and N249 valves? I ignorantly removed the N80 valve (and subsequently disposed of it) and it appears my fuel trims are dead in the water without it being accounted for.

Can anyone explain just what the purpose of the OEM killing fuel trims when ESKONF picks up a non-existent valve that should be there otherwise? I haven't wrapped my head around why this is the response in the system, I just accept it as true.


	Logged

ddillenger

Hero Member

Karma: +641/-21
Offline

Offline

Posts: 5640

	Re: ESKONF and disabling evap « Reply #31 on: March 23, 2014, 12:00:12 PM »

Unlike the 1.8, there is no plausibility diagnosis on the N249, so just ESKONF is sufficient. As for the N80, you need CDTES, CDLDP, and ESKONF.

As for the logic, I have no idea. I assume it's to prevent a bad component from severely impacting fueling.


	Logged

Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience!

Email/Google chat:
DDillenger84(at)gmail(dot)com

Email>PM

16g-95gsc

Full Member

Karma: +1/-1
Offline

Offline

Posts: 73

	Re: ESKONF and disabling evap « Reply #32 on: March 23, 2014, 05:24:48 PM »

Thank you for the reply.

What about CLATEVE and CLALDPE? I have set all of these parameters to 0 from the start, so I have not received any DTC's since day one, but I am curious why you say only CDLDP and CDTES are necessary (this is more of a teach a man to fish type question).

Am I incorrect in that the STFT's remain active with an incorrect ESKONF, but LTFT's are disabled?


	Logged

ddillenger

Hero Member

Karma: +641/-21
Offline

Offline

Posts: 5640

	Re: ESKONF and disabling evap « Reply #33 on: March 23, 2014, 05:34:35 PM »

When properly coded out via ESKONF, error classes aren't needed.


	Logged

16g-95gsc

Full Member

Karma: +1/-1
Offline

Offline

Posts: 73

	Re: ESKONF and disabling evap « Reply #34 on: March 26, 2014, 05:53:37 AM »

Bytes 11 through 13 which should refer to locations 10C7F-10C81 all show as 55 (hex) when I look them up on my stock M-box bin file. 55 translates to bit pairs: 01010101

What the heck is 01?


	Logged

Pages: 1 2 [3]

« previous next »

Jump to:

Navigation

Personal Tools

November 17, 2024, 08:49:58 AM

Welcome, Guest. Please login or register.
Did you miss your activation email?

Navigation

Personal Tools

Search