RS4boost
Full Member
Karma: +46/-0
 Offline
Posts: 125
|
 |
« Reply #195 on: August 22, 2012, 02:05:24 PM »
|
|
|
Ok very interesting. Only flashed in bootmode and done? And the car runs without problems? |
|
|
|
|
Logged
|
|
|
|
|
prj
|
|
« Reply #196 on: August 22, 2012, 02:29:14 PM »
|
|
|
Ok very interesting.
Only flashed in bootmode and done?
And the car runs without problems?
Yes... After you flash to 551K in boot mode you can flash over OBD. |
|
|
|
|
Logged
|
|
|
|
RS4boost
Full Member
Karma: +46/-0
Offline
Posts: 125
|
|
« Reply #197 on: August 22, 2012, 11:23:10 PM »
|
|
|
Yes...
After you flash to 551K in boot mode you can flash over OBD.
Thank you for sharing this info...  |
|
|
|
|
Logged
|
|
|
|
|
professor
|
|
« Reply #198 on: August 31, 2012, 10:48:18 AM »
|
|
|
.Got error -8
What it mean guys?
|
|
|
|
|
Logged
|
Seat Ibiza MK4 Cupra 1.8t 20V, stg3.
"Those 1.8T 20V machines are really tough" ©
|
|
|
Michel94
Jr. Member
Karma: +0/-0
Offline
Posts: 31
|
|
« Reply #199 on: September 01, 2012, 01:46:07 AM »
|
|
|
Thank you for sharing this info... And K-box flash with F file works ? |
|
|
|
|
Logged
|
|
|
|
|
prj
|
|
« Reply #200 on: September 01, 2012, 02:33:56 AM »
|
|
|
And K-box flash with F file works ? Most likely, but I would not do this, because F does not have misfire recognition while K does. |
|
|
|
|
Logged
|
|
|
|
Il Signor Zetec
Jr. Member
Karma: +0/-4
Offline
Posts: 48
|
|
« Reply #201 on: September 16, 2012, 01:56:27 PM »
|
|
|
- connection method "double slowinit" added (helps with "instrument cluster" problem)
To use double slowinit set in the [Communication] section of the .ecu file:
Connect = SLOW-0x00
DoubleDelay = 12 ; Possible values 1 .. 100 (delay in 100ms)
This allows to connect only while engine not yet started.
hello Setzi, thank you for your useful tool. I had the same problem described here: http://nefariousmotorsports.com/forum/index.php?topic=837.msg16551#msg16551I used a particular charateristics file for my ecu (8N0906018J) with slow init. During the mods on the .ecu file I didn't find a row to mod the double delay time. Also changing the whole rows in [connection] with your Connect = SLOW-0x00 DoubleDelay = 12 ; Possible values 1 .. 100 (delay in 100ms) I can't connect to the ecu (error = cause<0x04> ) Then the solution is to put a dedicated K line from ecu? Can I do any other test? |
|
|
|
|
Logged
|
|
|
|
Il Signor Zetec
Jr. Member
Karma: +0/-4
Offline
Posts: 48
|
|
« Reply #202 on: September 23, 2012, 03:09:31 AM »
|
|
|
I used a directly connect K line cable. Now all work good
|
|
|
|
|
Logged
|
|
|
|
Milka
Full Member
Karma: +3/-0
Offline
Posts: 129
|
|
« Reply #203 on: September 27, 2012, 04:58:21 AM »
|
|
|
Really great tool, worked first time I tried it on an RS6.
I do have a request is it possible to get modified Defs so that ME7Info can map dual MAFs? Currently I have the following:
msdk_w mshfm_w uhfm_w
From what I can tell the first 2 are combined values but the last one is voltage and I think is for an individual sensor? I would love to have voltage and g/s for each MAF.
Thanks
|
|
|
|
|
Logged
|
|
|
|
|
prj
|
|
« Reply #204 on: September 27, 2012, 05:56:34 AM »
|
|
|
You can get them by disassembly Does VAG-COM support showing the mass flow over each MAF? If yes, try printing the measuring block info with me7logger and seeing what it reports. |
|
|
|
|
Logged
|
|
|
|
|
phila_dot
|
|
« Reply #205 on: September 27, 2012, 06:02:23 AM »
|
|
|
It will almost definitely be located directly before or after in RAM.
|
|
|
|
|
Logged
|
|
|
|
Milka
Full Member
Karma: +3/-0
Offline
Posts: 129
|
|
« Reply #206 on: September 27, 2012, 07:01:49 AM »
|
|
|
Thanks guys. Yep, through VCDS I have a combined g/s which maxes out at 364 while the individual MAF values continue to rise. I will try to get the info and post it tomorrow (Aus time).
prj, I'm still working on clutch switch wiring, will be in contact very soon
|
|
|
|
|
Logged
|
|
|
|
|
prj
|
|
« Reply #207 on: September 27, 2012, 07:25:58 AM »
|
|
|
My question was not because you should log with VCDS. My question was because if you can see this with VCDS, then use ME7Info-s functionality to print information about measuring blocks. This will yield the addresses most likely, IF it is possible to log them with VCDS. Now you see where I was going with this  |
|
|
|
|
Logged
|
|
|
|
Milka
Full Member
Karma: +3/-0
Offline
Posts: 129
|
|
« Reply #208 on: September 27, 2012, 07:57:35 AM »
|
|
|
Yep I realised that, was just stating what VCDS has. I did not know that ME7Info had that option (probably should check the options)
Just ran it with -g option, then looked up measuring block 2
measgroup 002: 0001(nmot ) 0002(rl ) 0394( ) 0395( )
Not sure how I log these in ME7Logger yet, will try and figure it out.
Last 2 are the individual MAF readings g/s, there is no MAF voltage in the measuring blocks but I think I have one of those mapped already in the full .ecu file (just to see when I get close to maxing out the MAFs)
|
|
|
|
|
Logged
|
|
|
|
|
prj
|
|
« Reply #209 on: September 27, 2012, 08:42:16 AM »
|
|
|
Ha, it seems empty in ME7Logger. Maybe something for setzi to work on.
But it's pretty easy to find in ASM if it's in the measuring blocks.
|
|
|
|
|
Logged
|
|
|
|
|
