NefMoto

Hello, I'm looking to find an XDF definition file for my car, or a working pair (xdf + stock BIN) to work with.

My goals include:

1) write out SAI (via MSLUB method)
2) some basic performance improvements later on.

Ideally I'd like some help at defining my own file, but a working example will probably be easiest to learn on. If anyone thinks it's a good idea, I'd be the goat for a "how-to define your file" thread.

Is there anybody out there?

Ok, so keeping with the theme of self-learning and searching, I've dug up some info.

MSLUB is apparently located at 0x182cf and is 8-bits.

How do I set this up in tunerpro? I've found an xdf that will (hopefully) work for my 1.8t file. The xdf has many tables defined, but not MSLUB.

I'm posting some screen shots of tunerpro with me trying to define MSLUB, along with my original file and the xdf I found. I just really don't know if I have this right, or complete.

anyone have a few minutes to help me through this?

Thanks

Thanks for trying. Here is your prize :)

You are a Prince. Much obliged!

ddillenger: Setting all values in this MSLUB to "0" will tell the ECU to expect 0 airflow during SAI operation? Are the original values in this map volts?

Sorry for all the questions, I just want to understand what I'm fooling with.

Is this photo correct? Hit "execute", save file and re-flash to car?

Axis is volts, map is kg/h. Setting the map to 0 tells the ecu that no flow is expected at any voltage, so when the ecu sees no flow it returns a pass. I suggest unplugging the pump with this mod.

Also, don't forget to update the checksums.

That clears it up. The SAI pump is already out of the car, died after it filled up with condensation due to a faulty combination valve. I ended up removing all of the PCV and SAI gear, but I'm looking at re-installing the n249 valve and vacuum reservoir, apparently the bypass valve can be hard on the turbo if not controlled electonically (currently operated strictly from intake manifold vacuum)?

I've got an email in to MTX for the tunerpro plugin. Going to flash as soon as my checksums are fixed.

Thanks again for all the help.

That xdf you posted does not align with your stock file much if at all.

It's my xdf for 518F and is not even close-lol. That's why I created a new one for MSLUB. Also, if you don't have the hardware plugged in (relay or solenoid) for sai, you will need ESKONF or resistors (ick).

Yikes. Well thats why im glad you guys are here. The SAI pump relay is still installed.

Is there a well known starting-point xdf available for my engine for performance?

Well, I've sent payment to MTX for the checksum plugin. Hopefully have it up and running tomorrow for my first modified file flash, cool!

After that's done, I want to start working on some small performance improvements. I've been searching the forum and google for an xdf for my ECU, but it's hard to find one. Anyone have this file in their bottom drawer? The engine is AMB and the trans is 6-speed manual, if it matters.

Cheers

Hey ddillenger,

I got the MTX plugin up and running to check the new MSLUB "0" file. When I save the file however, it says there are no checksums to correct. Perhaps MSLUB is not monitored for checksum error? Will flash tonight if I can confirm not dangerous!

Save the file, then open it again. Have the changes been saved?

It's telling me that the stock bin file is not where it's supposed to be. I renamed a copy of my stock file according to MTX's instructions, and can confirm the original MSLUB values are on this "comparison" file in the C:/ directory. I'm going to drop MTX an email, but they're all asleep right now being an Italian company. Any Ideas?

Would anyone be able to run a checksum correction on my file? I'm not sure if it's just MSLUB or some other issue because (for now) I only have MSLUB defined on my XDF file. Maybe my original BIN is corrupted somehow? Here's the original file, and the new SAI delete file. After the trouble I had reading the file originally, I don't want any extra trouble due to flashing back a bad file! :-[

ddillenger,

I tried starting over, modifiy the stock file, save it as a new modified file and it still gave me the message. Re-open the modified file and the changes are intact.

Check the file with me7check, post the screen it displays.

Here it is. apparently 3 errors remain. MTX email reply says I must not have named the original bin file properly in the C:\ as per their README file. I'm pretty sure I did this right, but I'll double check. Here's the screenshot from ME7Check

GOT IT!!  :D

I figured out the problem. In the readme file from MTX it states you must rename your file : "C:\Bosch_VAG_ME7_2002.BIN". The problem I had was I copy-pasted the name, which actually created a file called C:\Bosch_VAG_ME7_2002.BIN.bin.

I emailed MTX that it might be a good Idea to mention in the readme that the name visible in the folder will look like "Bosch_VAG_ME7_2002" without the .bin suffix.

Now I've got "checksums sucessfully calculated" message! WOOT!!

Thanks for your help again DD

Flash Success!

The new file is written to the ECU and car runs, drives, starts again after shut off etc. I'm so stoked that it worked.  ;D

Now I'd like to find some tuning definitions. The search continues!

Awesome right?

The power of DIY :)

Hello again.

The MSLUB trick worked perfectly. I confirmed SAI readiness via OBD2 scan tool. I still need to defeat the EVAP
I've been reading and searching and trying to figure out winols to compare my current .bin file vs another well defined .bin file. I feel like i'm spinning my wheels a bit, and need a bit of a push to get going in the right direction. I'd like to eventually have the skills to define the maps I need in my own stock file, but I'm finding the learning curve is  very steep. Anyone local who is doing this sort of work is keeping their secrets (one guy wanted to charge me $350 just to eliminate SAI readiness failure).

I understand it is possible to flash another well defined stock .bin file to my ECU, and use that xdf. What I need to know is how to properly confirm that the new .bin file will work with my ECU. How do you select a file to "cross-flash" for me7.5?

Here's my stock file again, to avoid returning to page 1. Hope someone can help me out.

I found a comprehensive 1.8t definition file and a stock file to work with. The stock file is the same engine number as mine (AMB). Does this mean the car will operate on this file? Mine is standard transmission. when I compared the files in winols, they weren't the same, although it looked like the locations were very close for each map. I was able to line a few of them up to compare, but they didn't all line up together, different offsets. Normal?

I guess the *ideal* thing for me to do would be take the known locations of each map in the AK file, find these maps in my original file and create a new xdf. A part of me wants to go through all of this, but it is going to be a lot of work, and I'm not actually "discovering" anything new. I'm just copying the last guy's efforts. Would be easier and more productive to just use his xdf and say thanks for the hard work.

thoughts? Am I headed down some sort of rabbit hole here?

I've attached the AK file I'd like to flash to my car, and my original file as well for comparison

Little help please?

AF AK BC can all be crossflashed. I recommend doing some searching, and using the 518AK file I posted along with the 518AK xdf (also posted by me).

Thank you again. I really appreciate the advice.

DDillenger,

I've found your 518ak bin and xdf files, and successfully cross-flashed the bin to my ecu. Thanks again for the heads up on compatibility. The xdf is a good start, but I'd like to add a few more parameters. Is it possible to copy entire parameters from a well rounded xdf (mbox s4 for example) and change the parameter location to suit the 518ak file? How is this normally done? I'll post the files I found and flashed.

Is it a good Idea to continue asking questions in this thread, or start a new one somewhere else?

Yes, and yes.