NefMoto

Compiled against 8D0907551A 0261206110 352345 for this XDF.

Link to rom:

http://www.nefariousmotorsports.com/forum/index.php?topic=4.0

XDF Contains:

(http://i272.photobucket.com/albums/jj172/spen0007/8D0907551c.jpg)


{POST EDITED AS I MISTAKENLY THOUGHT THIS XDF I GENERATED WAS FOR 8D0907551C}

Thank you for all the hard work.

Unfortunately something went wrong with the adresses in the xdf.
The values in the maps are all over the place.

Perhaps you could have a second look at it.

Thanks for the update.  I posted the wrong file, this was the 8d0907551a xdf.  Sorry for causing confusion and I will do a 8d0907551c xdf soon.

Spen

Fantastic news. Many thanks!

Nice work  ;D
Ldrxn fixed to start address
0x1D8B2

all the xdf files so for in this thread have given me issues with the setup on maf tables, would crash tunerpro.  here is one based on the other revision above by jude, this should allow you to view the entire 512 cells of the mlhfm maf voltage table. 

-please let me know if you find any other unstable areas.

Thanks for working on the A-box xdf guys?  Everyone with odd-ball 00 S4's should appreciate it.

Can we clean up this thread after doing some testing to verify that we have the right XDF and definitions, and isolate crashes of TunerPro to specific items?

I am willing to do some testing. I would like to get a post of the most recent and corrected (to the best of our knowledge) XDF file.

My TunerPro ver 4.14 that I use on WinXP shows axes-less maps with this XDF file.

I loaded the Abox file from this site, which I had flashed in my car in the past.

Anybody having this problem?

use the one I posted. it works just fine with tuner pro

This definition file also works for:
4B0907551L - 2000 Audi A6 2.7T Tiptronic
4B0907551K - 2000 Audi A6 2.7T 6-speed Manual

I gave up working on this file after I used SnowTrooper's Mbox XDF with the Bosh MAF voltage linearization.

I was going to do a proper Mbox switch as of Nyet's wiki. I was unable to find a socket to do the mating without splicing. Then I thought of putting the Bosch voltage map in the Mbox, and that is when I searched here and found the gem.

Big thanks to SnowTrooper. Car runs fine. I notice some minor rough-idle in cold starts in the Winter. But I found that this is the case with other Mbox S4s and the Porsche 996 Turbo. it is minor and I can live with it.

Here is still the same thing weird with krkte, as it is with the d and c box.

If you look, it is on these boxes around 0,56 ms/%. So even if you change the scale from 0,000167 to 0,00011111. This wont work.

Where is the bug?

I am searching for the real krkte and its conversion for a longer time...

Has anyone flashed this into there S4 A box? What kind of gains we talking here?

I too am searching for KRKTE.  Cross referencing the M box defined file, i have 3 workable locations but nothing to suggest that any of these are it.

17050
1B29E
1B2E0

In the M Box it is located in a sequence
70 03 4D 65 04 starting at 1C2BC

In the A map the 4D 65 is found at 1BFCE with a matching sequence at 1BFA2 (A box) and 1C290 (M box)

I feel that should eliminate 17050 but that leaves the two 1B2xx locations

Sorry, forgot to post the file i was referencing as its a different software version than the one in the first post

found it
18da8
missing as its only 8 bit on this file.  Conversion .001776

Why not just run M and call it a day

I'm not the OP, but I like your idea!  To cross-flash an M-box tune to an A-box (or possibly to an F-box), I assume I'd need to flash the whole eeprom as well as the tune, correct?

2000 S4 6MT should be A-box, but I'm not the original owner and this machine's obviously been tuned before (e.g., 17psi).  The label is missing from my ECU, and I've been unable to read the eeprom (tried both the 1.31 and 1.40 versions of ArgDub's tool). 

I took the chance (hoping it wasn't APR, etc.) and was able to read the flash BIN (attached) using the latest NefMoto app.  I used TunerPro to do compare differences, and this BIN is definitely closer to stock A-box (342 different bytes) than stock M-box, but only 104 of those bytes are defined using the A-box XPF.  The most matching definitions were 207 of those bytes using an F-box XPF, but unfortunately I can't find a stock F-box bin to compare.

My questions are:
1) What "box" is my current tune?
2) To cross-flash, is eeprom needed as well as tune?  If so, where can I get the M-box eeprom to cross-flash to A-box (or F-box)?
3) For whichever box I have, is there an XPF available that would allow me to see all the variables needed for a rear O2 delete, for example?  If not, is there a way for me to create a full XPF definitions file for whichever box I actually have?

EDIT: VCDS reports "8D0 907 551 A" (A-box), FWIW.

EDIT #2: Found a 551F bin on the S4Wiki and compared, and mine's definitely not that. I guess it's an A-box tune (BIN) after all, but the A-box XDF simply isn't as complete as the F-Box XDF. Need to learn more about these...

Since M doesn't have an immo, you don't even need to worry about copying the eeprom over, you just have to get the engine coding right (which you can do entirely through vcds), and copy the bosch MAF tables over (or convert to hitachi).

Honestly, dont bother with the F or the A.

Thanks Nye!  An M-box flash it shall be.  Reading the M-box community tuning thread now (http://nefariousmotorsports.com/forum/index.php?topic=6695.180).