NefMoto

Very new to all of this an just trying to find a definition file so I can start at least browsing the bin files and get familiar. Any help is appreciated.  ;D

You should post exact ECU number - at least VAG one, but including version info because different software version could/would have different addresses.

Sooo

Step 1. Get my ECU vag part number.. got it lol.. Thanks

Please obey the rules of the definitions board when posting there. Thanks!

you can use damos files ( because they are a lot of them on the net ) to make your own .XDF (but it takes some time )
just open them with text editor :)

Will the "M box" aka manual S4 XDF work with the CH box BIN?

Where is the most updated 01 AWM XDF?

I have a few KP files.. I can read the XDF in Notepad, and CSV in Excel, but what about the KP files?

Trying to come up with the most complete definitions file.. Trying to understand if I can flash a BIN with a newer software code...

360101 vs 360854

BTW.. XDF, KP and Damos are all terms for definitions files?

Cant Edit:
http://nefariousmotorsports.com/forum/index.php?topic=17137.msg132290#msg132290

Used this persons XDF as a starting point, it is the newest by date..

Glad it helped someone lol

Cant open KP files in notepad, since they are propertiary files.

You can flash newer software version.

IMO there is no point using the 018CH version unless you need the no immo function, else just crossflash to a file that has damos available.

Yes those terms are definition files, however a2l/damos files are semi official, the rest are manually created.

Reiterating my understanding to confirm.

B5 S4 8D0907551M (M-box) ECU XDF and Bins seem public, but I havent seen many CH box Bin/XDF combos.

I bought a 15$ Vag Cord. Should I buy a spare ECU from the junkyard, plug it into my car and practice with that so I dont screw up the original?

Original file = ".BIN" (ECU Data)
MapPack = ".KP" (Maps)
Damos = ".A2L" (Map & Axis Data)
WinOLS complete file = ".OLS" (Map & Axix Data & ECU Data)

I read that Damos require the Glass beads and secret handshake, as they are usually complete.

Do price and handshake complexity increase with more valuable mfgs? How much for a Gallardo Damos? I have a Huracan I might like to tune.  ;D

http://files.s4wiki.com/defs/

OK, Update.

Learned how to edit my posts, and learned people use Several XDFs over the same BIN. to find all the definitions... Kind of baffled there most common models arent well documented. Cant find CH Bin/XDF combos for the 01 AWM 1.8Ts.

There are bunch of a2l/damos files out there on the internet , pretty much for most of the cars but not all combinations or software versions, so IF you can you should always crossflash , specially on ME7 that has been around for 20 years.
If you got some exquisite car or something along those lines and you know there is a damos for it then ofcourse you can get into the secret stuff or just buy one.


The "box" nomenclature is mostly for the S4 ecus however CH box for the 1.8T is fine too, yes you can flash the 360854 on 360101 or vice versa. 018CH is the VAG part number of this box, 4B0906018CH.

This ECU and the 2 software versions came from the NA market , they do not have IMMO function in the code, which means if you cant be bothered to immo off the eeprom flashing this file will run the car, ofcourse the downside is that there is no damos out there in the wind. However like I said you are much better off immo offing the eeprom and flashing a file(1.8T ofcourse) that has a full definition available.

You can find original files here on the forum, in the ECU original files section, both of the 018CH software versions are out there, HOWEVER you cannot flash an S4 binary on your 1.8T ecu that should be obvious.

Here is a Stock . BIN file from Tony for these cars..
http://nefariousmotorsports.com/forum/index.php?topic=219.0

I am hearing about people bricking their ECUs trying to read cars that were previously flashed? Some encryption/ address shifting trick to keep people from reading a "commercial" tune? Not entirely familiar with this process.. Why does reading a previously "tuned" ecu cause a bricked situation?

I picked up this Car/ECU from a previous owner and suspect it has been messed with. What route should I go with to avoid possibly bricking it?

Should I flash it with the stock BIN from the beginning? Or should I read the flash and possibly brick it in the process?  Is this "bricked" situation something the Galletto 1260 + Boot mode is supposed to fix? Trying to avoid this situation.

The current "Tune" that came with the car, while removing some emission components, has significantly retarded timing. Led me down this rabbit hole. Been having dreams about this stuff I read about it so much.

http://nefariousmotorsports.com/forum/index.php?topic=12043.0title=
Another Bin and XDF

There was all kinds of nonsense used back in the ME7 days. Some tuners used fancy riser boards with programmable logic on them which would scramble the addresses on the flash chip, so that when they were accessed directly as maps, the data would be correct, but when they were accessed sequentially to read, you'd get garbage. These wouldn't usually cause a brick on read though, just bad data. Depending on how they were implemented they could cause bricks on write, although usually it just wouldn't work.

Other tuners used much less advanced riser boards which just scrambled the data on the flash chip using lazy tricks like swapping address lines. These could be read over OBD but not using a flash chip programmer - back in the day when everyone knew hardware but nobody knew software, this was a real protection! Often these were used to implement a dealer model where dealers could only write a certain number of tunes.

Other particularly evil tunes would brick the ECU intentionally by just patching the Read handlers in KWP to become "brick" handlers. The less evil ones would just return garbage data or snarky messages instead. This is the big hazard when reading over OBD.

To avoid both of these things, open the ECU, check for a riser board, then read/write in boot mode. This is also the safest way to get a clean slate: flash a stock file in boot mode (Galletto). And this is the recommended place to start.

As for XDF, not many people use TunerPro. Your best bet there is to acquire WinOLS, or to ask someone if they can export the OLS to a KP (WinOLS version of an XDF), and then transform the KP to an XDF. ecuxplot comes with a tool called mapdump which will then turn (old!) OLS KP files into XDFs.

As an addendum to d3irb's excellent post:

Always have a (verified) functioning way to flash via bootmode as a fallback.

Or have a few backup ECUs on hand. Preferably both if you intend to do a lot of flashing.