VAGCOM logging Q's

[BITRBO]

A couple logging questions for the gurus:

1. Is it me, or when you log multiple blocks (with VAGCOM) does it take FOREVER to circulate back around to any single block? I mean, when I look at the CSV file in Excel, the time stamp for any one block is in increments of ~2.4 seconds! Granted, I was trying to log 9 blocks simulataneously, but still. Does it really take that long to check an individual block? Maybe I'm reading this wrong, IDK... (EDIT: Just read up on it. Multiple logs are baaad for VAGCOM).

2. If the above is true, is the only other way to get simultaneous data for multiple blocks (w/o massive time increments) with APR's ECU-X? I hate to have to buy ANOTHER software I'm trying to get some nice logs of multiple blocks (chipped vs. stock) that I can post up to see if I'm having any issues, but it seems to be really difficult w/ VAGCOM...

3. What is the best methodology when doing logs: Start at ~3k rpm and go WOT until redline (~7k rpm)? Does it matter what gear I'm in? (EDIT: NVM: it's 3rd gear). Does it matter if the a/c is on?

4. What are generally some useful/helpful blocks to log when trouble shooting: Groups 1, 2, 5, 114, 115? When doing a WOT pull I know some sensors just go into a closed loop and stop reading actual data.

5. I have noticed for a while now that there is a block for actual & specified engine torque (in Nm), but is this accurate? If so you could theoretically calculate HP at the crank, no?

(EDIT:) 6. As some of you have read, I have been having fluctuating boost and throttle issues, mostly at cruising speed or at idle. Will doing any 3rd gear WOT logs tell me anything, if my issues are at idle or cruising speed?

Thanks!

EDIT: I had seen this once (ROSS-TECH's website?), but forgot where, so I just answered some of my own questions : http://www.audizine.com/forum/showthread.php?t=115367

[s4nicetry]

A couple logging questions for the gurus:

1. Is it me, or when you log multiple blocks (with VAGCOM) does it take FOREVER to circulate back around to any single block? I mean, when I look at the CSV file in Excel, the time stamp for any one block is in increments of ~2.4 seconds! Granted, I was trying to log 9 blocks simulataneously, but still. Does it really take that long to check an individual block? Maybe I'm reading this wrong, IDK...

2. If the above is true, is the only other way to get simultaneous data for multiple blocks (w/o massive time increments) with APR's ECU-X? I hate to have to buy ANOTHER software I'm trying to get some nice logs of multiple blocks (chipped vs. stock) that I can post up to see if I'm having any issues, but it seems to be really difficult w/ VAGCOM...

3. What is the best methodology when doing logs: Start at ~3k rpm and go WOT until redline (~7k rpm)? Does it matter what gear I'm in? Does it matter if the a/c is on?

4. What are generally some useful/helpful blocks to log when trouble shooting: Groups 1, 2, 5, 114, 115? When doing a WOT pull I know some sensors just go into a closed loop and stop reading actual data.

5. I have noticed for a while now that there is a block for actual & specified engine torque (in Nm), but is this accurate? If so you could theoretically calculate HP at the crank, no?

Thanks!

1 - The more logs you try at once the longer the time interval between points with VAG COM, get ECU-X as it is much quicker running multiple logs. (~14 per second or more) You'll get ~2 per sec with VAG running only 1 log at a time.

2 - Anwered in 1.^

3 - I run about 2500 - 7000 in third. Use 3rd gear as a constant so you can compare your differences whether it be from using lemmi or just checking differences with temp, changing your gas type etc. Make sure your logging on the same flat road as well, and don't worry about your AC.

4 - STFA for a good understanding of the blocks and which ones are the best to use. I personally use 3,4,20,21,31,32,115 for the most part when running logs but there are several more that can be useful tools as well.

5 - Block 120 and yes you could figure out your theoretical hp using this.

[BITRBO]

Sweet - Thanks for the help!

[Mike@Startup]

Vag-com sucks with more then 2 values logging at once. Just do the run a few times, & switch out the values.

I had weird boost issues on my S4, it turned out to be a failing N75, & there were no codes & it passed resistance test.