Pages: 1 ... 11 12 [13] 14 15 ... 26
Author Topic: Emissions delete and setting actual readiness  (Read 369377 times)
prj
Hero Member
*****

Karma: +1072/-480
Offline Offline

Posts: 6035


« Reply #180 on: October 30, 2012, 06:01:16 AM »

I'm assuming for RS4 K/Q box no changes will be needed since there are no rear O2s on the RS4?

Uhm, yes there are. At least on K-box.
My RS4 has (or had) rear O2's, cats, SAI and so on.
« Last Edit: October 30, 2012, 06:05:24 AM by prj » Logged

PM's will not be answered, so don't even try.
Log your car properly - WinOLS database - Tools/patches
nyet
Administrator
Hero Member
*****

Karma: +607/-168
Online Online

Posts: 12268


WWW
« Reply #181 on: October 30, 2012, 10:28:05 AM »

So we'll need to figure out ESKONF bits if we want to use K/Q then.. :/
Logged

ME7.1 tuning guide
ECUx Plot
ME7Sum checksum
Trim heatmap tool

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! 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 ex
prj
Hero Member
*****

Karma: +1072/-480
Offline Offline

Posts: 6035


« Reply #182 on: October 30, 2012, 12:57:38 PM »

So we'll need to figure out ESKONF bits if we want to use K/Q then.. :/

May I ask why? And they are probably exactly the same as M-Box, because the hardware is the same.
matchew pointed out that removal of SAI does not affect learning of fuel trims on K-Box.
Logged

PM's will not be answered, so don't even try.
Log your car properly - WinOLS database - Tools/patches
masterj
Hero Member
*****

Karma: +62/-5
Offline Offline

Posts: 1049



WWW
« Reply #183 on: November 01, 2012, 08:28:37 AM »

hehe... tried to generate path of how variables affect each other.... Final variables are important output variables from main functions, while top is reserved for maps and still undefined variables... Smiley I know that most people will find this silly but at least to me this is way easier to see what's going on with variables when we zero out maps

These functions have been analyzed:
ATM
BBKHZ
DHLSHK
DHLSHKE
DIMC
DKATLRS
DLSAHK
DLSH
DLSSA
DSLSLRS
KHMD
LAKH
LRSHK
SLS
TC1MOD
TC6MOD


By the way, I think that it is useful to force b_sbbhk = 1 because that way we enable auto clear of precat o2 sensor errors when we change sensor or it is back to normal readings (more info in DLSU)
« Last Edit: November 05, 2012, 04:47:32 PM by masterj » Logged

masterj
Hero Member
*****

Karma: +62/-5
Offline Offline

Posts: 1049



WWW
« Reply #184 on: November 04, 2012, 07:50:22 PM »

One more thing: After studying ATM (exhaust gas temp model) I've found a way to update it for test pipes/decats.

First we have to set B_trkh = 0, B_kh =0, B_kw = 0 to fix tatmsta.

CWKONABG.0 = 0 >>> B_katfz = 0 >>> B_kha = 0 >>> B_trkh = 0
CWKONABG.0 = 0 >>> B_katfz = 0 >>> B_kh =0
TKATW = F(max) >>> B_kw = 0


Now we have to fix two subfunctions for TIKATM and TKATM variables by setting these values:
ZATMIKML = 1 && ZATMIKKML = 1 && texoikm_w = 0 (TABGMEX = F(max) && TIKATMOE = 0) >>> tikatm_w = tabgm

ZATMKML = 1 && ZATMKKML = 1 && texom_w = 0 (TABGMEX = F(max) && TKATMOE = 0) >>> tkatm_w = tabgm

UPDATE: One more interesting thing with these models that I found is that until start up timer passes all these variables are preset to TATMTP map, which in most files is set to 60 C. That means, that for some time after starting engine ecu will think that your EGTs are 60 degrees...

SUMMARY:
CWKONABG.0 = 0
TKATW = F(max)
TABGMEX = F(max)
TIKATMOE = 0
TKATMOE = 0
ZATMIKML = 1
ZATMIKKML = 1
ZATMKML = 1
ZATMKKML = 1


Here's hoping there won't be any problems in other functions (haven't looked through all of them yet) Smiley
« Last Edit: December 10, 2012, 12:33:16 PM by masterj » Logged

masterj
Hero Member
*****

Karma: +62/-5
Offline Offline

Posts: 1049



WWW
« Reply #185 on: November 28, 2012, 08:01:27 PM »

Small suggestion to people who fixed ATM (exhaust gas temp model) like I said earlier:
I know this might be a childs play, but I like to set my LAMBTS to work properly and there are few things to check regarding decat...

First thing here is to check if CWLAMBTS.2 = 1. That way we tell ecu to use tabgkrm_w (temp in exhaust manifold) for FBSTABGM instead of modelled temp before cat. Technically it isn't needed and that almost makes no difference, but most of the time you want to set FBSTABGM multiplier based on exhaust manifold temp instead of precat (which it isn't here anyway) temp.

CWLAMBTS.2 = 1 >>> tabgkrm_w in FBSTABGM

Finally, you have option to disable cat and precat temp enrichments (if you haven't fixed ATM!). To do this just FF TKATBTS & TIKATBTS. Or if you fixed ATM you can do it like me:
TKATBTS = TABGBTS >>> fix B_tkatbts && TIKATBTS = TABGBTS >>> fix B_tikatbts

SUMMARY:
CWLAMBTS.2 = 1
TKATBTS = TABGBTS
TIKATBTS = TABGBTS
Logged

masterj
Hero Member
*****

Karma: +62/-5
Offline Offline

Posts: 1049



WWW
« Reply #186 on: December 06, 2012, 07:11:15 PM »

I have started (again) to gather info on variables that we change with map changes. At the moment I have written PROKONAL, LRSHK, LRSKA functions variables, but I will add more when I'll have time Smiley

LEFT SIDE - sorted by functions
RIGHT SIDE - all variables sorted by variable name


Now If you wan't to generate graph out of this data then just use yEd Graph Editor and feed the right side Wink

If anyone has some free time and want to play with dissassembly then it would be a good idea to check if variables are really created and read like FR doc shows us.. Also there are some variables with ? ? ? - that means I haven't found out what happends to these variables after ouput from ori function (FR document)

Also, I'll delete some of these maps when I check all the functions and find out that they can be overwritten by other maps to keep the map list as short as possible.

Another thing: This isn't same list as at the end of FR document, because this includes EVERY single functions that mentions said variables, for example DIMC function isn't shown in the end as few others Smiley
Logged

masterj
Hero Member
*****

Karma: +62/-5
Offline Offline

Posts: 1049



WWW
« Reply #187 on: December 10, 2012, 08:01:16 PM »

Some more new info on my analysis here:
ATM:
After complete checking of this function I've realized that some of my suggestions here can be skipped, in particular variables TIKATM_W, TIKATM, TKATM_W, TKATM can be ignored when diagnostic functions DLSH, DLSAHK, DHLSHK, DSLSLRS, DKATLRS are disabled AND LAMBTS, LRSKA, BBSAWE, LRSHK are fixed as shown further down on this post.
Although TIKATM_W, TIKATM, TKATM_W, TKATM can be ignored I choose to leave my previous temperature model fix in my file, if you want to do same (just for the sake of "correct" value Wink) check this out:
ZATMIKML = 1 && ZATMIKKML = 1 && texoikm_w = 0 (TABGMEX = F(max) && TIKATMOE = 0) >>> tikatm_w = tabgm
ZATMKML = 1 && ZATMKKML = 1 && texom_w = 0 (TABGMEX = F(max) && TKATMOE = 0) >>> tkatm_w = tabgm


Now second part of my suggestion was to fix TATMSTA and this still applies after complete function check:
CWKONABG.0 = 0 >>> B_katfz = 0 >>> B_kha = 0 >>> B_trkh = 0
CWKONABG.0 = 0 >>> B_katfz = 0 >>> B_kh =0
TKATW = F(max) >>> B_kw = 0



LAMBTS:
Some corrections here too:
CWLAMBTS.2 = 1 (result: TABGBTS_W = tabgkrm_w)
TKATBTS = FF && DTBTS = 0 (result: B_TKATBTS = 0)
TIKATBTS = FF && DTBTS = 0 (result: B_TIKATBTS = 0)


LRSHK:
So far I've chosen to set CLRSHK.0 = 1 && CLRSHK.1 = 1 to get B_LRHK = 0 && DLAHI_W = 0 && DLAHP_W = 0. Still no idea what to do with output variables LAMSOLH_W, LAMSONH_W, USRHK  Huh


LRSKA:
In my file originally CLRSKA was set to 0. After looking at the FR I've decided to leave CLRSKA = 0 (CLRSKA.0 = 0 in particular), to get B_LRKA = 0 && LAMKA_W = 8.


BBSAWE:
Finally I have came to fuel cut-off function to check for tkatm variable. To disable unneeded cat related cut-off latency (TVSAKAT=0) I've set KFTVSAKAT = 0. Also in BTATMSA subfunction I've decided to max out TKATSA, TAVHKSAO, TKIHKSAO so fuel cut-off couldn't be stopped from kicking in due to cat (I know that I could leave TAVHKSAO & TKIHKSAO since those are for precat/maincat systems, but for the sake of clean analysis I FF'd them too Wink):
TKATSA = FF
TAVHKSAO = FF
TKIHKSAO = FF




Currently, I think I have done ATM and LAMBTS 100%, while other functions might need some fine tuning. Also please keep in mind that I'm doing this all on FR level and do not check if FR doc == ASM code Smiley

P.S> More info in attached files
Logged

masterj
Hero Member
*****

Karma: +62/-5
Offline Offline

Posts: 1049



WWW
« Reply #188 on: December 11, 2012, 02:41:34 PM »

Update  Smiley
Logged

masterj
Hero Member
*****

Karma: +62/-5
Offline Offline

Posts: 1049



WWW
« Reply #189 on: December 30, 2012, 03:03:47 PM »

OK, added new functions to the list:
BBDLS
BBKHZ
DIMC
GGLSH
KHMD
PROKONAL
SLS
TC1MOD
TC6MOD
TEMPKON


Problem with DEKON function. I have no idea what variables (names?) goes out of ESKONF map and to which functions these variables go (maybe DEVE, DECJ?). Any input on this map would be appreciated Wink

Everything I do know is recorded in excel file attached below
Logged

catbed
Sr. Member
****

Karma: +8/-2
Offline Offline

Posts: 300


« Reply #190 on: January 05, 2013, 10:14:30 AM »



I started trying to correctly code out my rear o2s and SAI. I have set the various codeworts from phila_dots post on page 9, and have found ESKONF at 10D27 in my bin (018ch). I set all the codewords, but did not change ESKONF, then went for a drive. I threw a code for open circuit sensor 2, but the MIL was not lit up. So I went back and changed ESKONF, the 3rd bit. It was originally 048, but I changed it to 240. The DTC is now gone, but the readiness shows incomplete or not ready. The post-cat o2 sensor heater is still being activated, I can see the request through measuring blocks in VAGCOM.

This is what I have done:

CDKAT = 0
CWDLSAHK = 0
CDHSH = 0
CDHSHE = 0
CDLATV = 0
CDLASH = 0
CDLSH = 0
CLRSHK = 5
CWKONLS = 1
ESKONF - as described above

Could CDLSHV cause this problem? That is the only codeword I can't find in my XDF/.kp. I see CDLSHV in the FR but I couldn't find what it does.
« Last Edit: January 06, 2013, 04:33:03 AM by catbed » Logged
c00teriyf
Newbie
*

Karma: +4/-0
Offline Offline

Posts: 22


« Reply #191 on: January 06, 2013, 06:12:10 PM »

Hello, question.  I am just starting to get into understanding how to code out DTCs. Mine will be work a 4.2 V8. I understand that the locations will be different (and I still don't really understand how to find them with that equation but I will keep at it). But my question is will the nomenclatures or parameters be the same.

IE:

CDKAT, CWDLSAHK, CDHSH, CDHSHE, CDLATV, CDLASH, CDLSH, CLRSHK, CWKONLS, ESKONF...etc etc. for the various items I will be coding out? I wouldn't imagine that would change.
Logged
phila_dot
Hero Member
*****

Karma: +173/-11
Offline Offline

Posts: 1709


« Reply #192 on: January 06, 2013, 07:39:33 PM »


I started trying to correctly code out my rear o2s and SAI. I have set the various codeworts from phila_dots post on page 9, and have found ESKONF at 10D27 in my bin (018ch). I set all the codewords, but did not change ESKONF, then went for a drive. I threw a code for open circuit sensor 2, but the MIL was not lit up. So I went back and changed ESKONF, the 3rd bit. It was originally 048, but I changed it to 240. The DTC is now gone, but the readiness shows incomplete or not ready. The post-cat o2 sensor heater is still being activated, I can see the request through measuring blocks in VAGCOM.

This is what I have done:

CDKAT = 0
CWDLSAHK = 0
CDHSH = 0
CDHSHE = 0
CDLATV = 0
CDLASH = 0
CDLSH = 0
CLRSHK = 5
CWKONLS = 1
ESKONF - as described above

Could CDLSHV cause this problem? That is the only codeword I can't find in my XDF/.kp. I see CDLSHV in the FR but I couldn't find what it does.

Wideband ECU?

What are you seeing in VCDS? B_hshe?

What isn't passing readiness O2 sensors or O2 heaters?

Log the cycle and error flags listed in DIMC to see exactly why readiness isn't complete.

CDLSHV is the codeword for function DLSHV which tests if the post cat O2's are interchanged/swapped between B1 and B2. The only outputs are lamlshv_w to %LAMKO and DTC P3262. This doesn't affect readiness.
Logged
phila_dot
Hero Member
*****

Karma: +173/-11
Offline Offline

Posts: 1709


« Reply #193 on: January 06, 2013, 07:45:47 PM »

Hello, question.  I am just starting to get into understanding how to code out DTCs. Mine will be work a 4.2 V8. I understand that the locations will be different (and I still don't really understand how to find them with that equation but I will keep at it). But my question is will the nomenclatures or parameters be the same.

IE:

CDKAT, CWDLSAHK, CDHSH, CDHSHE, CDLATV, CDLASH, CDLSH, CLRSHK, CWKONLS, ESKONF...etc etc. for the various items I will be coding out? I wouldn't imagine that would change.

For the most part.

One difference you will see is LRS vs LR. You listed CLRSHK, but I would list CLRHK.

Wideband is continuous lambda regulation (LRS), narrowband is not (LR).
Logged
catbed
Sr. Member
****

Karma: +8/-2
Offline Offline

Posts: 300


« Reply #194 on: January 07, 2013, 03:32:06 PM »

Wideband ECU?

What are you seeing in VCDS? B_hshe?

What isn't passing readiness O2 sensors or O2 heaters?

Log the cycle and error flags listed in DIMC to see exactly why readiness isn't complete.

Yes, wideband ECU. I am not quite sure of the name of the value in VCDS, but I believe it was block 041. The o2 sensors were not passing readiness, but I just put more miles on it and checked again and they all read PASSED!   Cheesy But now I'm throwing a code for b1s1 malfunction in circuit, though I believe that is unrelated. Now the question is if Jersey will pass inspection on my car.  Roll Eyes
Logged
Pages: 1 ... 11 12 [13] 14 15 ... 26
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.029 seconds with 17 queries. (Pretty URLs adds 0.001s, 0q)