Readiness - Catalyst
- Thread starter carabuser
- Start date
Ok, i did it right now, i copied in the same root MHD folder (com.mhd.flasher.n54) where is the WBxxxxxx_flashoptions.xml
You should see extra monitoring channels in MHD now. Those need to be ticked for it to record them.
I am not connected to the car right now but i can see three new parameters in data logging options that i can tick :
1 LV_SO2P_CT
1 STATE_NOX
1 STATE_RGN
(however i don't know what MHD did with the new update 2.23 for the login handling but i can't see my purchased license anymore)
You should be on 2.33 now. Some login issues were fixed.
Interested to see the AFR findings.
Thanks, i meant 2.33, it seems that i had some 2FA issues with my Google account, sorted by cleaning cache of Chrome app, now ok license back
Anyway i will able to post some logs in a few hours
Here are the logs with the three parameters ticked.
I don't know if it's relevant, but i have cold start noise reduction and MT shift bog ticked.
First two logs are with MHD Stage 2+.
First log, startup, cold engine : Log link
As you can notice, it starts bouncing around 165 seconds after startup, all the 3 parameters remains the same all this time (0, 0, 3).
The fact that it start to bounce later, means something (one routine or more) is activating, does it activate with water temps? fixed timer ? or maybe something else
Second log, hot idle after a 25 minutes trip : Log 2 link
Still no changes about the 3 parameters ( 0, 0, 3)
After that i flashed my stock bin with the CarAbuser table sent, with 1774 value, to see if it helps : Log 3 stock bin
The idle seems not as bouncy on this one, but the car was just started, as you can see it start to bounce again when i rev it at the end of the log. And still no changes about the 3 parameters ( 0, 0, 3).
I don't know if it's relevant, but i have cold start noise reduction and MT shift bog ticked.
First two logs are with MHD Stage 2+.
First log, startup, cold engine : Log link
As you can notice, it starts bouncing around 165 seconds after startup, all the 3 parameters remains the same all this time (0, 0, 3).
The fact that it start to bounce later, means something (one routine or more) is activating, does it activate with water temps? fixed timer ? or maybe something else
Second log, hot idle after a 25 minutes trip : Log 2 link
Still no changes about the 3 parameters ( 0, 0, 3)
After that i flashed my stock bin with the CarAbuser table sent, with 1774 value, to see if it helps : Log 3 stock bin
The idle seems not as bouncy on this one, but the car was just started, as you can see it start to bounce again when i rev it at the end of the log. And still no changes about the 3 parameters ( 0, 0, 3).
Try setting the byte at 4331C and 4331D from 00 to 01.
4331C should disable lambda stimulation in bank 1 and 4331D should be bank 2.
If that doesn't work I'll send some more params to log.
4331C should disable lambda stimulation in bank 1 and 4331D should be bank 2.
If that doesn't work I'll send some more params to log.
I defined LC_LAMB_PLS_INH in I8A0S a few days ago and got 0x4331E and 0x4331F for the switches.. @studio54 if those values from carabuser don't work try these.
I also got these two hex addresses from a quick hex search.
4331C and 4331D looks to be deactivation toggles for the AFL (Air fuel-lean) diagnosis.
Ok thanks all of you.
I will prepare 2 bins with those, so i can test both tomorrow and see the results on logs.
@carabuser if you want I log some more special parameters, you can send me another xml so we can hit two targets with one bullet
I will prepare 2 bins with those, so i can test both tomorrow and see the results on logs.
@carabuser if you want I log some more special parameters, you can send me another xml so we can hit two targets with one bullet
I did some logs, it's still oscillating.
Logs are probably useless right now but anyway :
First log, 4331E & 4331F to 01 : Log 1
It did the same thing as previously, during 1-2 minutes after cold starting it is almost perfectly steady at 14.6/14.8, and then it start to bounce again, i just logged the bouncing part.
Second log, 4331C & 4331D to 01 : Log 2
When flashing, it's short flashes (2 minutes with my cable), i assume it's ok ?
Let me know what to do next ? new parameters to log ?
Logs are probably useless right now but anyway :
First log, 4331E & 4331F to 01 : Log 1
It did the same thing as previously, during 1-2 minutes after cold starting it is almost perfectly steady at 14.6/14.8, and then it start to bounce again, i just logged the bouncing part.
Second log, 4331C & 4331D to 01 : Log 2
When flashing, it's short flashes (2 minutes with my cable), i assume it's ok ?
Let me know what to do next ? new parameters to log ?
Ok thanks. Yep, that's weird. Does the 2 minute short map write is writing all the tables correctly ?
(Just in case, I sent you one of the bin i used for last logs, just to check if I added the parameters in the XDF the right way)
Sorry for the silly question, but did you select long write because you knew you needed a long write? Or was the MHD app smart enough to require a long write based on differences it saw in the custom map you flashed?
Similar threads
