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

[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=

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/foru...c=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/foru...c=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...-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/foru...p?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 ?

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