NefMoto

Hi there

This is my first post and I'm am new to remapping. I am keen to learn abut how and why each map is changed and the effect it has on the car. Previously I have paid company's to remap my ecu's in different cars for different reasons like pdf removal etc. My current car I brought to just play with this stuff is a 2002 Audi Allroad with a 2.7t BES engine. The ECU I have is a 4Z7907551Q as its a jam import into New Zealand. I have done a heap of searching on the web including this site but cannot find much info on if I can find a .xdf or some sort of software for winols to help with map identification. I have read the map from my car with a kess v2 so I have a hexdump to play with. First question is if I use this map and adjust it do I have to worry about immo or not or if I try a map from a different source will I have to worry about it? Second question is the main ECU I can see people are remapping for this is a 4Z7907551R is this possible to use to remap mine? Im only looking to do a stage one for now but would be good if there is a already modified map that I could compare with so I can see the sort of corrections and modifications to further the performance of the car.

Thanks for your time and hopefully one day I will babe answering another beginners questions

You search bad, start by reading this s4wiki.com/wiki/Tuning , I would make a copy of EEPROM and Flash (this will be useful for you if you turn your block into a brick) As I remember the definitions from “R” and “Q” different you have to look for cards. recalculate checksum after changes

Thanks for the info. I must search bad lol I started reading the s4wiki.com after making this post which is extremely helpful in what im looking to do. By EEPROM im guessing that you are referring to the dash cluster? as for the different cards im not totally sure what you mean but im guessing they have different .xdf files for Tuner pro?

Information about the block is stored in the eeprom (in me7.1.1 chip 95P08), binding to the dashboard block, block coding. just make it

Yes. These are definition files, the location of some variables and maps in different blocks of firmware 4z may coincide, the rest will need to find and change the addresses in the definition file