Pages: [1]
Author Topic: 2000 A6 2.7T which file to start with  (Read 4603 times)
heromanni
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 13


« on: November 09, 2018, 07:02:37 AM »

Hello all, I'm new to car tuning and wanted to learn enough to make my own tune.

I have read my 2000 audi a6 AJK 230hp ecu file, it is 4b0907551F. Looking with that file there is no xdf to it, I read that there is definition file 8d0907551D that can be used with 4b0907551F. However it is not that complete and needs more maps to be defined.

I have another 2000 a6 AJK ecu with 4B0 907 551 G inside, I plan to take immo off this and play around with it.

What would be the best file to start with?

I have read about going to M-box that has pretty much everything defined. But the maf changing from Hitachi to Bosch is something that needs work. Is it just to open the files with Winols and copy f-box maf data to M-box? which maps? And problem is that is there F or G or any box with Bosch maf and definition file that has all the maf tables defined?

Thank you
Logged
heromanni
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 13


« Reply #1 on: November 09, 2018, 12:21:14 PM »

There is something wrong with the definition file found from http://nefariousmotorsports.com/forum/index.php?topic=430.0

the maps in the definition file are not correct for Y-axis, values and x-axis seems to be ok. I tried using the original file from the same link.

Where is the problem?
Logged
turboat
Moderator
Hero Member
*****

Karma: +45/-3
Offline Offline

Posts: 619


« Reply #2 on: November 09, 2018, 12:54:06 PM »

Take a look at the 2.7T stage 1 project thread, fairly sure it includes an m-box bin adapted to your maf in the first post. I run a m-box on a UK a6, it works but I had to mess around coding out a few errors.
Logged
SQT
Full Member
***

Karma: +2/-4
Offline Offline

Posts: 57


Respectfully SQT ;)


« Reply #3 on: November 10, 2018, 02:44:21 AM »

There is something wrong with the definition file found from http://nefariousmotorsports.com/forum/index.php?topic=430.0

the maps in the definition file are not correct for Y-axis, values and x-axis seems to be ok. I tried using the original file from the same link.

Where is the problem?

The map definition needs to be corrected, since they have an offset for each block, in fact, I am surprised that your question has been answered or I ask the wrong questions.
« Last Edit: November 10, 2018, 12:33:34 PM by SQT » Logged

a6 2.7
sorry for my English
heromanni
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 13


« Reply #4 on: November 10, 2018, 02:53:40 AM »

Okay, need to look for that

There is actually m-box bosch file In the stage1 2.7t topic, awesome!
I Will try that once I get eeprom sorted out, have maybe ch340 based cable there, does not accept ftdi drivers..

Lähetetty minun BLA-L29 laitteesta Tapatalkilla

Logged
SQT
Full Member
***

Karma: +2/-4
Offline Offline

Posts: 57


Respectfully SQT ;)


« Reply #5 on: November 10, 2018, 03:04:30 AM »

I use galleto 1260. I edit my firmware in Winols. In the WinOls, on the definition file 8d, I find the same fragments. If this helps you I will be very happy. Do not forget the checksum after editing. You can try using 8d files in block 4b, I haven't tried it yet. Most likely there will be problems with immo and abs
Logged

a6 2.7
sorry for my English
heromanni
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 13


« Reply #6 on: November 10, 2018, 03:16:39 AM »

Okay right, my plan is to write the M-box bosch file as it is to my G-box. For m7eeprom tool i need FTDI cable.

It sounds like I will have immo and abs problems also then, immo I try to remove completely but abs will give the error
Logged
SQT
Full Member
***

Karma: +2/-4
Offline Offline

Posts: 57


Respectfully SQT ;)


« Reply #7 on: November 10, 2018, 03:47:25 AM »

If you edit the firmware, there will be no problems. If you want to use firmware 8d instead of 4b and use the definition file xdf 8d, then problems are possible
Logged

a6 2.7
sorry for my English
heromanni
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 13


« Reply #8 on: November 10, 2018, 09:42:18 AM »

How do you correct the map definition?
Logged
SQT
Full Member
***

Karma: +2/-4
Offline Offline

Posts: 57


Respectfully SQT ;)


« Reply #9 on: November 10, 2018, 11:28:17 AM »

How do you correct the map definition?
You are using an inappropriate definition file, so you have distorted information
The geniuses have disassembled the firmware c4 b5 ecu 8d on the shelves, creating the definition file, both firmwares are loaded into the WinOls, one of them with the definition file, using the comparison method we find fuel, boost maps, sensor maf and a bunch of many maps and variables (you need to see a lot of maps To accurately determine which one is responsible for what). But I am new and I think that it is not quite right, there are variables that I could not find, some of them relate to disabling the rear lambd
Professionals may leave comments in this thread to confirm or deny this or that information
Logged

a6 2.7
sorry for my English
turboat
Moderator
Hero Member
*****

Karma: +45/-3
Offline Offline

Posts: 619


« Reply #10 on: November 10, 2018, 01:35:02 PM »

How do you correct the map definition?

Download the bin that suits your maf, use the m-box xdf. A6 2.7T should run with a m-box but you will have some dtcs.
« Last Edit: November 10, 2018, 01:45:47 PM by turboat » Logged
heromanni
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 13


« Reply #11 on: November 10, 2018, 03:04:38 PM »

I Did some map finding with winols with m-box and kp file compared to my current file. It does not find all of the maps, some maps are easy to find.

Sure thing I Will flash the M-box file to my car to get all the data, ill have to wait to get ftdi cable, it take few days. After that I can sort the Immo issue to get going. Hopefully there is help on this forum to the dtc issues that Will Come with the different box
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.019 seconds with 17 queries. (Pretty URLs adds 0.001s, 0q)