NefMoto

its not perfectly organized but, oh well!!

please let me know if you know any maps to be wrong!
thanks!

2-16-15 updated map pack, had one defined backwards (KFLDHBN)
dont know how to replace this one, so ill just make another post with it there

Can you export a copy for the 1.721 version of WinOLS (if possible)?

thank you
epy

there's no option to change the version. i could to .csv file tho if that helps?

That would work! Thank you. I am just digging and reading and comparing as much information as I can on maps for the MED9.1 ECU.

epy

here you go!

as i said before, to anyone that finds anything wrong, please let me know and i will correct it!! i just want it to be as accurate as possible
thanks

Roger that. Thank you.

epy

Does winols allow you to also export the axis addresses for the maps?
epy

not that i know of, ill look and see tho. i could have missed something

I am actually having a harder time determining where the map axis addresses are. The maps are not too bad, it just takes time to scan through the hex dump and find a match. But the damn axis addresses are damn impossible at times.

epy

Which are you having a hard time with? Let me see what I can do.

I am looking at KFLDRL right now in a 115G file (attached). The 10x16 map looks to be at 1CF3E8, but the axis is elusive to me.

epy

1CA5E4 RPM
1CF7F2 %

What was your process to find these addresses?

epy

If you know what they look like in other files, you don't need matching values, just similar data :)

Thank you.

Does that map look funny at 1000 rpms? Seems it goes down, when it should go up.
epy

The question that I have is, how do you know that this is the axis that the ECU is using. In other words, if I want to modify the axis, and I want to make sure that the ECU uses the new axis, how do I ensure that?

epy

You are free to change the axis at will, BUT..

You must ensure that it is not a shared axis. If it is shared with any other maps, you need to ensure that any changes made are reflected in any other maps that use that axis.

As long as you modify the correct address for that axis, the ecu will use it. You can't just create a new axis wherever you want and expect the ecu to use it, not without custom code.

Does that make sense?

ah!! So when I define a map in WinOLS, that definition is transferred to the ECU. I thought the mappack, xdf, or kp file was only used by WinOLS or TunerPro etc. and that the ECU has its own references for where maps and the related axis are.
epy

The mappack you create IS only used by winOLS, but if you do it right, it will match what the ecu uses.

When I said you can change the axis, I meant values, not location :)

This actually confuses me, because I can read a file from the ECU and it will not have the maps defined or the related axis. Then if I flash it back to the car (without any maps or the map axis defined), it should work.  ???
epy

Think of winOLS and tunerpro as the legend to a map. The map is accurate without them, but they help you to understand the contents.

Which maps use which axis, as well as the their factors and locations are all defined within the binary you read, but not in the map area. That's all part of the actual code.

I might be making a mess of this trying to make it clearer.

Ok. That makes sense. I thought you were saying I can find any address to use as the axis as long as it was the correct values, which was confusing me.

Is there a way to read the part of the binary that tells you where the maps and each axis is?

You can disassemble the ASM to do that with a tool like IDA. The "part" of the binary that does that is the actual code.

yes, IDA will confirm the axis'. i have no idea exactly how to make it do it, but i know it can!! it would be nice if that type of stuff was explained in a guide for IDA. that program has a steep learning curve!

Thanks for the map pack, perfectly lines up with my 2006 Octavia RS (ECU MED9.1 1Z0907115A 0261S02339 386859)
No offset needed.

really?? nice to know!!

heres the updated pack few more maps and correct KFLDHBN

Thanks for keeping this updated!  ;D

Has anyone done any work to start creating and XDF of this KP and CSV?

no problem!!

i have not, i tried with tuner pro once, but it wasn't as fast as i was hoping so i stopped. i might again someday, but i don't use it myself so im not in a big hurry to do it

I guess there is no time like the present for me to learn. Would you be able to upload the latest CSV of this?

here you go, sorry it took so long!!

Thanks for uploading this I'll start on it this weekend and upload my progress.

another update with a few more maps, mostly ARMD

So i have tunerpro, winOLS, & Nefmoto.
But I need a XDF file to make heads or tails of the rom file.
I could not generate a XDF from any of the files already posted in this thread.
Any help?

TIA

Ben

use ols and the .kp file

Thankyou for the above.

would this map pack line up with a MED 9.1 from a 2006 jetta 2.0 tfsi Bosch Software Number: 1037391667
Bosch Hardware Number: 0261S02080
Vw Software Number: 1K0907115B 
System Type Number: 2.0l R4/4V TFSI

trying to tune my car to work with my cold air intake with out throwing p2177

i don't think it will line right up, but i could be wrong

Could you please post the original file in this post as well? :)

you want like a BDM read? or just the bin?

heres the stock bin. i kust gave it a generic name at the time, cuz i knew what it was lol

sorry for late replay i only have the mpps cable for now going to order the bdm reader so i would like a bin only i guess and what file would you like posted someone else worte the file for me that is throwing the code (p2177). pm me for the file please

 when i flash back to the file i got from the dealer when they did my ecu swap i can't do the group 60 in vcds TBA has a error 
ecu-nr prod 1K0907115B
ecu-nr ecu 0261S02080
software # 391667


but the file you posted will work on my car but im getting high fuel trim on stock file and stock intake

Hey all i got my ltft issus fixed someone on this form bench flashed it back to stock software for me now i would like to find a map pack that would work for my file,  stage 1-2 files would be nice to learn