NefMoto

Here goes, I've been working on this for a little while and hope this can help someone. This was all generated by ME, so there may be some mistakes :P but I did the best job I could.  Let me know if you find any, and I will update this/fix it as time permits. I organized as best I could, still needs a little work, but here it is. Any help would be greatly appreciated!!

***Update 12-19-11***
New map pack- Organized/fixed minor mistakes
CSV.file for those that use earlier version WinOLS/TunerPro

***Update 12-30-11***
Updated map pack- FINALLY defined "PROKONAL" function (still unsure from address 181A2-181AB)
Updated (same as map pack) CSV.file
Added a read me for CSV.file because some people might not know (I didn't!)

***Update 01-04-12***
Updated map pack, had a very great member disassemble "PROKONAL" (readiness) bits to be sure

                         :)****THANK YOU setzi62**** :)

Updated (same as map pack) CSV.file

***Update 01-10-12***
Updated map pack, defined all axis in all the 2d and 3d maps.

For now I'm pretty done. (Time to get back to what I came here in the first place to do... tune the damn car!!) This should have more than enouph in it, if you see anything missing/wrong please let me know. Enjoy!!

Open my definitions map for 4B*DC ecu ;) I didn't mapped error classes like funktionsrahmen IDs but instead I mapped them directly to P**** errors, this way you'll know exactly which bit is responsible for which error...

Thanks for the reply, on second thought though I don't really think it matters to find these bits unless a mil or cel is thrown correct?, in which case it's easy enouph to code out via Tony's post about it. 

Yep its easy, I actually made my whole error class table with this method :) And yours should be same, so you can save your time by just copying values from my kp

Thanks for this. Came in really handy in defining another file. Lots of good maps.
Enough maps for a Stage 3  :)

You sir are quite welcome! I'm glad that I'm FINALLY in a position to give back instead of just taking! I need to organize/update this with more . In due time.... :)

That's great :)

It looks like you have the load axis for KFFDLBTS/KFLBTS wrong. It should be 1D26A not 1D26E, I think. That or TABGTS is in the wrong place.

These Passat/Audi files are a rare breed. They are completely different than the MKIV/TT counterparts. Such a pain to define.

Thanks for the heads up, I will look into that. Yes, they are different. All the Damos/map packs I have compared it to have been totally different. Not real bad, but a pain in the ass none the less!

So I had a look this morning and everything seems to be in the right place? Unless TABGBTS is at 1D1FA? I don't think it is, but if you could have another look I would greatly appreciate it. I'm pretty sure that the axis for KFFDLBTS and KFLBTS are correct. Whenever you have time, thanks!

TABGTS seems to be correct but your axis is wrong because it has TABGTS as a value.
If you move the axis back a few values you will see what I mean.

Edit: I may have been wrong. This Passat file is playing mind tricks on me.
This is how it should look like:
(http://i.imgur.com/yPobi.png)

Sheeewwww.... I've been looking at it trying to figure out what I've done wrong for the past 30 minutes!! It's ok, gave me a chance to finally figure how to do screen shots! On a side note, do you have any idea the where the "x" axis is for KFLDIMX located at 1EA5E? Thats been driving me crazy for a while? Only if you have time, of course, thanks!

in my file it is @ 13546

That's funny, I originally had it at 1352E, which is the same as your 13546, and wasn't 100% sure. I'll take that, thank you!

you're welcome, Rob :)

Rob have you manually checked that all of the PROKONAL bits are correct? I don't want to use a bad base  :P

No, I apologize but I'm unaware of a method to do that. If you would enlighten me on your method, I would be more than happy to do it. It is my absolute desire to get this right. I lined the prokonal addresses up with another and made sure the damos had the same amount of addresses. Hope that makes sense, at the time it was the best idea I could come up with. Sorry for any confusion/downtime I have caused.

Nah from looking at it I can tell its wrong. No worries man. I'll have someone disassemble my Passat file and you can use that as a base once I define mines. :)

Well that sucks, I was pretty uneasy about defining these bits. My method was not as precise as I like to be. It was just a rough educated guess. Let me know when you have yours disassembled (I assume that's probably the only correct way to do it to be for sure). I would greatly appreciate it!....

Bump- map pack updated/organized MUCH better in first post.

Happy Holidays to all, enjoy!

And chance of getting these ported over to TunerPro xdf's?

Honestly I don't have any plans to. I mean, technically you could open the csv file and transfer each map to tunerpro, one at a time. Might be time consuming, but nowhere near as bad as having to find them all manually like I did. You don't really need all of them anyway- only like 80% of what I have. I remember reading somewhere that somebody was making a program to do just that? Don't know what ever came of it? Really, if you transfer it yourself, you'll probably be doing yourself a favor with the experience you gain. Just my 2 cents. Happy tuning!

Bump; Updated ori post with updated map pack/CSV.file- enjoy :)

Update, probably last update for a while. I defined axis to go along with each map. I think this is a great start for anyone with an 01 A4. Enjoy. Special thanks goes to setzi62 for his skills in disassembling some of the code for me.

Is this at all similar to the 018M ecu? A friend has an 018M APR stage 3 car that I want to retune and I haven't found any definitions for it.

I have read on the WWW that they are interchangeable, but take that with a block of salt. A stock M box can be found here

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

If you don't already have one. When I get to my pc, I will happily open both bins to see how close they are.

What turbo is going on the stage 3? I'm working on putting something together myself. Right now its powered on hopes and dreams, but maybe with some more parts by spring/summer.

I just compared both bins, from what I can tell they are very much the same. Of course stuff is scattered across at different addresses, but still really close. You could probably flash my file, and just use it, or you could use my definition file and just change the addresses where need be. Like I said, everything is in the same order, just not at the exact addresses (from what I can tell) Let me know if you need help finding anything.

Hey. I have started to make a XLF definition. But I cant get enything complitely right with rob's CSV. Is there something differnt with LSB/MSB or something else in TunerPro vs. WinOLS?

Are you using the same bin? There's 2 or 3 revisions floating around. What's maps are you having trouble with? What's LSB/MSB?

LSB and MSB stands for Least Significant Bit and Most Significant Bit. I have used your .8 bin/hex file. isn't that right?
Im getting NMAX to work, easy. But Timing and boost is problematic, I can see that the code is wrong in the table. So its like the bin is wrong.
Thanks for reply.

I'm at work, so I cant check it until later. The only thing I can think is that it needs to be signed to see negative values. I know WinOLS has this option, I'm unsure if tunerpro does. Check this out.

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

Again, this may not be the problem you refer to. Without screen shots or something more to go from...

I think I figuried it out. I changed the direction og row/column from your .csv :)
And TunerPro have the signed bit option. I turnd this on too, so I can see negative numbers.

Thanks for help.

Did you get it figured out? My apologies, but I don't think I'll be able to have a look until Sunday evening. I was hoping to have a look this afternoon, but work ran over, and this weekend is packed.

It's ok. I think i figured it out, but does not all det 018CH have the same software? I have now started to convert the CH to CG. There is a lot of differnce there, but with a few days I think I will work something out. I have allmost done the timing.

I'm aware of one other version, or revision, that is posted on here for the CH Box. If the numerical value of the software dictates the sequence of the revision, I believe that the one I have posted is the most current that I have found. I'll have to update this map pack, as I've done some other things.

I see. I have another question. Is there a logical way to find the X and Y advisor? Like RPM and percentage values.

Open WinOLS, compare said bin file to damos. This part has taken me hours, but I learned a lot. There are a few posted on here, don't overlook Me7.1 damos, the earlier ones helped a lot as well. The S4, and Seat Leon are what I use primarily. Both are posted on here. Unless you know disassembly, this is the best method.

I see, thanks. Yes, making definitions take a lot of time. I have used meny hours allready and just made definitions for most of the timing. But I havnt found the X/Y yet. I'm useing TunerPro, is there any major differnces that I have to be aware of?

WinOLS has a "2d" mode to view the hex in. I'm not sure if tunerpro has this. It doesn't cost anything to download the demo, its here;

 http://www.evc.de/en/download/down_winols.asp

Imo it's easier to find maps with WinOLS, even the demo. You can not export files with the demo version, and most people can't afford the 1,600 euro full version. Then there's the not so legal way to get the pirate version, but its really not needed. Tunerpro has a better checksum as its been proven on here to validate the checksum after new code has been added to a bin (for AL/NLS). Plus the checksum is like a 13$ plugin.

I take a damos, try these;

 http://nefariousmotorsports.com/forum/index.php?topic=467.0title=

open in WinOLS demo. Search for map ID (say KFZW for timing), and look at it in 2d. compare map, and x axis and y axis. Find the same in your bin, usually found at or around the same locations. I just compare the patterns between the two bins. I know its not exactly precise, but  without real disassembly this is the best there is. This has worked for 99% of what I want.

 I hope I have helped to answer your questions, let me know if you have more. I enjoy passing on a fraction of knowledge that this site has given me. :)

I see. TunerPro have the ability to show the hexcode in 16 columns row. You can allso show the code in binary and decimal.
I have tried to serach for X/Y in decimal mode. Should be something like 013,019 and so on.

But maybee i should download the WinOLS demo if this is better for making definitions. But i think i will use TunerPro to make tuningfiles. because I have the ME7 checksum plugin there.

Thanks for help.

Well, here's my opinion on things. I think WinOLS demo is great for searching through the code and comparing damos to bin files. If you want you can even define a whole bin with WinOLS..... but for tuning I think its better to have tunerpro and plugin. There's pros and cons to both, but in the end the 100% legal way to do it without problems is WinOLS demo and tunerpro with plugin. That coupled with Tony's software and you have everything you need for just a couple dollars.

Again, the only way that I have found to define x and y is to use WinOLS 2d mode and open where it is located in a damos file, go to the same address in the bin that I want to define and find the same pattern. It's never really that far away.

Is there a particular map axis your having trouble with? I'd be more than happy to take a look.

Yes you have right. I think I got to try the demo and use DAMOS to get it easier for me and put the data over to TunerPro.

But another question. What is your KRKTE conversion parameter? I m getting out 0,079 with X * 0,00045.
And i am having a fue problems with LDRXN/ZK. They have complitely the same values :/

I'm at work right now, so no pc. Are you saying that LDRXN/ZK have the same values, or the axis are the same?

The values is the same. begins with 90. I think that is te startvalua for most 1.8t

I will be sure to post address and offset for both LDRXN/ZK along with a screen shot of there location. I'll have it done before the days over.

LDRXN
16 bit- 16 by 1 map
address 1F1D6
offset .023438

LDRXNZK
16 bit- 16 by 1 map
address 1F218
offset .023438

If I load the ch box this is completely right. but if I load mine cg and putt inn 1F1D8 for LDRXN and 1F21A for LDRXNZK they are kompletely the same. Could it be that my box have the same values or is this random and wrong address on one of them??
BTW, What is your X and Y addresses here?

Do me a favor and send me your original file. rob.mwpropane@yahoo.com
I'll take a look. Today I have a little work, then change some suspension parts on my car, and then I'm free. I will take a look at x and y addresses, but I know its nmot (engine speed), and they are located rite before each map.

Thanks mate. I will meanwhile look for more maps.

Updated to include kp file for revision 360101 (in first post)

I think that your y-axis address for KFTARX and KFTARXZK is off in your 360101 map pack. I believe it should be 13480.

But again, thanks for posting this.

I believe your right! Fixed and updated in the ori post. Thanks for pointing this out (maybe I was tired ??? ::)). Let me know if you find any others, but in reality, 99% should be good. I have never changed axis in KFTARX/KFTARZK, but when you change values in structure PLEASE proofread before doing so (sounds like you are!)

Yes it was, thank you for pointing this out. Fixed in ori post. Let me know if you find any others. When changing any structure PLEASE proofread before doing so (sounds like you are!!)

Could you post the CSV for the 360101 software?  LDRXN isn't ligning up.

Side note, how can I find out which software I'm working with?

ldrxn: 1f0e4

I'm not sure in tunerpro, but winols (even demo) file>properties.

The location that k0mpresd mentioned was correct so my CH must be the earlier software. I ended up figuring out the maps I needed to delete secondary air and rear O2 so I really don't need anything else however if you do have the csv for the early software, I wouldn't mind working on an XDF for the community.

I'm not in front of the pc (have the kids at the dentist), but I'll try to see if I can upload back here later. If I don't, just pm me to remind me;)

***Here you go. Anyhing written at the top and not filed in a sub folder is still a work in progress;)

AWESOME!

Thank you very much!  Karma has been given.

You sir are more than welcome.

Hi, Rob! :) Do you remember up setzi disassembling binary? Did he dissasemble whole prokonal in 18000 area or just part of it? :)

Here is an updated 360101 map pack with a few more maps added from NWSOLLE and ZUESZ. NWSOLLE is cam changeover and ZUESZ is for 2.0t coil pack conversion dwell times.

If it's not too much to ask, would you be able to find the location of cw_can_r? I've exhausted my admittedly limited skill set and gotten nowhere. It's defined in the TT and S4 damos but I can't match it to this bin.

sorry for the late reply, but I think CW_CAN_R_0 is located @136BC. R_1, R_2, R_3 should be the next 3 bytes.

Is this for the 360854 or 360101 bin? I'm looking at a 360854 file and if it's there then the configurations wouldn't make sense.

That is for the 360101, sorry I should have specified.

Turns out I was looking at a 360101 all along actually. What values do you have there?

@136BC I have 250dec.

Ok that's what I have too, that would make the configurations:
CAN_0 - Getriebe 2, Airbag, LWS, Kombi, Allrad 1, Bremse 3
CAN_1 - Nothing at all
CAN_2 - Airbag, Kombi
CAN_3 - Bremse 1, Airbag, LWS, Kombi

None of those really make sense. LWS is steering wheel controls and isn't present in any of the TT or S4 configuration so it shouldn't be here. All zeros is a bit fishy, wouldn't expect that. I only get errors for communications with ABS and the cluster, so I would assume that would be one of the options.

this is a very helpful map pack although I'm running into an issue with KFZW, KFZW2, KFMIOP and LDRXN. Possibly the wrong Addresses? I mean the values in IOP and LDRXN seem spot on but the axis are broken on all maps.

I've attached the .bin

Accidently attached the def file before this is the .bin

This is a great start for 4B0906018CH ecu.
I'm going to be updating my progress here with a periodic XDF similar to what I did for the S4's M-box.
The entire 1.8t & 2.7t tuning process needs to be simplified, the cars are over 10 years old now.

That would be great!!!! so far I fixed KFMIOP KFMIRL KFZW LAMFA KFLDIMX and LDRXN

I'm searching for CDKAT KFLBTS KFDLBTS

according to the currect XDF CWDLSAHK is located at 18613 but I've read on here its on 18663 but I cannot tell which is correct. I'll post my corrected XDF for CH version 360854 I've hit a brick wall as far as my understanding on finding and coding out the catalyst.

KFLBTS 193B3
KFDLBTS 1D1CE
CDKAT 181A1
CDKATSP 181A2
CDKATSPF 181A3
CWDLSAHK 18613

Perfect thanks!!! But how do you find the load axis for BTS? Comparing a defined HS bin right now looks like its in a completely different part of the binary.

I think I found KFMLDMX - 1C594?

Gonna bring this back from the dead, looking for ZKLAMFAW and I think I might have found it at either 1D1FA or 1D20A. Can anyone confirm?

Has anyone been able to find Kflamkr and Kflamkrl in the 360854 file, or does it just not exist?

I think I'd like to go this route for fueling, but I'm not sure if that's possible with this file.

Found 'em. Kflamkr @ 19097, Kflamrl @ 190BB.

I didn't think to check the 360101 file, which gave up the locations.

Derp.

Spent about an hour comparing with some bins with know locations and still haven't been able to find:


AHKATMN
AHKATMX
AHKATS
AHKATSB

added some maps to the last updated map pack from rob in 2012
added eskonf and var tables, added nwpmbbr and vwpmbbr for left foot breaking

I have been updating that file too, mine has the 2.0 coil settings , left foot braking and a few other things. any chance you have locations for ahkatmn, ahkatmx, ahkats and ahkatsb, I cant cross them over from anything still. i managed to get a lot from a few passat files on here actually

Heres where Im at currently

Here i got bored and cant sleep, heres another 48 more in this one

Added ESKONF and ESKONF var, KFMIZUFIL, UNS, UOF, KFZWMN maps, ELDLRP, TDLDRA, TDLDRA2, KFNWGM maps, KFTVSA maps, EDLDRP, NDLDRAPU, KFVPDKLD

Hey im using a 018ch 360101 and have an xdf i use with everything i need except parameters for armd interventions. Specifically i need to find TMAR, or KFDMDARO, either one will do but if i can find tmar then kfdmdaro wont matter.

This is pretty much the last thing i need for my tune to be done. Ill go through the whole learning curve of learning how to find it myself if i have to but if somebody already has the addresses or can find them more easily than i can id appreciate it lots.

Somebody helped me find them here they are for 018ch 360101

1189E  1x1   TMAR            (8Bit)
1F4F2  6x8   KFDMDADP    (16Bit)
1F552  6x8   KFDMDARO    (16Bit)
1F5B2  6x8   KFDMDAROS  (16Bit)