NefMoto

Hi, i'm searching  map definition (map pack) fort rs4 b5 8D0907551K .

I find this: http://svn.curtisfong.org/filedetails.php?repname=mesim&path=%2Ftrunk%2Fdata%2F8D0907551K.kp&peg=77

But i don't know how make a .KP file with.

thanks...

From that URL just go back one level to /tunk/data/

http://svn.curtisfong.org/listing.php?repname=mesim&path=%2Ftrunk%2Fdata%2F&peg=77

Then you can download the .kp file you displayed above.

Sorry but i see .KP for 8D0907551F, R , G , M but not for K?

Ah, yes sorry I guess that was too easy!

nobody?  :(

Just flash it with a different rev.

why do you car if it is k?

other rev for RS4 B5 is 8D0907551F, but if i flash a K ecu with F software the ecu will not work , and the car will not start... no??? i think i can't do this.

may require a cluster or engine recode.

unfortunately, I am not familiar with F/K box differences.

the k-box should be the one with EODB Function in combination with Multifunction Indicator Light... thast the whole difference (getting Euro EU3)

There is an RS4 K-box .ols is in this 2.7t.zip file:
http://nefariousmotorsports.com/forum/index.php?topic=613.msg5053#msg5053

I haven't even opened it, but there it is by title.

The 551K file in there is actually 551F

You can not flash 551F into a 551K ECU, it will brick the ECU.

551K is a VERY easy file to tune. When I say tune, I mean tune correctly, not just lifting load limiters and other such school boy methods.

What is the big deal with needing a *.kp file or a map definition? If you are not able to find the parts of the file that need tuning, then you shouldn't be tuning that file at all.

I disagree wholeheartedly. Tuning skill/knowledge can be almost completely decoupled from disassembly skill/knowledge. Not saying that I'm skilled at either of those, but someone might be an incredible tuner of the actual variables/maps, while at the same time having no idea how to disassemble the hex code into workable maps.

I don't think everyone who wants to be able to tune their car should have to learn how to become a computer programmer/disassembler first.

if the rs4 k-box is so optimal for tuning, why haven't we completed this line of repairs yet?  i know prj was working on something, but i haven't seen anything tangible come from that yet.  does anyone know more about this and where are we getting hung up?

I am guessing 551F and 551K have different EEPROM structure, so EEPROM needs to be flashed from 551F as well.

I have made some light mods to my 551K file, but generally it's about finding all the maps you need to tune via other definitions.
There's 551G and then the Allroad definition. Using those two you can find any value pretty much.

I haven't had much time to tune the car. Been working on fixing it most of the time.
Don't even have WBO2 installed on it yet.

Okay, so from what matchew says these ECU's are physically incompatible between each other.
Meaning the difference supposedly is not only EEPROM - could be boot rom that is different.

My car is 551K.

The maps can be found easily, but the process is tedious.
I made a small map detector, so far I get 883 maps if I feed it with all the .kp's and .bin's I have.
It basically looks up exact matching maps that are over 3 bytes in size with an offset.

This is still less than 1/4th of the total. I guess I could try to optimize it for some more averaging, but the rest will have to be done by hand.

I think it is probably worth trying to find all the maps.

Why not give it a shot?

I did it by hand for the M box :)

If I have time I will start on it.

Last I checked, the M-box definition available on your SVN was very far from "all the maps".
That'd take a ridiculous amount of time to do by hand (4000+ maps/constants).

It's not hard at all to find everything that is needed to tune, at least for me... it's just tedious.

I mean for "all the maps I need", not literally, "all the maps", which IMO, would be pointless.

Oh, I agree...
But there is so much that can be automated.

I played around with some algorithms, and I am getting pretty good results with just binary analysis.
An amalgamation of my map pack parser and XDF generator.

Obviously some things will have to be done by hand, but I should get a pretty good file by just feeding it existing things.

The algorithm searches for all the maps with the exact same contents within a 50kb offset, with some limits (minimum map size).
After that, it takes each match, and sees how many bytes in front and behind it match as well (outside of the current map area).
It then chooses the map with the largest matching region, which pretty confidently is the correct thing.

Once you have a few key maps, you can then do the same region extending technique, but lift the minimum map size limit, thus getting lots and lots of things.
There's a few quirks I have to sort out, such as locating axes, but other than that I'm almost done.

Hi guys,
I saw that flashing the K-ECU with an F SW would break the ECU. Is this true? does anybody have experience with this? And what happens exactly? completely dead and no way back?
It seems that I have this problem, but I would like to know if this fit's to anybody's experience.
many Thanks in advance
Greg

Just flash with 551K in boot mode. 551F and 551K are incompatible between each other indeed...

Hi,
the prob is, that I can not get the ECU into boot mode again. Seems to be dead...
Are there other options to check the ecu if it is really defect? Or might it be that the ecu is locked...?

You should be able to get it into boot mode regardless of what is flashed onto that chip.

You could flash complete crap onto that chip, and you'll still get it into boot mode.