NefMoto

real readiness passed hack for sai delete. 100% passes all inspection/emission/readiness tests.

Is this preferred over zeroing CWKONABG? If so, why? TIA :)

That's the only change? Does this require the pump to be installed and connected, or? Good work.

I'm guessing it's the difference between showing 'not equipped/supported' verses tested and 'passed' in emission testing.

I never understood how testers get the 'not supported' status.

vcds will not show "not supported". Some sort of glitch where that unsupported monitors show as passed. I wonder if they know?

If anyone wants to see I can post screenshots from the two programs, vcds showing passed and PPE showing not supported?

Well I thought readiness were bits. If so, how can a bit show 3 different statuses..... statuss.... stati ....

this is real passed. not vcds passed and inspection machine unsupported.

I know, I was just explaining the vcds glitch in case others weren't aware.

What hardware is connected?

n112.

What's PPE? And is there any other ways to view/log the unsupported status?


Why not remove that also? What about pump relay? Is it still connected?

you could i assume, but the car in question has an aeb head and the guy just needed to be able to get it through inspection. pump relay is still there.
just think of it as a standard sai delete. pump, combi, ect are removed.

I'm not sure. PPE=Palmer Performance Engineering. They have diagnostic software and flashing software (mostly for American cars) that I have.

Same file, different software. Codeword block was 00'd. (This has nothing to do with k0mpresd's mod, just illustrates vcds is incorrect in reference to readiness)

(http://i45.tinypic.com/bxv09.jpg)

(http://i50.tinypic.com/cmctw.jpg)

Readiness is real simple, it's two bytes.

The ready byte and evsup1. Ready byte set is failed/incomplete readiness and clear is passed/unsupported. Evsup1 set is supported and clear is unsupported.

There's no VCDS bug. It displays the ready byte and not evsup1.

ESKONF will always be required in order to disconnect hardware.

Edit: I've explained all of this in detail in the readiness thread.

Can you suggest wording I can use to improve the s4 wiki?

there must be more than just failed/incomplete and passed/unsupported.
what makes the difference between the 4? if theres only 2 bytes, then why are there 4 choices?

Ready is initialized with evsup1. If a monitor is unsupported in evsup1 (clear) then the corressponding ready bit is cleared (pass) on initialization. If a monitor is supported in evsup1 (set) then the corresponding ready bit is set on initialization (failed/incomplete). The ready bit will then be cleared (pass) if the testing is complete, Z flags set, and there are no errors, E flags clear.

Therefore, a clear ready bit equals a pass or that it's unsupported and a set ready equals a failed or incomplete test.

More on evsup1:
http://nefariousmotorsports.com/forum/index.php?topic=615.msg25603#msg25603

Trust me...I've gone through these functions numerous times. There really isn't much to it.

B_cdsls = 1:

evsup1 : readiness : emission status
1 : 1 : failed/incomplete
1 : 0 : passed

B_cdsls = 0:

evsup1 : readiness : emission status
0 : 0 : unsupported (but shows passed in VCDS)
0 : 1 : never happens

upon code reset, readiness is set = to evsup1 which is set based on codewords.

Let me ask again:

Can somebody be so kind as to provide me with (accurate) wording I can use in the s4wiki? I'm really unhappy with what is there now since it doesn't make any damn sense.

Thanks :)

so those are the 4 options. thanks.  :)

So any such luck on a similar approach to O2 readiness?

As in secondary O2 is supported, EVSUP1 and codewords show this, the test runs and the results are always acceptable?

What happens with whole bunch of SAI functions with this hack? If we leave cdsls = 1 then ecu thinks it still can use sai and affects mixture (injected secondary air) on idle or no? Has anyone checked the SAI group in vcds? What amount of secondary air it shows?

For SAI delete files, I used a few codewords (can't remember exactly which ones) which disable all SAI functions, ESKONF (for component removal), and an ASM hack to take care of evsup1.

Readiness still sets immediately because the Z flag is set and E flag is cleared from the codewords, but evsup1 remains set.

This method could be improved I think by forcing the cycle counter to be evaluted against the readiness threshold even in the absence of set E flags. This should keep readiness from being set immediatley after reset.

This is pretty well documented.

So I read the 16 page thread on setting readiness and there are many different ideas in there but I didn't see any kind of clear consensus/explanation?

The ASM hack for getting EVSUP 1 was mentioned there and then just again here but is there example/documentation of that?

There was speculation of SRY* Thresholds but also didn't see any outcome?

Unsupported is simple but that doesn't cut it in my case so I'm looking to understand a means of being supported and still passing readiness for secondary O2.  Maybe it is fully explained there and there is either too much conflicting information to wade through, or I'm a couple IQ points away from catching it? ???

What model/engine do you drive? Ecu number?

http://s4wiki.com/wiki/Tuning

I'll give you that, that thread is progressive, so you want to focus on the info towards the end.

S4wiki is a good consolidation as DD linked above.

Edit: want to clarify that ASM hack is not required or recommended for rear O2 delete

So I believe I have followed the method outlined in the S4 wiki correctly, and it passes VAGCOM's readiness but still shows unsupported in a more sophisticated tester?

My ECU is 8E0909518AF for an 03 A4

That is a consequence of CDKAT going to zero for example correct?  I'm looking for how to have it pass readiness and be supported, maybe I'm missing something but that's not covered in the wiki is it?

What monitor are you talking about? Oxygen Sensor(s)?

Yes, specifically I'm looking to be able to show supported and passed without a CAT.

I think I'm starting to get it...  Looks like CDKAT might not directly affect EVSUP1 and thus you can disable secondary O2 without messing up supported/unsupported?  Is that part of what you're getting at with not needing an ASM hack for just the secondary O2?

But with codewords/systems that do impact EVSUP1 you've got a more complicated issue?

You wouldn't happen to be able to elaborate on ESKONF?

ESKONF is best understood by reading the FR. Search for the DEKON module, translate it, and go to town. If you have specific questions I'll try my best to help, but I just managed to wrap my head around it recently.

As dd said, the chart in the FR about ESKONF is absolutely the best place to start. It's for a 1.8t but it shows you how Bosch calculates the values for ESKONF.


I uploaded the DEKON module to the translated FR thread I believe.

ESKONF is not difficult to understand. For those who require an english version of documentation read the Alfa FR!
BUT we lack alot of information about how to evaluate ASM or a combination with traces on ecu PCB to identify the correct pair of bits for specific functions.
ESKONF layout differs quite alot between ecus.

This is where I'm at with it. If every software were setup the same it wouldn't be an issue.

I've not looked closely at the ASM code call to ESKONF function but if we can do a hack which allows it to do it's thing with only ignition on it would be easy to find out what is what.
Then by flashing a few different ESKONF configs it would be a piece of cake to disconnect connectors one by one to identify ESKONF bits.
Now it's a bit difficult since you need to drive the car before fault code appears.

Just to be clear when the correct bits are set in ESKONF as philla_dot describes along with the other code words for secondary O2 removal, the readiness behavior will be as expected and will pass more sophisticated testers?

IE some time needed to set readiness, readiness is set to incomplete/failed when cleared and then comes back?
I'm pretty much at trial and error on the bits right now and just want to be sure I'm chasing the right thing.

A question to disable SAI:

If you teek MSLBAS and MSLUB and disable powersupply to secoundary airpump, is it also useful to set KFFMSML to zero, to not (in)correct exhaust back pressure in order to (not awaillable)secoundar air mass ?

Excellent question, and one that I did try to figure out, but I no longer have the car to experiment on. I would tend to say yes but I don't have facts to back it up.

EDIT: My bad, disabling SLS sets SAI as unsupported I think... not passed.

My gut feeling tells me that disabling the SLS function in CWKONABG would make that unnecessary.

A word of warning, from my brief research different ECUs do this differently.

When you just teek MSLBAS and MSLUB, SLS function is still activ, but no airflow is a valid situation, while SAI is "running".

CWKONABG will have effect to readyness, AFAIR..