Audi TT Forum banner

.xdf file

9K views 11 replies 4 participants last post by  StuartDB  
#1 ·
Hello,

Has anybody got the .xdf file for a bosch ME7.5 from a 225 Quattro BAM 2002?
 
#3 ·
Afraid I don't know yet went to use my ebay VAG-COM cable and it didn't work, wouldn't even install the drivers, tried on 2 PC's. Also the actual ECU has that extra fixing on the right hand side and I don't think there is a easy way to get it out.

I have ordered another VAG-COM cable.

Other than VCDS/VAG-COM or actually getting the ECU out do you know another way of getting the box code & revision?

Thanks

Ian
 
#7 ·
A_Banging_Donk said:
Well until you read out the flash, the xdf is useless so do that first.

https://s4wiki.com/wiki/Tuning#Flashing_utilities
I think Ian is trying to check over a selection of bin's he has obtained, assuming they are not encrypted?

But yes... of course, before touching anything in the ECU follow the safety procedures and learn the tools, back-up ECU, bench flashing rig etc etc, I am not sure how far these type of threads are allowed on TTForum, I know they are not really allowed on ASN - as it only takes a second to brick your ECU and that shouldn't be encouraged, but there is no harm in spending some time checking out different maps and comparing bin files as a starting point on your desktop.
 
#8 ·
Hello all,

Finally got some cables that work.

The output from VAG-COM;

Address 01: Engine
Protocol: KW1281
Controller: 8N0 906 018 H
Component: 1.8L R4/5VT 0004
Coding: 10710
Shop #: WSC 01236

I think it's the 8N0 906 018 H and the 0004 that's need to match the definition file.

I have also got the original map and a couple of ECU screen shots from VAG-COM and Nefmoto which you can view here - https://www.dropbox.com/sh/cbhbszmjppyr ... JrSoa?dl=0

Any help with a definition file would be most wecome.

Thanks

Ian
 
#9 ·
All,

I loaded the 8N0 906 018 BH.xdf in to TunerPro and it does say "Ď€ S3" at the bottom. I also compared the 8N0 906 018 BH stock.bin with the one from my car and there are differences (defined and undefined).

I have got the attached 8N0906018H AMK-BAM.xdf but it look far from factory.
 
#10 · (Edited by Moderator)
The xdf are just pointers with human descriptions. Show some screen shots of the differences, or upload the bin you read from your car maybe it's already been mapped.
What tool did you use to read the map from your car. The s3 you saw is just a label identifying the xdf is not a value from the actual bin.

There is no such thing as a factory xdf! VAG dont use tunerpro

arh I see you uploaded your bin file I will take a look.

key maps look the same to me?
What categories are you concerned about? Load and Boost PID are identical along with CAT, Fueling and Timing

compareIanBIN.png


compareIanBIN2.png


before considering writing anything to you ECU you must get something to ensure the check sum is correctly written otherwise you will temporarily brick the ECU (It will start once then that writes the check sum and then the car wont start again until the battery is disconnected for some time or you have to remove the ECU and bench flash in boot mode.
 

Attachments

#11 · (Edited by Moderator)
Thanks Stuart,

As you are ware I'm building this as a project-toy, I'm nearly there with the mechanical side and I'm looking to adjust the mapping to increase the performance predominatley for track days IE not necessarily max power. I want to get as far as I can myself before handing it over to a propper mapper if required and I don't think that a single trip to a mapper will fulfill my curiosity.

I have a lot of reading to do and videos to watch and I'm getting there.

I can now;

- Diagnose faults (been able to do this for a few years)
- Log the ECU readings (been able to do this for a few years)
- Download the cars running map
- Upload a map to the car

My next steps are to do some more reading and video watching and make some VERY SMALL adjustments to the map and see what happens, I was also thinking that I could see what he diiferences are between the 225 and 240 and may be use the 240 map as a referance.

So my next questions are;

- Is it wise to use the 8N0 906 018 BH.xdf as a basis for modifying my standard map or is there a better one out there?
- Have you any pointers on modifying the standard map?
- Do you know where I can get a map for a 240?

Also I design Communications Systems and Computer Networks as a day job so have no problem working with these types of systems, It's just another system to learn.

I realise that VAG have something a bit more substantial than TunerPro, the "Non-Factory" XDF I refered to (8N0906018H AMK-BAM.xdf) View attachment 8N0906018H AMK-BAM.zip has entries like Flames etc which I don't think VAG would normally use in production.

I have the ME7Check.exe so can do the checksum check and I think there is a TunerPro add-in to creat a new Checksum for modified files, so that's the next job to do.

Thanks for your help on this and any pointers are most appreciated.

Ian
 

Attachments

#12 ·
Yeah me7check will confirm the checksum and me7sum will generate the checksum. But the free for personal use tunerpro plug-in is excellent.
Not sure what xdf you have, the one I uploaded is pretty comprehensive and I have corrected a few items where the multiplier factoring was incorrect, and added several additional tables to allow configuration of the x and y axis of the actuator duty cycles as the default is limited to 1 bar boost.

A BFV ECU is configured differently so the BAM / AMK XDF is different but there are plenty of notes about the 240 map from a BFV on nefmoto it essentially ups the maximum charge pressure (a bit more load), but some bits of it are rubbish too. For example it ups the load during continuous knock to compensate knock intervention, when the correct thing to do is make sure you don't get intervention in the first place, and also it doesn't change the fuelling (hence needing to compensate for knock intervention)

Just be careful with these settings remembering you have a Franken 23 hybrid. I was advised to set a maximum actuator duty cycle to something like 30% whilst playing with various maps to map sure it didn't go crazy.