|
nyet
|
 |
« Reply #15 on: February 25, 2013, 07:16:40 PM »
|
|
|
I've explained all of this in detail in the readiness thread.
Can you suggest wording I can use to improve the s4 wiki? |
|
|
|
|
Logged
|
|
|
|
|
k0mpresd
|
|
« Reply #16 on: February 25, 2013, 07:22:05 PM »
|
|
|
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.
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? |
|
|
|
|
Logged
|
|
|
|
|
phila_dot
|
|
« Reply #17 on: February 25, 2013, 07:42:11 PM »
|
|
|
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#msg25603Trust me...I've gone through these functions numerous times. There really isn't much to it. |
|
|
|
|
Logged
|
|
|
|
|
elRey
|
|
« Reply #18 on: February 25, 2013, 08:06:44 PM »
|
|
|
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?
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. |
|
|
|
« Last Edit: February 25, 2013, 08:09:13 PM by elRey »
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #19 on: February 25, 2013, 08:09:07 PM »
|
|
|
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  |
|
|
|
|
Logged
|
|
|
|
|
k0mpresd
|
|
« Reply #20 on: February 25, 2013, 08:14:46 PM »
|
|
|
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.
so those are the 4 options. thanks. |
|
|
|
|
Logged
|
|
|
|
New2Tune
Full Member
Karma: +3/-1
 Offline
Posts: 55
|
|
« Reply #21 on: May 03, 2013, 10:36:55 AM »
|
|
|
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?
|
|
|
|
|
Logged
|
|
|
|
|
masterj
|
|
« Reply #22 on: May 04, 2013, 01:45:11 AM »
|
|
|
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?
|
|
|
|
|
Logged
|
|
|
|
|
phila_dot
|
|
« Reply #23 on: May 04, 2013, 07:21:07 AM »
|
|
|
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. |
|
|
|
|
Logged
|
|
|
|
|
phila_dot
|
|
« Reply #24 on: May 04, 2013, 07:21:47 AM »
|
|
|
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?
This is pretty well documented. |
|
|
|
|
Logged
|
|
|
|
New2Tune
Full Member
Karma: +3/-1
Offline
Posts: 55
|
|
« Reply #25 on: May 04, 2013, 09:12:40 AM »
|
|
|
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?  |
|
|
|
« Last Edit: May 04, 2013, 09:19:40 AM by New2Tune »
|
Logged
|
|
|
|
|
ddillenger
|
|
« Reply #26 on: May 04, 2013, 09:17:25 AM »
|
|
|
What model/engine do you drive? Ecu number? http://s4wiki.com/wiki/Tuning |
|
|
|
|
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
|
|
|
|
phila_dot
|
|
« Reply #27 on: May 04, 2013, 09:25:28 AM »
|
|
|
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
|
|
|
|
« Last Edit: May 04, 2013, 09:27:31 AM by phila_dot »
|
Logged
|
|
|
|
New2Tune
Full Member
Karma: +3/-1
Offline
Posts: 55
|
|
« Reply #28 on: May 04, 2013, 09:32:07 AM »
|
|
|
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?
|
|
|
|
|
Logged
|
|
|
|
|
phila_dot
|
|
« Reply #29 on: May 04, 2013, 09:33:59 AM »
|
|
|
What monitor are you talking about? Oxygen Sensor(s)?
|
|
|
|
|
Logged
|
|
|
|
|
