[The Nightman]

Originally Posted by hassmaschine

5 minutes seems really long. Did you enable fast baurdrate? what cable do you have? normally, it's about 45 seconds.

I'm using the BimmerGeeks Pro K+Dcan cable (link) and have fast baudrate enabled in WinKFP. Maybe I missed something? Here are some screenshots:

[PD330]

Baudrate is just 9600 (seen in last Screenshot). You can set it to max.

[The Nightman]

First start up seemed fine until I gave it a few revs and the idle became very rough. Gave it a few more revs and it went back to normal and remained that way. Possibly due to the adaptations I reset? Went for a test drive and engine felt great. Much better performance throughout the entire powerband. However, I noticed the CEL was on and the fault code was 2AAC:



This code is for the small DISA valve but what's odd is the noted mileage (119,856 km) was 3km before I installed the 3IM and went for my test drive. The DISA valve tested fine and the flap was solid so I just cleared the code and it didn't return after I restarted the engine. Instead, I was greeted with 2A1A:




I cleared the fault and did a DMTL test which seemed to be fine. I restarted the engine and no CEL or fault codes other than 2FA3.

[The Nightman]

I'm trying to get rid of the 2FA3 fault code with NCS Expert. I followed the following instructions exactly but it didn't work - the fault is still there. I used 6BMOT for my MSV80. Is there a step missing between step 9 and 10?

Originally Posted by jazz5000

1. Load NCSExpert.
2. Load Profile and select Expertmode
3. F1 (VIN/ZCS/FA)
4. F3 (ZCS/FA f .ECU)
5. Choose E89 (for the E9X)
6. Select CAS
7. F6 (BACK)
8. F4 (Process ECU)
9. Select the Module I want to Revert back to Stock.
10. F2->Choose "SG_Codieren->ok
11. F3->to start coding the ecu with factory settings according to the vehicle VO.

http://www.e90post.com/forums/showth...1#post20020041

[PD330]

I know the 2FA3 code also from mhd etc. I think most of the guys just don't care as this has not really an effect.

Maybe you have a look to ISTA, for most failures there is an detailed guide how to fix (could end up in something like "replace DME", but give it a try )

[hassmaschine]

yeah, 2FA3 doesn't do anything.

I think even if you disable it in the tune, it still comes back anyway. I choose to just ignore it.

[The Nightman]

I managed to get rid of the 2FA3 code after I realized I forgot to create a blank .man file last time

[j4m35]

Just wanted to report back that I've my 3 stage intake manifold installed and have successfully flashed the MSV70 with RSADelete and the S7581219_523i_to_525i tune; then my GKE211 to ZB#7564218.

I used NCSExpert to code the DME and EGS (with defaults from the VO) to remove the Coding error. Then used INPA to clear any / all of the faults.

On a side note, I changed API tracelevel and IFH tracelevel in WinKFP to 0 and that made the flashing sequence a lot quicker.

Anyway, I took the car out for a test drive and it runs great. Thanks for all the help hassmaschine!

I guess the next step for me is to learn how to perform DIY tunes. I tried converting the .0da file from Intel hex to bin and opening it in TunerPro but I don't see anything. Any ideas what I am doing wrong?

[The Nightman]

Originally Posted by j4m35

On a side note, I changed API tracelevel and IFH tracelevel in WinKFP to 0 and that made the flashing sequence a lot quicker.

BimmerGeeks recommended the same thing but I haven't tested it yet. Glad to know it works!

[rjahl]

Originally Posted by freedomfries

BimmerGeeks recommended the same thing but I haven't tested it yet. Glad to know it works!

Yes, set trace levels to 0. You should be able to flash an 0da in 45 seconds.

tracing can really slow down the process.

[hassmaschine]

Originally Posted by freedomfries

I managed to get rid of the 2FA3 code after I realized I forgot to create a blank .man file last time

Awesome! I'll have to add this as a guide for people who get 2FA3 (and if it bugs them enough to fix it).

Originally Posted by j4m35

Just wanted to report back that I've my 3 stage intake manifold installed and have successfully flashed the MSV70 with RSADelete and the S7581219_523i_to_525i tune; then my GKE211 to ZB#7564218.

I used NCSExpert to code the DME and EGS (with defaults from the VO) to remove the Coding error. Then used INPA to clear any / all of the faults.

On a side note, I changed API tracelevel and IFH tracelevel in WinKFP to 0 and that made the flashing sequence a lot quicker.

Anyway, I took the car out for a test drive and it runs great. Thanks for all the help hassmaschine!

I guess the next step for me is to learn how to perform DIY tunes. I tried converting the .0da file from Intel hex to bin and opening it in TunerPro but I don't see anything. Any ideas what I am doing wrong?

Nice!

well, if you don't have an XDF for MSV70 (and I assume you don't since the only one that exists was created by me), you won't see anything in Tunerpro. Custom tuning support is one of my big goals to finish this year (I can generate XDFs of course, but it's a time sink and takes away from other priorities).

[The Nightman]

Unfortunately 2AAC keeps coming back each time I drive my car:



Researching the code indicates that the servo motor in the small DISA valve is faulty and that replacement is the only fix. Sigh

[hassmaschine]

Yeah, that sucks. Its cheaper but you have to take the manifold off to replace.

[Blueeyesredpanda]

Originally Posted by freedomfries

Unfortunately 2AAC keeps coming back each time I drive my car:



Researching the code indicates that the servo motor in the small DISA valve is faulty and that replacement is the only fix. Sigh

Same thing happened to me. I'm getting new DISAs

[The-Traveler]

Originally Posted by Blueeyesredpanda

Same thing happened to me. I'm getting new DISAs

I checked my top disa because it's easy to get to, and it's tight.

Does anyone know how to check whether the second one is working properly. Is this code the only way? I don't have a code but want to make sure both flaps are tight. As I said, he top one is an easy check.

[Rickyshucks]

Anyone notice a decrease in fuel economy after flashing a 325i to 330i. Gas has been going down a lot faster.. maybe its just me having too much fun with it! Lol

[hassmaschine]

It's in your head.

[Rickyshucks]

Yeah probably. Gas prices are jacked up right now in Canada. Tune has been great btw hass. You sir are #1

[desertman123]

It is given that the first gas tank after a tune is null

[j4m35]

Originally Posted by hassmaschine

Nice!

well, if you don't have an XDF for MSV70 (and I assume you don't since the only one that exists was created by me), you won't see anything in Tunerpro. Custom tuning support is one of my big goals to finish this year (I can generate XDFs of course, but it's a time sink and takes away from other priorities).

Ah!!! So that's what an XDF is for! As you can see I'm a total n00b in this area. Is there an automated way to generate the baseline XDF? I don't mind putting in the time to make an XDF (or improve on what is available) if you can point me in the right direction. It would be a nice learning exercise for me.

[PD330]

No, the xdf contains information which single map is on which address. There are tools like winols which can help to identify maps, but you have to investigate if this is correct and what each map does.
With some experience, there are some maps which can be identified easily (things like ignition timing, torque limits etc.), but other values are nearly impossible to detect (DTC cutoff flags for example).
The best way is to have a leaked a2l file from the OEM, then you have all the maps with naming and just need to translate a little bit. But these files are rare and often expensive.

[justpete]

Originally Posted by PD330

No, the xdf contains information which single map is on which address. There are tools like winols which can help to identify maps, but you have to investigate if this is correct and what each map does.
With some experience, there are some maps which can be identified easily (things like ignition timing, torque limits etc.), but other values are nearly impossible to detect (DTC cutoff flags for example).
The best way is to have a leaked a2l file from the OEM, then you have all the maps with naming and just need to translate a little bit. But these files are rare and often expensive.

Is a2l the actual name of the file or is there something specific needed from BMW to help create the xdf file?