**** Guide on How to Take and Graph Logs ****

[jibberjive]

Since this took me a lot of hours to cobble together myself, and a good few days to get everything working together, I figure I'd put up a step-by-step 'How To' thread to help shorten that learning curve to like 30 mins for people. Shout out to Tony@NefMoto for creating the forum, Setzi for creating the powerful logging utility, j2mc for creating the logger GUI, and for Nyet for developing (and maintaining with upgrades) the ECUxPlot. Extra props to them for not only developing them, but for releasing them for the public to use.

This is just a "quick start" guide to start logging your car. To learn how to interpret the logs and tune your car, it's going to require a lot more substantial of an effort and research. For that, I suggest the forums over at www.nefmoto.com (http://www.nefmoto.com).

COMPLETE GUIDE ON HOW TO TAKE LOGS:

0. Buy the blue "409.1 FT232RL OBD2" cable from this seller:
http://stores.ebay.com/alpha-bid

0.5 Go to www.nefmoto.com (http://www.nefmoto.com) and register for the forums (you need to be registered to download the attachments).

1. Download the driver for that cable from the first post here (it's FTDI D2XX), and install it:
http://nefariousmotorsports.com/forum/index.php?topic=2200.0title=

2. Go to this thread and download/unzip the latest version of Setzi's ME7logger (as of this post, it's V1.17, it's attached to the first post in that thread):
http://nefariousmotorsports.com/forum/index.php?topic=837.0

3. Go to this thread and download the GUI attached to the first post. Place the GUI in the ME7logger folder. Make a shortcut for the GUI on your desktop:
http://nefariousmotorsports.com/forum/index.php?topic=1079.0title=

4. Go to one of the following links to download your ECU's .bin file. Place the .bin file in the ME7logger folder.
--Audi RS6 4.2TT BCY 0261207857 4D1907558 366304 (http://nefariousmotorsports.com/forum/index.php?action=dlattach;topic=49.0;attach=64)
--Audi RS6 4.2TT BCY 450HP 4D1907558 0261207857 367724 (http://nefariousmotorsports.com/forum/index.php?action=dlattach;topic=1476.0;attach=2048 )
--RS6 4D1907558 0004 0261207857 367724 (http://nefariousmotorsports.com/forum/index.php?action=dlattach;topic=47.0;attach=62) (not sure if this is the same as the first one or not)
--Audi RS6 4.2TT BCY 450HP 4D1907558B 0261208051 1037368087 (http://nefariousmotorsports.com/forum/index.php?topic=2645.msg25066#msg25066)
--Audi RS6 Plus 4.2TT BRV 480HP 4D1907558F 0261208728 1037370934 (http://nefariousmotorsports.com/forum/index.php?topic=2646.msg25067#msg25067)

-Optional method of getting the .bin for your ECU- Use 'NefMoto ECU Flasher' to read your own .bin off of your ECU. Go to this forum, and the latest version of his flasher should be one of the first few sticky posts at the top:
http://nefariousmotorsports.com/forum/index.php?topic=2200.0title=

5. Click on the GUI shortcut on your desktop. Click the "Create ECU File" button, and select the .bin file from step 4.

6. Still in the GUI program, click the "Create Template File" button and navigate to the .bin file from step 4 again.

7. In Windows (not in the GUI) navigate to the "logs" folder inside of the ME7logger folder and locate the .cfg file that was created in step 6 (it'll be the same name as your .bin file from step 4). Open the .cfg file in notepad and erase the ";" in front of the variables you want to log (see end of this post for the common variables in the regular "Mark P" excel graph templates that you see posted here). You can also change the "SamplesPerSecond" up at the top of that file as well. I'd probably put it at 20 samples/sec and leave it alone if it isn't giving you any connection issues when logging.

8. You're now ready to log. With the car running and the cable plugged into the car's OBDII port and connected to the laptop, open the GUI again, highlight your .cfg file in the window, select the COM port that your cable is plugged into, and click the "Start ME7Logger button". You'll see !! and . as it's logging. Press ctrl-c to stop logging. The log file is now automatically saved in the "logs" folder inside of the ME7logger folder.

9. Any issues, consult the README file in the doc folder (which is inside the ME7logger folder, open it with wordpad), consult the ME7Logger thread in step 2, and finally consult the GUI thread in step 3. After exhausting the previous resources, post a new thread in the logging section on Nefmoto if need be.


------

Heads up that I wrote this guide for the B5 S4, but the variables for the RS6 should be pretty much the same, just there's two MAF's and the cylinder numbers keep going up to 8 of course:)

Common variables to log that you see in excel graphs (so to log these, just delete the semi-colon in front of them inside of your .cfg file):

nmot_w ;{EngineSpeed} ; {Motordrehzahl}
pus_w ;{BaroPressure} ; {Umgebungsdruck ohne Umschaltung auf Ersatzwert bei Sensorfehler}
plsol_w ;{BoostPressureDesired} ; {Soll-Ladedruck}
pvdkds_w ;{BoostPressureActual} ; {Druck vor Drosselklappe von Drucksensor (word)}
ldtvm ;{WastegateDutyCycle} ; {LDR Tastverhältnis , moduliert (Endergebnis)}
mshfm_w ;{MassAirFlow} ; {Massenstrom HFM 16-Bit Größe}
tans ;{IntakeAirTemperature} ; {Ansaugluft - Temperatur}
wped_w ;{AccelPedalPosition} ; {normierter Fahrpedalwinkel}
wdkba ;{ThrottlePlateAngle} ; {Drosselklappenwinkel bezogen auf unteren Anschlag}

dwkrz_0 ;{IgnitionRetardCyl1}
dwkrz_3 ;{IgnitionRetardCyl2}
dwkrz_2 ;{IgnitionRetardCyl3}
dwkrz_5 ;{IgnitionRetardCyl4}
dwkrz_1 ;{IgnitionRetardCyl5}
dwkrz_4 ;{IgnitionRetardCyl6}
zwout ;{IgnitionTimingAngleOverall} ; {Zündwinkel-Ausgabe}

rkrn_w_0 ;{KnockVoltageCyl1}
rkrn_w_3 ;{KnockVoltageCyl2}
rkrn_w_2 ;{KnockVoltageCyl3}
rkrn_w_5 ;{KnockVoltageCyl4}
rkrn_w_1 ;{KnockVoltageCyl5}
rkrn_w_4 ;{KnockVoltageCyl6}

vfil_w ;{VehicleSpeed} ; {gefilterte Geschwindigkeit (16-Bit)}
gangi ;{SelectedGear} ; {Ist-Gang vom CAN bei AT oder aus n/v bei HS}

lamsbg_w ;{AirFuelRatioDesired} ; {Lambdasoll Begrenzung (word)}
fr_w ;{LambdaControl}
ti_b1 ;{FuelInjectorOnTime} ; {Einspritzzeit für EV's auf Bank1}
tats_w ;{EGTSensor}
tats2_w ;{EGTSensorBank2}
tabgm ;{EGTModelBeforeCat}
tabgm2 ;{EGTModelBeforeCatBank2}

usvk ;{O2SVoltageSensor1}
usvk2 ;{O2SVoltageSensor1Bank2}

rl_w ;{EngineLoad} ; {relative Luftfüllung}
rlmx_w ;{EngineLoadSpecified}
rlmax_w ;{EngineLoadCorrected}
rlsol_w ;{EngineLoadRequested}


-------


Long Term Fuel Trim Partial (note, the fra's are in a scalar form (so you need to subtract 1 and multiply by 100 if you want a percent, for example an fra_w value of 1.02050 is 2.050%)):

fra2_w ;{AdaptationPartialBank2} ; {multiplikative Gemischkorrektur der Gemischadaption (Word) Bank 2}
fra_w ;{AdaptationPartial} ; {multiplikative Gemischkorrektur der Gemischadaption (Word)}


Long Term Fuel Trim Idle ('per time', which just means that these variables aren't necessarily the real final 'idle fuel trim' percentage that the ECU is multiplying the final fueling by, rather these just give you an idea of which side the idle fuel trims are on (+ means that the ECU is adding fuel because it's too lean, - means the ECU is pulling fuel because it's too rich), so these just you just show you which direction to adjust the fueling, not necessarily the magnitude to adjust it. The real variables for the final value of the idle LTFT's (rka_w/rka2_w) aren't defined automatically in the .ecu file created by the ME7Logger program. Also note that these values are in percentages, so a value of 1.0500 is 1.0500%):

rkat2_w ;{AdaptationIdleBank2} ; {additive Gemischkorrektur (pro Zeit) der Gemischadaption Bank 2 (Word)}
rkat_w ;{AdaptationIdle} ; {additive Gemischkorrektur (pro Zeit) der Gemischdaption (Word)}


Short Term Fuel Trims:

frm2_w ;{LambdaControlAvgBank2} ; {schneller Mittelwert des Lambdaregelfaktors (Word) Bank 2}
frm_w ;{LambdaControlAvg} ; {schneller Mittelwert des Lambdaregelfaktors (Word)}

[jibberjive]

HOW TO VIEW THE LOGS:

1. Go here to download Nyet's ECUxPlot (which also works with ME7Logger). Right click and install as administrator.:
http://nefariousmotorsports.com/forum/index.php?topic=1714.0title=/

2. Take an hour to play around with ECUxPlot to see what it consists of. Read the FAQ here http://nefariousmotorsports.com/forum/index.php?topic=1714.msg16497#msg16497 . There's no help file, but it really is pretty self explanatory if you spend a second looking at all of the options. It has a filter that you can turn on-off, that filters out 3rd gear FATS pulls so that you can get graphs containing the data that you're used to seeing on the forums. You really don't need to play with any of the options if you don't want to.

3. You'll want to add your own graphs and save them as presets so that you can easily load them in the future (see logs below for the graphs that I've added to get the same MarkP info, you might want to add a couple of more, or different ones). After you have all of your common graph presets saved that you want, from then on when you open a log file, you can go to "load all presets" under the options bar, and it'll automatically pop up all of your graphs. If you want to save them as picture files to post online or review later, with all of the graphs open go to "export all charts" under the file bar.

4. Tweak your tune and go faster[:D]


----ECUxPlot tips & tricks: When you load it, it will load the graph to the size that it was when you last closed it. In addition, the graph size that it first loads is the size that the 'load all presets' command makes all of the other graphs. So if you want all of your graphs a certain size, open ECUxPlot, resize the graph to the size you want, close it, re-open ECUxPlot and load your file. Also, leave the "show FATS window" unchecked until after you've done the "load all presets," or else you'll have a FATS window for every graph. When you save the graphs, the legend is smaller in the saved image than it is on the graph on your screen. Pay careful attention to the axes, as they are filled automatically (so, for example, a 2 degree difference could be shaped like a 20 degree difference IAT curve).

------

Graph preset examples (nevermind the actual values in the logs, REALLY, don't compare your logs to these as any type of standard, these are just some random logs to illustrate the ECUxPlot graph presets that you might want to make):

http://i297.photobucket.com/albums/mm235/jibberjive/Logs/GT144_4FATS_2_VE_20120403_074214-Fueling.png
http://i297.photobucket.com/albums/mm235/jibberjive/Logs/GT144_4FATS_2_VE_20120403_074214-FuelInjector.png
http://i297.photobucket.com/albums/mm235/jibberjive/Logs/GT144_4FATS_2_VE_20120403_074214-LoadMAF.png
http://i297.photobucket.com/albums/mm235/jibberjive/Logs/GT144_4FATS_2_VE_20120403_074214-EGTIATKnock.png
http://i297.photobucket.com/albums/mm235/jibberjive/Logs/GT144_4FATS_2_VE_20120403_074214-Timing.png
http://i297.photobucket.com/albums/mm235/jibberjive/Logs/GT144_4FATS_2_VE_20120403_074214-O2Sensor.png
http://i297.photobucket.com/albums/mm235/jibberjive/Logs/GT144_4FATS_2_VE_20120403_074214-IntakeAirTempThrottleBodyAngle.png
http://i297.photobucket.com/albums/mm235/jibberjive/Logs/GT144_4FATS_2_VE_20120403_074214-BoostPID.png
http://i297.photobucket.com/albums/mm235/jibberjive/Logs/GT144_4FATS_2_VE_20120403_074214-Power.png
http://i297.photobucket.com/albums/mm235/jibberjive/Logs/GT144_4FATS_2_VE_20120403_074214-Acceleration.png
http://i297.photobucket.com/albums/mm235/jibberjive/Logs/GT144_4FATS_2_VE_20120403_074214-FATS.png

[Kgnast]

Cool man, thanks alot for putting this information up for everyone.

[QuattroRS]

Or you could just buy the the VagCom and hook it up to your laptop. Then use all the other cool features of the VagCom.

[lswing]

Oh god....overload.....Ross-Tech, and I think they make the pretty graphs too....can you really judge HP accurately with a computer anyhow?

[jibberjive]

can you really judge HP accurately with a computer anyhow?
No. Well, yes, but all of the specific variables of the car have to be right for it to be usably accurate, so I'd say the "HP estimate" for the ME7Logger is more of a novelty than anything. Though that's definitely not where the power of the ME7L lies.


Or you could just buy the the VagCom and hook it up to your laptop. Then use all the other cool features of the VagCom.

I fully support and love Ross-Tech and VAG-COM, but this ME7Logger is a whole different beast. I use ME7Logger in parallel with vag-com, as I'll use vag-com to check/clear codes, change settings and log blocks where transient stuff doesn't really matter (like long term fuel trims and idle O2 voltage), and I use ME7L for when I want to do any real logging. I don't know how the performance of the vag-com on the ME7.1.1 ECU of the RS6 is, but on B5 S4's, the logging resolution of vag-com is terrible, and you could only log a handful of variables at a time. APR came out with the logging utility ECUx in early-mid 2000's, and that was a godsend for people because they could get some real resolution in their logs, and they can log more than 5 or 6 variables at a time. Then the developer that came up with ECUx parted ways with APR a while back, so for the past like 5 or so years ECUx has been in a weird limbo state where APR doesn't 'support' it and doesn't try to sell it (they wouldn't sell it to me when I called them on the phone to try to buy it a few years back). But you can still buy ECUx at certain places, like ECS. Kinda weird.

Anywho, since then, a user on Nefmoto.com named Setzi came up with his own logging utility (ME7Logger), and released it as freeware. Though not the most user-friendly utility, ME7L is very powerful and is key to telling the health of a car/tune, or is key to making cars go faster if you're custom tuning. It can log like 30+ variables at a rate of 20+ hz, and can log just about any variable you could ever want. One doesn't need to know the in's and out's of Motronic ME7 to use it though. And that's precisely why I put together this writeup, so that people who may not knowledge/desire to get deep into the ECU can still get this setup and installed with their variables and graphs pre-set, so they can log and graph with just a couple of buttons.

I know it's not for everyone though, just thought I'd throw this up here for those who might be interested.

[Elevens]

I really appreciate you attempting to spread the knowledge. I have minimal knowledge on engine tuning and I am sure this will really help. Thanks.

[DHall1]

The performance of the Vag on the RS6 is respectable in turbo mode. That said, you are correct as it will only log 3 items at a time. This info seems really cool but for the most part the owners here have simple Stage 1 or 2 RS6s. I will save this link and thanks for putting together such a complete guide to the parts and pieces.

[jibberjive]

Even those that are on stock turbos, I'd highly suggest logging your cars with ME7L. Just my opinion.

[alrightroad]

Great write-up. Thanks for sharing.

[v8a6]

Great write-up. Thanks for sharing.

Agreed. This is really going to help me out. Thanks for taking the time to do the great writeup!

[RS8]

Hi
I'm going to try this but I'm using my Vag-Com cable and the flasher says that it is suppoerted..


But I don't understand about the BIN number:
4. Go to one of the following links to download your ECU's .bin file. Place the .bin file in the ME7logger folder.
Can I find this number inside my ECU or can I read it in Vag-Com ?

Or how do I find it with the 'NefMoto ECU Flasher' ?
If I read the ECU info I can see for exampel ECU Software Number "037358187" and a hardware number
But I can't find any of these numbers ?
4. Go to one of the following links to download your ECU's .bin file. Place the .bin file in the ME7logger folder.
--Audi RS6 4.2TT BCY 0261207857 4D1907558 366304 (http://nefariousmotorsports.com/forum/index.php?action=dlattach;topic=49.0;attach=64)
--Audi RS6 4.2TT BCY 450HP 4D1907558 0261207857 367724 (http://nefariousmotorsports.com/forum/index.php?action=dlattach;topic=1476.0;attach=2048 )
--RS6 4D1907558 0004 0261207857 367724 (http://nefariousmotorsports.com/forum/index.php?action=dlattach;topic=47.0;attach=62) (not sure if this is the same as the first one or not)
--Audi RS6 4.2TT BCY 450HP 4D1907558B 0261208051 1037368087 (http://nefariousmotorsports.com/forum/index.php?topic=2645.msg25066#msg25066)
--Audi RS6 Plus 4.2TT BRV 480HP 4D1907558F 0261208728 1037370934 (http://nefariousmotorsports.com/forum/index.php?topic=2646.msg25067#msg25067)

[KWest]

Great write up.

I've been using ME7logger for some time now, the data rate and amount of ECU variables available make it far superior than VAG. If you only want the basics the stock PID's that VAG will display are fine. If you are doing your own tuning and trying to follow the ME7.1 function sheets to understand how the ECU work ME7logger is a must.

jibber,
You should note that some tuners have safeguards to prevent map reading, some of which can be nasty. If you have a tuned ECU you should really try get a stock .bin file for your ECU before you try read it out.


Here is a example .cfg .ecu file for the 558E (Canadian ECU).
https://dl.dropboxusercontent.com/u/1097543/ME7logger_558E.zip

[RS8]

I don't understand?
I can use Ross-Tech Vag-Com to read fault codes and logg data..

So all I want is to use ME7logger so I can logg all sensors, do you say now that I can't do that because I have a custom made chip in my ECU ?


What can happen if I just try one of this .bin file. ?

4. Go to one of the following links to download your ECU's .bin file. Place the .bin file in the ME7logger folder.
--Audi RS6 4.2TT BCY 0261207857 4D1907558 366304 (http://nefariousmotorsports.com/forum/index.php?action=dlattach;topic=49.0;attach=64)
--Audi RS6 4.2TT BCY 450HP 4D1907558 0261207857 367724 (http://nefariousmotorsports.com/forum/index.php?action=dlattach;topic=1476.0;attach=2048 )
--RS6 4D1907558 0004 0261207857 367724 (http://nefariousmotorsports.com/forum/index.php?action=dlattach;topic=47.0;attach=62) (not sure if this is the same as the first one or not)
--Audi RS6 4.2TT BCY 450HP 4D1907558B 0261208051 1037368087 (http://nefariousmotorsports.com/forum/index.php?topic=2645.msg25066#msg25066)
--Audi RS6 Plus 4.2TT BRV 480HP 4D1907558F 0261208728 1037370934 (http://nefariousmotorsports.com/forum/index.php?topic=2646.msg25067#msg25067)

[KWest]

I don't understand?
I can use Ross-Tech Vag-Com to read fault codes and logg data..

So all I want is to use ME7logger so I can logg all sensors, do you say now that I can't do that because I have a custom made chip in my ECU ?


What can happen if I just try one of this .bin file. ?

4. Go to one of the following links to download your ECU's .bin file. Place the .bin file in the ME7logger folder.
--Audi RS6 4.2TT BCY 0261207857 4D1907558 366304 (http://nefariousmotorsports.com/forum/index.php?action=dlattach;topic=49.0;attach=64)
--Audi RS6 4.2TT BCY 450HP 4D1907558 0261207857 367724 (http://nefariousmotorsports.com/forum/index.php?action=dlattach;topic=1476.0;attach=2048 )
--RS6 4D1907558 0004 0261207857 367724 (http://nefariousmotorsports.com/forum/index.php?action=dlattach;topic=47.0;attach=62) (not sure if this is the same as the first one or not)
--Audi RS6 4.2TT BCY 450HP 4D1907558B 0261208051 1037368087 (http://nefariousmotorsports.com/forum/index.php?topic=2645.msg25066#msg25066)
--Audi RS6 Plus 4.2TT BRV 480HP 4D1907558F 0261208728 1037370934 (http://nefariousmotorsports.com/forum/index.php?topic=2646.msg25067#msg25067)



You should read what model and software your current ECU is with VAG-Com. The model should be 558(x), then you can find a stock .bin that matches.

From my knowledge
558B is Euro
558D is US
558E is Canadian
558F is Euro RS6Plus

As long as you're using the correct ECU model then the software version shouldn't matter.

ME7logger connects to all the ECU with the same protocol, and then reads the memory locations defined in the .ecu file. If you load the wrong .ecu file it will simply read the wrong data which won't hurt anything.

[RS8]

You should read what model and software your current ECU is with VAG-Com. The model should be 558(x), then you can find a stock .bin that matches.

From my knowledge
558B is Euro
558D is US
558E is Canadian
558F is Euro RS6Plus

As long as you're using the correct ECU model then the software version shouldn't matter.

ME7logger connects to all the ECU with the same protocol, and then reads the memory locations defined in the .ecu file. If you load the wrong .ecu file it will simply read the wrong data which won't hurt anything.

Thanks.
But I don't find 558 anywhere ?
I have cheked boat with vag-com and Nef moto ecu flasher but I only see other numbers?
And on my ecu label there is no letter after 558 ?

[KWest]

Thanks.
But I don't find 558 anywhere ?
I have cheked boat with vag-com and Nef moto ecu flasher but I only see other numbers?
And on my ecu label there is no letter after 558 ?


That would match the first and third download then.

Audi RS6 4.2TT BCY 0261207857 4D1907558 366304 (http://nefariousmotorsports.com/forum/index.php?action=dlattach;topic=49.0;attach=64)

[RS8]

Thanks.
But the second download don't have a letter either? Whats special with that one?

[RS8]

Problems!
The first download contains a .org file and not a .bin?
But second and third .bin seems to work it starts to logg but then I get "Can't open serial port Com2", because I have a USB cable..
And if I choose Use FTDI on Comm Options then I get this fault code:
can't load library ftd2xx.dll

So now i have tried a couple of "Virtual Com port" software but I don't find any software that you can choose USB to Com port in?
I'm trying on Google with "freeware virtual usb to com port windows xp" but can't find the right one?
Anyone knows a usb-com software that will work?


I have tried to install this driver again but this one you can't do anything in? (you can't choose com port or anything?)
1. Download the driver for that cable from the first post here (it's FTDI D2XX), and install it:
http://nefariousmotorsports.com/foru...c=2200.0title= (http://nefariousmotorsports.com/forum/index.php?topic=2200.0title=)

And my Ross-Tech usb cable works fine (it says "Premium feature licensing supported") in Nefmoto Flasher !

Or is it FTDI I have to choose in Me7logger for USB then what does this mean?
can't load library ftd2xx.dll

[RS8]

I have now been using ParetLogic Health Advisor to FIX my computer and also tried to install everything again..
But when I use FTDI on Comm Options then I get this fault code every time i tries:
"can't load library ftd2xx.dll"


Is it FTDI i shall use for USB cable?
And does anyone know how to solve this ftd2xx.dll problem?

(I have 5 different ftd2xx.dll on my computer when I scan it.)

[RS8]

I have tried another computer now but same problem?

Logged data size is 10 bytes.
Really logged are 6 entries with 10 bytes.
can't load library ftd2xx.dll
Initialization failed, exiting ...
exiting (cause=0x1)...

This file ftd2xx.dll is in the cable driver "CDM" file and I tried to copy this and put in in ME7logger folder, but it dosen't help?

This is the versions i'm using now:
CDM v2.08.30 WHQL Certified
ME7logger v1.20
ME7Logger_GUI v1.6

[lswing]

RS8, was there a reason you're not just using the standard RT software that logs almost all the info needed easily? Just checking, good luck as it looks interesting!

[RS8]

RS8, was there a reason you're not just using the standard RT software that logs almost all the info needed easily? Just checking, good luck as it looks interesting!

Because with Ross-Tech you can only log 3 groups at the same time..

And I want to log a lot of things like all of this things:

nmot_w ;{EngineSpeed} ; {Motordrehzahl}
plsol_w ;{BoostPressureDesired} ; {Soll-Ladedruck}
pvdkds_w ;{BoostPressureActual} ; {Druck vor Drosselklappe von Drucksensor (word)}
mshfm_w ;{MassAirFlow} ; {Massenstrom HFM 16-Bit Größe}
tans ;{IntakeAirTemperature} ; {Ansaugluft - Temperatur}
wdkba ;{ThrottlePlateAngle} ; {Drosselklappenwinkel bezogen auf unteren Anschlag}

dwkrz_0 ;{IgnitionRetardCyl1}
dwkrz_3 ;{IgnitionRetardCyl2}
dwkrz_2 ;{IgnitionRetardCyl3}
dwkrz_5 ;{IgnitionRetardCyl4}
dwkrz_1 ;{IgnitionRetardCyl5}
dwkrz_4 ;{IgnitionRetardCyl6}
zwout ;{IgnitionTimingAngleOverall} ; {Zündwinkel-Ausgabe}

rkrn_w_0 ;{KnockVoltageCyl1}
rkrn_w_3 ;{KnockVoltageCyl2}
rkrn_w_2 ;{KnockVoltageCyl3}
rkrn_w_5 ;{KnockVoltageCyl4}
rkrn_w_1 ;{KnockVoltageCyl5}
rkrn_w_4 ;{KnockVoltageCyl6}

lamsbg_w ;{AirFuelRatioDesired} ; {Lambdasoll Begrenzung (word)}
fr_w ;{LambdaControl}
ti_b1 ;{FuelInjectorOnTime} ; {Einspritzzeit für EV's auf Bank1}
tats_w ;{EGTSensor}
tats2_w ;{EGTSensorBank2}
tabgm ;{EGTModelBeforeCat}
tabgm2 ;{EGTModelBeforeCatBank2}

usvk ;{O2SVoltageSensor1}
usvk2 ;{O2SVoltageSensor1Bank2}

rl_w ;{EngineLoad} ; {relative Luftfüllung}
rlmx_w ;{EngineLoadSpecified}
rlmax_w ;{EngineLoadCorrected}
rlsol_w ;{EngineLoadRequested}

[lswing]

Just a thought, even though you can only log three at a time, sometimes each one has a few useful parameters. If I need more I'll just switch settings and do another log, but I see your point in wanting to log anything you want.

[jibberjive]

I'm looking to edit the original post to add/fix some stuff, but the edit button is gone from that post. Does editing privileges on a post expire after a certain amount of time? Who might I PM to get permission to edit that post again?


jibber,
You should note that some tuners have safeguards to prevent map reading, some of which can be nasty. If you have a tuned ECU you should really try get a stock .bin file for your ECU before you try read it out.
I know some tuners have safeguards against reading their files (ie. disable read over OBD, some have used encryption boards, etc), and some protect their data/values by doing things like scrambling maps in the files etc., but can you give an example of what you are considering 'nasty' safeguards?

[jibberjive]

Thanks.
But the second download don't have a letter either? Whats special with that one?
RS8, it sounds like you're giving it a good effort. Hopefully I can help you.

Issue #1- Getting the correct .bin file (the .bin file is the 'flash' from the ECU that contains all of the tuning parameters/maps/values.

I think it is best for someone to read the file off of their own ECU rather than downloading, as then they will be sure that there will be no issues or no questions about whether or not they have the correct .bin file for their car. If the logging files are set up with a .bin that is different from what is on the ECU, it will not allow logging; generally there is not cross-compatibility. With tuned ECU's, reading your own .bin from the ECU is definitely the best practice, as the file that is currently on the inside of the ECU may not be the same "box" (part number) of file that originally came on the car (for example, even though you are in Sweden, your tuner may have based his tuned file off of a US car or an RS6+ car). Also sometimes tuners choose to modify the part number in the flash with other values, like the tuner's name or something. If these part/hardware numbers in your ECU are different than the part/hardware numbers for the .bin that you use to create the logging files, you cannot log.


Solution - Download the .bin file from your own ECU and use that to create the other files. To do so, use the free Nefmoto flasher/reader software to read your own .bin. Check here to download the program (I have found personally that NefMoto version 1.9.1.2 is more reliable for me, but I'd try the newest version first if I were you): http://nefariousmotorsports.com/forum/index.php?topic=2200.0title=
Here's a link to some usage instructions. If you set up your Ross-Tech cable as below in solution #2, you should be able to use it for the NefMoto flashing software as well. Once you have your own .bin, go through the steps listed in the first post.



but then I get "Can't open serial port Com2", because I have a USB cable..

Issue #2 - com port and drivers for VCDS cable use with ME7Logger

Solution - You need to install the VCP drivers from Ross-Tech, and you need to go into 'options' in the VCDS software and uncheck 'boot in intelligent mode'. See more detailed here http://nefariousmotorsports.com/forum/index.php?topic=3138.0title=
After that, you should be able to use the VCDS cable with ME7Logger and Nefmoto flashing software. To see which com port you need to specify, plug the cable into a USB ports, on your computer go to Control Panel > Device Manager and look under 'Ports (COM & LPT)' to see which Com port shows up. In the Me7Logger gui, specify that port.

After you do the above, you should be good to go. Good luck!

[RS8]

I finally got the cable to work with Ross-Tech "Virtual COM Port" http://www.ross-tech.com/vag-com/usb/virtual-com-port.html
But I don't have to specify my comport it works now if I choose FTDI in ME7logger!? but unfortunately I have another .bin file so that is my new problem now.

But I don't understand how to read my own .bin file?
I have Nefmoto flasher but where in the program can I read and save my .bin file?

[RS8]

The only thing I find that I can do in NefMoto Flasher is to read ECU info?
So now I have done this, in Nefmoto flasher I "read ECU info" and then "Save ECU info" and named it to AudiRS.bin
And then copied that file into my Me7Logger

But then in ME7logger it says that my:
.bin file has not correct lenght (is 0x382 bytes long, 0x80000 or 0x100000 bytes expected)
When I use this AudiRS.bin to "create ECU file" and "Create Template file" So I don't get an Config file to use.


So I guess this is the wrong way to make a .bin file...

So how do I do it??

I have found this on Nefmoto:

1. Open Nefmoto
2. Click KWP 2000 Flashing Tab
3. Click Connect Slow/Fast Init.
4. Click "Choose Memory Layout"
5. Open the Memory Layouts Folder
6. Select ME7 "29F800BB.MemoryLayout.xml" this is the correct one for your ecu.
7. Select Read if you want to read out your ecu

But that MemoryLayout.xml is for an jetta 1.8T So if this is the right way to read my ECU what MemoryLayout.xml file is it for RS6 ?
http://nefariousmotorsports.com/forum/index.php?topic=4118.0
What should I do after to make my .bin file?

[jibberjive]

The only thing I find that I can do in NefMoto Flasher is to read ECU info?
So now I have done this, in Nefmoto flasher I "read ECU info" and then "Save ECU info" and named it to AudiRS.bin

The 'ECU info' is not the .bin file; the ECU info is literally what it sounds like, the information about that ECU (hardware # etc.). Since you're able to get that far though, you have been successful with connecting to your ECU through the Nefmoto software. This is good. After you are connected, click the tab 'KWP2000 Flashing', click 'Choose Memory Layout', select either 'AM29F800' or 'AM29F800BB' (I don't remember which is correct for the RS6, but there is no risk if you select the wrong memory layout). Click 'Full Read Flash' and save the .bin file when it is done. It should automatically disconnect when it's done reading and saving, but just make sure the dialog says 'disconnected' before unplugging the cable.

Use this .bin to set up your logging.

Edit:
I just re-read your post, and you already list exactly what I said. Just do that.

[RS8]

I have tried all seven Memory layouts but when I do a Full Read flash I only get "Memory layout validation failed" on all of them?


I have one ecu with stock old ecu file loaded in to it and ECU hardware number 0261207857 4D1907558
and another ECU with special MTM tuned chip in it, but I can't read Memory layouts on any of them?

[jibberjive]

I confirmed that the correct memory layout is AM29F800BB, but there might be two issues.

-NefMoto software is known to not be able to read the RS6's very well. It might be because of this.

-Your ECU is tuned, so the tuner may have employed some read protection tactics.

If you can't read via NefMoto, your best bet is to try either MPPS or Galletto cable/software to read your ECU via bootmode. If you decide to pursue that, do some research on nefariousmotorsports.com and ask your questions there, as that is beyond the scope of this logging walkthrough here.

Would you mind posting your ECU info file that you pulled? I might be able to help you choose one of the already downloaded .bins.

[RS8]

Here is the ECU info from one box.
0x92 Hardware: 0261207857
0x94 Software: 1037366304
0x91 Vehicle: 0x0D, Hardware NO*, 0xFF
0x9B Calibration: 4D1907558 , 0002, 0x03001678, 0x00000450, 0x54D3, 4.2l V8/5VT ,*
0x9C calibration: 0x87060000

Is it all this you need?

I have asked my tuner and he havent put in anything but he says maybe there was a read protection already on it?
But he have other stock files he can give me to test with.

[jibberjive]

I have asked my tuner and he havent put in anything but he says maybe there was a read protection already on it?
But he have other stock files he can give me to test with.If you havea personal relationship with your tuner, just have him send you the .bin. No need to download anything.

[RS8]

My Tuner made me a new chip and sent me a .bin file for that one so finally it works for me.

But when i'm logging lambda on this two:
fr_w ;{LambdaControl}
fr2_w ;{LambdaControl}

I can se my lambda value on both in excel but I can't se them in ECUxPlot ?


And on all of this I only get number 1 or 0 on them in excel and also nothing in ECUxPlot.
​lambts_wlamfa_w
lamfaw_w
lamfawkr_w
lamsbg2_w
lamsbg_w
B_lambts
B_lr2
B_lrhk



Can you see your lambda in ECUxPlot ?

[jibberjive]

Which lambda are you looking for? I assume you want to know the final lambda that the car is requesting (as the RS6's are based only on narrowband O2 sensors, and thus can't tell you the actual AFR outside of a couple of points in either direction of 14.7)?

The RS6's fueling strategy is to run the air-fuel ratio as close to stoichiometric (14.7 AFR or lambda 1) as possible most of the time, and it only enriches under load and when necessary (when it goes into open loop control). When you were logging all of those variables, was it under the type of situations where the car would logically be requesting lambda 1 (ie. idle or light load). Cause if so, that's why you would see all of those values equalling 1, as that would be the requested lambda. And the 'B_xxx" variables are flags, not lambda values. Either way though, now that you've got the thing up and running, these technical questions are better fielded on the nefmoto forums themselves, as the scope of this thread is to help people get the hardware and software connected, not to analyze the data.

Regarding ECUxPlot, play with the filter if you can't see any of the values. Read the 2nd link in the 2nd post of this thread (the ECUxPlot FAQ).

[RS8]

It is the narrow band lambda value I want to se, and I guess that it is fr2_w and fr_w that only show this?
(I have problems now that my car runs lean when it is cold outside so my lambda value is over 1.1 but only fr2_w and fr_w shows what it is..)
Is it any idea to log the other values that only show 1 or 0 ?



<tbody>
fr2_w
fr_w
fzabgs_w
ksta0
ksta1
ksta2
lambts_w
lamfa_w
lamfaw_w
lamfawkr_w
lamsbg2_w
lamsbg_w
mshfm_w
nmot_w
plsol_w
pvdkds_w
rl_w
rlmx_w
rmslt
rmslt2



-
-
#
-
-
-
-
-
-
-
-
-
g/s
rpm
mbar
mbar


-
-



LambdaControlBank2
LambdaControl
CountMisfireTotal
ColdStartEnrichmentRange0
ColdStartEnrichmentRange1
ColdStartEnrichmentRange2
LambdaPartProtection
TargetAFRDriverRequest
AirFuelRatioDesiredBank2
AirFuelRatioDesired
MassAirFlow
EngineSpeed
BoostPressureDesired
BoostPressureActual
EngineLoad
EngineLoadSpecified
SecondaryAirMass
SecondaryAirMassBank2


1,10962
1,14472
0
1
1
1
1
1
1
1
1
1
4,88889
700
1024,57
1034,92
15,2344
126,305
1
1



1,11176
1,14777
0
1
1
1
1
1
1
1
1
1
5,41667
695,5
1024,53
1034,92
15,5859
126,305
1
1



1,11404
1,15082
0
1
1
1
1
1
1
1
1
1
5,33334
698,25
1024,57
1034,77
16,2422
126,305
1
1



1,11649
1,15387
0
1
1
1
1
1
1
1
1
1
5
704
1024,57
1033,95
16,0781
126,305
1
1



1,11893
1,15692
0
1
1
1
1
1
1
1
1
1
4,66667
721,25
1024,57
1033,32
15,6094
126,305
1
1



1,12137
1,16028
0
1
1
1
1
1
1
1
1
1
4,66667
729
1024,57
1034,88
15,2109
126,305
1
1



1,12381
1,16364
0
1
1
1
1
1
1
1
1
1
4,58334
714,75
1024,57
1034,96
14,8828
126,305
1
1



.
.
.
.
.






















tats2_w
tats_w
ti_b1
ti_b2
timxth_w
tmot
tmst
ub
ushk
ushk2
usvk
usvk2
wdkba
zwout
B_lambts
B_lr2
B_lrhk
tans





°C
°C
ms
ms
ms
°C
°C
V
V
V
V
V
DK
°KW



°C





EGTSensorBank2
EGTSensor
FuelInjectorOnTime
FuelInjectorOnTimeBank2
TheorMaxInjectionTime
CoolantTemperature
EngineStartTemperature
BatteryVoltage
O2SVoltageSensor2
O2SVoltageSensor2Bank2
O2SVoltageSensor1
O2SVoltageSensor1Bank2
ThrottlePlateAngle
IgnitionTimingAngleOverall
CondLambdaPartProtectionActive
IntakeAirTemperature



240,898
246,015
1,776
1,736
168,3
84,75
69
13,9392
0,457177
0,457177
0,128588
0,170314
1,17647
24,75
0
1
0
50,25





240,507
246,015
1,836
1,788
170,452
84,75
69
13,8688
0,451961
0,457177
0,123373
0,170314
1,17647
23,25
0
1
0
50,25





240,507
245,253
1,868
1,82
172,04
84,75
69
13,9392
0,457177
0,457177
0,123373
0,165098
1,17647
13,5
0
1
0
50,25





240,507
245,253
1,82
1,772
171,856
84,75
69
13,9392
0,451961
0,457177
0,118157
0,154667
1,17647
13,5
0
1
0
50,25





240,546
245,214
1,8
1,752
169,132
84,75
69
13,9392
0,451961
0,457177
0,112941
0,154667
1,17647
15,75
0
1
0
50,25





240,507
245,214
1,756
1,712
164,832
84,75
69
13,9392
0,457177
0,457177
0,112941
0,149451
1,17647
14,25
0
1
0
50,25





240,507
245,214
1,744
1,696
165,628
84,75
69
13,8688
0,457177
0,457177
0,112941
0,149451
1,17647
21,75
0
1
0
51




</tbody>

[jibberjive]

Excellent, you were able to connect and to log. The scope of this thread is intentionally being limited to getting the hardware and software talking to each other and getting the ability to log. Any technical questions regarding analyzing the logged values is beyond the scope of this thread, and this is the last reply I will give regarding your technical questions in this thread. If you have any additional technical questions now that you are able to log, please ask them on www.nefariousmotorsports.com (http://www.nefariousmotorsports.com) forums, rather than in this this thread, as you are now past the scope of this thread. I am attempting to keep this thread relatively free of the technical jargon, as people don't really need to know the logic behind all of the Motronic ECU just to log their car, and I don't want them to feel overwhelmed by technical jargon.


To address your questions, fr_w and fr2_w (bank 2) are not the lambda values from the oxygen sensors; they are short term fuel trims, and are essentially the same as the frm_w variables mentioned at the bottom of my first post in this thread. They will help you find out that you're running lean because the values are positive (ECU is adding fuel in), but they don't tell you what the what the actual lambda of the car is.

Regarding all of the 'lamXXX' values you logged, those relate to the requested lambda from the ECU, not the actual lambda that the O2 sensors are reading. Those values are all 1 in this log because (according to your RPM, MAF vaues, injection time, etc) you are doing this log at idle, and simply put, your car is requesting a lambda value of 1 at the time of the log. The particular variable that you want to log to see the real, final requested lambda from the ECU is lamsbg_w/lamsbg2_w. The value of these 'lamXXX' variables are not binary (0 or 1), rather they are lambda values that range from 0 to around 1. Like I mentioned above, the RS6 fueling scheme is to stay as close to unity (lambda = 1) as possible (for fuel economy and emissions reasons), and you won't see requested lambda values drop below 1 until your car is enriching when it has a greater load at WOT, or it is enriching for component protection.

To log the actual lambda, you want to look at the O2 voltages that you logged (usvk/usvk2). You then have to know how that voltage correlates to lambda (generally something like this, and pay attention that the X-axis for lambda values for narrowband sensors only span +/- .02):

http://wbo2.com.au/~techedge.com.au//vehicle/wbo2/info/nb-afr.gif




So with that, I respectfully request that, now that you are able to connect and log, if you have any additional technical questions regarding the logged values, that you head over to www.nefariousmotorsports.com (http://www.nefariousmotorsports.com) and use the search bar to research any questions you might have about the logged values. And that if, after searching on your own first, you still have technical questions about the logged values, you ask them over on the nefariousmotorsports.com forums or start a new thread here on RS6.com, not in this thread.:) Thanks!

[RS8]

Last questions.


What can you see when logging in 20 samples / second that you can not see in 10 samples/sec?
Is there any idea to run at 20 samples/sec?


And if you were to run only one pull in the dyno, what would you log then?



And is it anything i should mark under "options" in this?
14887

[jibberjive]

Bump. I'm going to update this post sometime, but I thought I would bump this because it seems everyone is still using Vag-Com to log these cars.