open up measuring block 3, then click log, then click start. check it at warm idle (800 rpm) shoulf be ~4-5 g/s. Then you can road test it, get up in to 2nd gear at about 1500 rpm, press the gas to the floor and hold it to redline. then press stop to close the data file.

open it in excel, you can make a picture like this if it's working properly:

 

Do i access block 3 when engine started ? or do i start after i click "log" ?

/Jonas

 

sure, start the car first, then open vagcom, go to engine then measuring blocks then type in 003 in one of the three fields. you will see the live data at this point and can take down the idle reading. then press the log button, then the start button. easy!

 

Measuring Block 002. I've made my own XLS to represent some data. It is maybe not that acurate but gives good impressions when making mods.

Here's my latest graph

Purple line is the MAF reading. Here's the how-to:

1. Read the actual mbar with ignition on/engine off, MB 115. You will need this value in the data sheet (S1)
2. Determine the injector size@4bar, I'm still using 210cc@3bar which is 242cc@4bar. Still have no info about the actual injector size of my APU engine. They could be 270cc@3bar though, it only affects AFR. S2 in XLS.
3. Activate MB 120, 115 and 002 and make a run in 3rd gear from ~1000 RPM to redline (~6500 RPM) on a flat road
4. Import the CSV in the XLS at A1. Remember to change the decimal & thousand delimiter. We use comma for decimal and point for thousand delimiter. The CVS is US spec so change these delimiters while importing the data. Also use comma as the CSV delimiter
5. Skip all the useless data and your done

The original XLS is here

 

Oops, my posting was a bit longer to type. There are several ways to log the MAF reading!

 

sure, start the car first, then open vagcom, go to engine then measuring blocks then type in 003 in one of the three fields. you will see the live data at this point and can take down the idle reading. then press the log button, then the start button. easy!

i only get "baud sync fail" when i try to get in to "Engine" with engine idleing.

Nice XLS-sheet Dutch cant say i really understand it butt ill try get all data as u describe.

/Jonas

 

VAG-COM is not my favorite when it comes to reliability and sample rate for measuring blocks. I'm still having communication problems sometimes. Though not baud sync fail. When engine is off all is fine, as soon as engine starts troubles begin.

COM-port should be 9600,8,N,1 w/ no flow control. VAG-COM test the link first, COM test and OBDII test.

 

VAG-COM is not my favorite when it comes to reliability and sample rate for measuring blocks. I'm still having communication problems sometimes. Though not baud sync fail. When engine is off all is fine, as soon as engine starts troubles begin.

COM-port should be 9600,8,N,1 w/ no flow control. VAG-COM test the link first, COM test and OBDII test.

I will try these setting, but i have no problem with ex. automatic readings when driving or any other readings with only ignition on.

Thanks again

 

The whole idea of "measuring blocks" is that they try to group data that is useful into the same measuring block... logging block 002 will show MAF data vs. throttle position, while logging block 003 will show MAF data vs. engine timing. (I may have these backwards, but you get the idea...)

If you log more than one block, make sure that you use the time stamp for that block when plotting that block's data. (use the correct "X" for each "Y").

 

still cant get my VAG-COM to read 01-Engine while engine is running... Only clicks from dashboard and the "Failed to sunch baud rate" I have tried 2 different Laptops, on is freshly installed with W2k indead of XP.

I have no problem reading 01.Engine when its turned off, or reading transmission when its running.

Anyone else hade this problem ? and how did u solve it.

Im using a Dell Latitude C600 512Ram P-III 700mhz CPU.

Regards Jonas

 

have you updated your SW recently?

 

I have a C600/128MB/PIII600/W2k which runs fine and a C600/256MB/PIII750/W2k and does the same as you describe, I've killed almost every process/task/whatever, still no communication with engine running. Haven't solved it yet, a fresh install might help.

 

What SW? W2K patches/fixes or virus?

 

What SW? W2K patches/fixes or virus?

i have a old version of VAG-COM but i have tried the latest 5.09 from ross-tech.com i Only have activation for old 3.xx something.

I reinstalled W2k yesterday and only installed VAG-COM. No other applications at all. No updates/patches or fixes yet and no virusscan installed.

/Jonas

 

I don't know what cable your using (3rd party or OEM Ross-Tech) but the first will only work until 3.11 (latest shareware).

W2K SP4 would be the only extra SW you should install.

 

I don't know what cable your using (3rd party or OEM Ross-Tech) but the first will only work until 3.11 (latest shareware).

W2K SP4 would be the only extra SW you should install.

Im using seriell cable and a 3:rd party odb-II box. I will upgrade o SP4 and give it another go.

/Jonas