Audi TT Forum banner
Cancel
Create thread New Garage Forums

P1297 Check Engine Light ...

Jump to Latest
81 - 100 of 113 Posts
#81 ·
If you make any changes you must generate the check-sum otherwise it'll start the engine once then brick the ecu... and you'll either need to bench flash or leave the battery disconnected for a certain period of time..

There's some guys on nefmoto who have some tools which find the code words and work out the tables etc due the xdf
 
Discussion starter · #82 ·
Good to know. And interesting... I feel like working out my XDF will take me a year to figure out...

So on this thread 04TT 225 BEA 8N0906018CJ a guy has the same engine and says he got a similar but not equal damos (same as XDF?) from another guy named TTQS. Did some searching and think I found it here Basic ME7 Tuning How To

But it's an OLS file

Can someone explain OLS to me? I can't use it in tunerpro. Google is making me think it's like an encrypted bin file so not what I need? I also see it's a BAM and not BEA engine
 
#83 · (Edited)
It's used with winols, the locations are the same place.. but it sounds like a mission.

You might get a demo version...

If it isn't a daily driver, I would try and put on a BAM map if it is WideBand with VVT 225 or an APX map if narrowband... if it doesn't work try and put the original map back on

The QS BFV has a different structure maybe try that to view your bin ?
 
Discussion starter · #84 ·
StuartDB said:
It's used with winols, the locations are the same place.. but it sounds like a mission.

You might get a demo version...

If it isn't a daily driver, I would try and put on a BAM map if it is WideBand with VVT 225 or an APX map if narrowband... if it doesn't work try and put the original map back on

The QS BFV has a different structure maybe try that to view your bin ?
Click to expand...
Oooh I like those ideas. I will hold off for now on the WinOLS, it does sound like a mission and I'd rather not have to pay for the software

I will try to find a BFV XDF to view the .bin with

Also uploading a stock BAM map is smart... I have a BEA which is just the North American version of the BAM. From what I've read the only difference were emissions-related to suit North American EPA regulations. Unfortunately it is my daily driver. Is there a risk that I will 'brick' the ECU and the car won't run? And it won't even allow me to put my BEA map back on it once it's bricked?
And what about this original BAM bin... it says software version 005, not sure what that means. Using my VCDS it says my current software is version 001

2004 Audi TT BAM 1.8T 225, 8N0 906 018 CG software version 0005

2004 Audi TT BAM 1.8T 225, 8N0 906 018 CG software version 0005
nefariousmotorsports.com
or there's this one

Audi TT 1.8t BAM 225HP 8N0906018CG 0261208268 1037369579

Audi TT 1.8t BAM 225HP 8N0906018CG 0261208268 1037369579
nefariousmotorsports.com
 
#85 ·
No idea to the answer, but there's definitely some emission changes also maybe elevation changes.


I have a spare ecu and power supply so am a little less fearful if these things. I know they changed around the organisation of some of the me7.5 VAG ECUs .. but I don't know if a BAM maps works on a BFV ECU and vice versa. I have only bricked an ECU once and that was because I didn't update the checksum, and then I wrote a map car started perfectly well and at the end of the engine start, the car worked fine until a restart. Then nothing just turned over and couldn't read or write a map, you're supposed to 'bench flash' the original map back on.. its where you put a wire onto one of the pins.. but leaving it disconnected for a period of time also allowed it to be re-written over again.

If I get a chance over the next couple of days I will try and write your BEA map onto my spare ECU.. if it works... it doesn't mean it will work the other way too.
 
Discussion starter · #87 ·
StuartDB said:
No idea to the answer, but there's definitely some emission changes also maybe elevation changes.


I have a spare ecu and power supply so am a little less fearful if these things. I know they changed around the organisation of some of the me7.5 VAG ECUs .. but I don't know if a BAM maps works on a BFV ECU and vice versa. I have only bricked an ECU once and that was because I didn't update the checksum, and then I wrote a map car started perfectly well and at the end of the engine start, the car worked fine until a restart. Then nothing just turned over and couldn't read or write a map, you're supposed to 'bench flash' the original map back on.. its where you put a wire onto one of the pins.. but leaving it disconnected for a period of time also allowed it to be re-written over again.

If I get a chance over the next couple of days I will try and write your BEA map onto my spare ECU.. if it works... it doesn't mean it will work the other way too.
Click to expand...

Did you get around to writing the BEA map to your spare ECU?
 
Discussion starter · #89 ·
So I wrote a stock engine flash to my car (this one 04TT 225 BEA 8N0906018CJ) and there's no difference. Same original 2 engine codes about running lean and pressure drop between turbo and throttle valve. Plus the new one about 'control module programming not finished.' So I guess all was for naught.

So I guess it's not the MAP sensor. Back to the drawing board

On an unrelated note my car's fan seems to run 100% of the time now... going to rewrite the original flash and see if that fixes anything
 
#91 ·
The BAM XDF, doesn't have the same configuration as your BEA ECU... I manually added a table reference to a test file to demonstrate the LDRXN (max load) table was in a different MAP address in your BEA ECU.
If you're changing the bin file, you're going to need to either add the tunerpro checksum plugin or use the nefarious ms-dos executables before updating the map and writing it back.

It might be worth posing a question regarding simply putting a BAM map on a BEA ECU in nefariousmotorsports they are both ME7.5 aren't they. I don't believe REVO have different maps for AMK / BAM / BFV (they are all wideband 7.5 with VVT)
 
Discussion starter · #92 ·
StuartDB said:
The BAM XDF, doesn't have the same configuration as your BEA ECU... I manually added a table reference to a test file to demonstrate the LDRXN (max load) table was in a different MAP address in your BEA ECU.
If you're changing the bin file, you're going to need to either add the tunerpro checksum plugin or use the nefarious ms-dos executables before updating the map and writing it back.

It might be worth posing a question regarding simply putting a BAM map on a BEA ECU in nefariousmotorsports they are both ME7.5 aren't they. I don't believe REVO have different maps for AMK / BAM / BFV (they are all wideband 7.5 with VVT)
Click to expand...
Oh I thought maybe with that XDF I could still try to 'control+F' the string that needs to be changed from 2D to 0D.

I already asked about putting the BAM map on a BEA ECU. They are both ME7.5. Got no response. Also got no response when looking for the BEA XDF
 
#93 ·
All the XDF does is show the values at addresses with a sensible code and description and sometimes instructions (eg make 0 for decat) and performs calculations on them to show you something sensible, so if the value is milliseconds in the map it might be divided by a 1000 to show you seconds or similar.

Have you found a BFV XDF ?
 
Discussion starter · #95 ·
Can't find one. Here's maybe an incomplete one: XDF to suit 240 bfv file

And yeah not surprising that I can't just put a BFV on a BEA or BAM. Though BAM-BEA might be different since it's about the same engine. Not worth checking as I don't think it will solve any of my issues. As far as tuning goes, all I'd like at this point is to be able to modify my .bin file just enough to erase the 'control module programming not finished' code

My fan issue seemed to magically go away. Still have the original issues of lean code and pressure drop. I bought a new coolant temp sensor and o-rings for the injectors even though I know they're fine. Could try replacing the cat but that's expensive and definitely isn't causing the pressure drop code. Who knows
 
#96 ·
Are you sure you have the right map sensor? Has it been replaced at some point? I started my car after some modifications and accidently used my 4bar map sensor without the corresponding map updates and it had the same error.
 
Discussion starter · #97 ·
StuartDB said:
Are you sure you have the right map sensor? Has it been replaced at some point? I started my car after some modifications and accidently used my 4bar map sensor without the corresponding map updates and it had the same error.
Click to expand...
I've only owned the car 10 months now and don't have a way to ask the previous owner if it was replaced. I have a picture I put in on page 3 of this post and it looks like it has the original audi logo so I believe it's stock
 
Discussion starter · #100 ·
Figured I'd give an update since I've been busy and am about to be gone for 3 weeks for work:

Changed the MAP sensor - no change
Changed the engine coolant temperature sensor - no change to the CELs. I do notice that the temp gauge takes much longer to warm all the way up. I had a feeling my thermostat is bad and stuck open. I will order one and fix it when I get back. Though I still think that's a wholly unrelated problem

When I get back I'm also going to change the O-rings on the fuel injectors since it's very cheap even though I don't think that's the problem. I've now been intermittently getting a 4th CEL, saying my idle RPM is sometimes too high... again making me think an air leak. Though I've smoke tested this thing many times with no results I guess I can try again
 
81 - 100 of 113 Posts
About this Discussion
112 Replies
9 Participants
Last post:
doodlestj
Audi TT Forum
posts
3.7M
members
90K
Since
2002
A forum community dedicated to Audi TT owners and enthusiasts. Come join the discussion about performance, modifications, classifieds, troubleshooting, maintenance, and more!
Full Forum Listing
Explore Our Forums
TT Forum - Mk1 TT (8N) TT Forum - Mk2 TT (8J) Off Topic TT Events TT Forum - Mk3 TT (8S)