The Project Pad

wanna burn a chip for my 900 turbo? LOL I want to put a 2.1L head and intake manifold on plus a TD04 off of a 9000. I only say that because of the SS you posted.

What year 900T? Or more specifically, first-gen or second?

For a second-gen car (with Trionic engine management) you don't really "burn a chip", the data is in flash memory. And there's a whole web community dedicated to reprogramming Trionic... take a look at http://ecuproject.com/index.html.

If it's a first-gen car with LH engine management, there are a few people out there doing chips for them that I can give you info on if you want. But that system is pretty limited - if you want crazy power (and don't mind replacing transmissions constantly ), you might have to upgrade the engine to Trionic. But that's not a small task.

Its a 92 (pre-gm). I dont really follow Saab all that much but I know my way around the car. It has the APC unit if that matters

To read and write chips i use a willem GQ4X eprom programmer.
http://www.mcumall.com/comersus/store/comersus_viewItem.asp?idProduct=4312
There's a bunch of adapters they sell for this programmer too. i have the adapter to read the PLCC44 chip found in 0BD2 MK3 VW ECU's and the adapter to read PSOP44 chips from MK4 ME7 ECU's too. this chip burner comes with software and everything to read and write chips. this thing supports like 10,000 different chip if i recall correctly. i've even read and reprogrammed the mileage chips out of instrument clusters with this programmer.

another option for doing live tuning on this ECU is to get a moates ostrich 2 ROM emulator.
http://www.moates.net/ostrich-20-the-new-breed-p-169.html?cPath=95
use this emulator with tunerproRT tuning software and you can live tune and data trace whats doing what in the binary. you need to find or create a definition file for the version of the ECU your working with and that versions chip read out. i have started creating several XDF definition file for tunerpro but i feel what i have found isnt concrete enough to put it out there yet. im afraid people will be blowing up cars because i improperly labeled a map.

i use both of these devices to interface with my M2.3.2 ECU along with a VAG COM cable and VAG COM to watch the measuring blocks and get a rough idea of how the engine is reacting to the tuning.

If you want to start tracking maps down i would suggest either buying or hunting up a cracked copy of winOLS. thats a great piece of software and it will attempt to do some of the work for you and hunt for maps plus with the full version it will correct the checksum.

vwnut8392 wrote:To read and write chips i use a willem GQ4X eprom programmer.
http://www.mcumall.com/comersus/store/comersus_viewItem.asp?idProduct=4312
There's a bunch of adapters they sell for this programmer too. i have the adapter to read the PLCC44 chip found in 0BD2 MK3 VW ECU's and the adapter to read PSOP44 chips from MK4 ME7 ECU's too. this chip burner comes with software and everything to read and write chips. this thing supports like 10,000 different chip if i recall correctly. i've even read and reprogrammed the mileage chips out of instrument clusters with this programmer.

Wow... that's a nice unit and pretty reasonably priced!

AngryTaco wrote:Its a 92 (pre-gm). I dont really follow Saab all that much but I know my way around the car. It has the APC unit if that matters

Yup... that's a first-gen 900! I owned 4 of those and loved them all... some more than others.

Rather than drag this thread way off topic, shoot me a PM and I'll send you my contact info... I can point you to a few resources you might find useful.

elaw wrote:Wow... that's a nice unit and pretty reasonably priced!

Its a great programmer, has never ever let me down! my friend had an old school willem that was just a bare board eprom programmer back in the day and even being a bare board it was indestructable so i figured it was the right one to get. i had an intronix pocket programmer II before this one and that thing lasted almost 15 years. i picked up second hand with an issue and found a blown out cap in it, spent a few bucks at radio shack and got a good solid 5 years out of it before it gave up the ghost finally.

ive been trying to figure out the constants for the maps and their mathematical equations to make them into real world values. can anyone give any input on these? sure could use some help on this one.

I know 3A is the RPM scale and its equations is simply multiplied by 40.
3F is the load scale and i have no idea what its equation is.
There's 38, 37, 36, 2E and 4B so far and i have no idea what they do.

I think this line of code is the 4A0 907 551C ECU has something to do with the constants.


anyone have any input on these scales? i'd like to get my tuner pro XDF's all sorted out and i'll get them posted up here.

When you say load, are you referring to MAF readings? MAP?

AngryTaco wrote:When you say load, are you referring to MAF readings? MAP?

whichever the scale is on other half of the ignition table. i know the constant is 3F as for how to calculate it and plug it into tuner pro i cant seem to figure it out.

its been a while since i posted in this thread but and i think its due for an update. first the rev limiter for the 551AA and 551B ECU's. i've been working another fellow user on here and my cousin to figure out the conversion factor for the rev limiter and an expression that works properly in tuner proRT. we have successfully achieved this for the 551AA and 551B ECU's. here's the info on adding the rev limiter scalar along with another scalar for the RPM limit that relates to the RPM exceeded fault code.

First the rev limiter in the 551AA the hex offset for it is 0x8373. This is a 16bit value.
The expression for the scalar in tuner pro is exactly this.

when setting up your scalar in tuner pro make sure you set your size to 8 bit on the general tab or it will not show up right.

Now for the RPM limit that relates to the fault code. its hex offset is 0X8375 and it is 16bit as well.
The expression used for this is just a touch different than the one used for the rev limiter.

Once again dont forget when setting up the scalar to make the size 8bit instead of 16bit or the value will not show up right.

For the 551C and up ECU's the rev limiter and the fault limiter is calculated in a completely different way than the eariler 551AA and 551B ECU's. im working on figuring this out as well and i will post my progress once i know it works. lastly i have been working the injector scalar as well. i feel some good progress has been made on this too. My cousin with his programming background is going to write a small program for us that you will plug in all of the necessary data and it will spit out the KRKTE. at that point you plug the KRKTE value into the expressions and multiply it by X and you will get your injector on time. X is the hex value in the binary by way. so everyone enjoy and i'll keep posting info as it comes along. enjoy!

I decided to attach the 551AA timing/fuel XDF for tuner pro for you guys to check out. i have the injector scalar setup in there but im not sure it's right. so use that scalar with caution. This XDF will automatically correct the checksum of the timing/fuel file as well so it can be used to do live tuning with tuner proRT and a moates ostrich too.

Thanks for all of this good info!

Here is some interesting reading regarding datalogging with the AAN ecu:
http://www.s2forum.com/forum/showthread.php?t=48400

Here is a stock boost chip file that has the checksum routine disabled. This is the boost chip for the 4A0 907 551AA ECU. it will work in any other version ECU of the S4/S6 ECU as well. With this boost chip file you can live tune using tunerproRT and a moates ostrich emulator without having to worry about checksum errors. enjoy and more will come as time goes.

Here are some high resolution pictures of a stock AAN ECU with a chip socket installed on the boost side and a boostbutton.com latch adapter board installed on the boost side.

These are links to my google drive so you can get the full resolution images. I suggest you download them to your computer so you can view them better too.
https://drive.google.com/file/d/0B8k41D1CY71wdkFGbi10cDQxbFk/view?usp=sharing
https://drive.google.com/file/d/0B8k41D1CY71wZjdxQVZKTXlrd0E/view?usp=sharing
https://drive.google.com/file/d/0B8k41D1CY71wSkI5djhVY1JSbHM/view?usp=sharing
https://drive.google.com/file/d/0B8k41D1CY71wNm5UeHViMkswLVE/view?usp=sharing

Well here's another update on the 551AA XDF for you guys. in this one the rev limiter is confirmed working and in the boost XDF the patch does disable the checksum so you can live tune on the boost side. also the timing/fuel XDF auto corrects the checksum as well so now you can safely tune on both side of the ECU with out worries of checksum error fault codes.

attached is the latest 551AA XDF's for timing /fuel and boost boards with the stock bin files for both sides.

the injector scalar is in there but i havnt tested it yet because my wideband isnt in my S6.

Here's a video confirming that the rev limiter adjustment works in my 551AA XDF.

[youtube]https://www.youtube.com/watch?v=rHKI28Cx0QU[/youtube]


Have fun guys and hopefully more to come in time!

This is great info. Thanks for sharing all of your hard work!

With the Ostrich and Tunerpro one thing that makes me nervous about disabling the checksum is that often times Tunerpro will report the file was uploaded correctly but the check engine light will come on with the corrupt memory code. It will sometimes take me several attempts to upload the file to get the check engine light to go out. So if you disable the checksum then all you can do is trust Tunerpro. Do you see this as an issue with the boost chip?

You mean thanks for sharing someone else's hard work?

loxxrider wrote:You mean thanks for sharing someone else's hard work?

and who's hard work would it be other than my own? dimitri and mineha definitely arent feeding me information if thats what your getting at. those guys will take what they know to the grave before they let the public have it.

GTJeff wrote:This is great info. Thanks for sharing all of your hard work!

With the Ostrich and Tunerpro one thing that makes me nervous about disabling the checksum is that often times Tunerpro will report the file was uploaded correctly but the check engine light will come on with the corrupt memory code. It will sometimes take me several attempts to upload the file to get the check engine light to go out. So if you disable the checksum then all you can do is trust Tunerpro. Do you see this as an issue with the boost chip?

you wont ever get that fault code, i've been running my car around for 3 days with the emulator on the boost side with the checksum disabled and never got the fault a single time and that includes making changes to the mapping and everything. the car will run still with the fault in there anyhow, all the fault is there for is to tell you there is a problem with the eprom's or the ECU.

A question regarding the M2.3.2 maps, that are used for fuel-enrichment on WOT and boost events.
Can please anybody bring some light into this?

What I understood up to now is, that the 16x16 fuel map (at 0x8E13 on the 551B ECU with SW 358361) only has en effect at partial load conditions.
In an WOT event when the turbocharger produces boost, there must be another enrichment function.
Which map is responsible for boost enrichment?

I found all the maps of the Audi_RS2_8A0907551B_0261203478_1267358361 defined inthe map table, and compared them with another tuned map.
From my point of view, there are some maps in question that could be related to this enrichment function:
0x8CD9 4x5 2E vs 3A (3A is RPM, what is the descriptor 2E btw?)
0X9D1C 6x1 3A
0x9D2A 6x1 3A
0X9D5C 6x6 2E vs 3A

No one a clue?

you want to go to S2forum and find the same thread i started there. i stopped working on this project a while back.