club.liberty.asn.au

Howdy all.

I have recently picked up a 2002 Rev D b4 and was hoping to be able to tinker with the ECU but it is proving harder than first thought. I can't seem to find an ECU def so that I can download/edit/flash the ECU. I have briefly searched and found rumors of these elusive files but can't actually track them down. Does anyone have the ECU defs handy? Particulary A4SH701H...

I don't think there are many places here in NZ that do ECUtek for these anymore :/. Any other tuning options that anyone knows about?

Thanks!

Start with RomRaider forums mate

The definition (xml) for the TT roms (hex) are not readily avaiable.Romraider has the DTC only.
The definitions that are around have been generated via XMLwrite which was hacked/ripped from EcuTEK.
XMLwrite can generate the xml definitions for ECUEdit/Rommraider-Enginuity/ECUFlash software.
A few have been posted in openecu.org
ie:http://forums.openecu.org/viewtopic.php?f=54&t=2982.
XMLwrite was made available on the net via tinyrex some years ago but EcuTEK forced it to be deleted.
It was also packed with the Ecuedit software but that has been stopped as well.

I have A4SH701H and a few JDM ones if you're still chasing it.

I'm after the definition (ignition, fueling, & wastegate) tables for my JDM B4.

Only ever seen 3 or 4 partial or full definitions. I believe 701H was one, let me dig threw some old emails

Any XMLs or Hexs you guys might have for 701H would be awesome...

logan @ randellonline.com if you have anything.

My $20 VAG link cable can't read the ECU but it can data log and reset. Will be getting my hands on a tactrix in the near future I think.

KiDo_Tuning wrote:Only ever seen 3 or 4 partial or full definitions. I believe 701H was one, let me dig threw some old emails

Would be great if you can find anything relevant, still very keen for an open-source tuneup.

I found my full def for A4SHC00H and A4SH701H looks like I did a tune in one at some stage for fuel and timing but no boost, now I need to find the definition file I wrote which I suspect is somewhere amongst the 7 terrabytes on my home server

Yep any XML defs or hexs would be sweet

Also looks like my cheap cable won't talk via ECU flash / ECU explorer at all. All I get is the denso bootstrap cmd about 5 times then it errors out.

Thats with the green connectors connected and ECU flash 1.29a with the latest FTDI driver.

I can data log with the cable though, heh.

GorGasmB4 wrote:Yep any XML defs or hexs would be sweet

Also looks like my cheap cable won't talk via ECU flash / ECU explorer at all. All I get is the denso bootstrap cmd about 5 times then it errors out.

Thats with the green connectors connected and ECU flash 1.29a with the latest FTDI driver.

I can data log with the cable though, heh.

You need to start the download about 2 seconds after the ignition goes to the ON position They are worse than a bug eye WRX

I actually got the stock tune out of a 3L 01 Outback easier than most of the B4's come out

So I have come across quite a few hex and xml files now and some of them appear to start working in romraider/ecuflash/enguinuity but once the program has created/populated tables it says ready... but there are no tables to edit :/

Opened an 04 GT hex/xml pair and it works fine. Also using the default defs I can see the DTC codes and stuff.

So it looks like something funny is going on with the Roms/XMLs that I have aquired so far. Anyone else come across this happening?

The XML are generated to a specific size for use in the various programs.
An XML for Rommraider(previously called Enginuity) will not work in EcuFlash or EcuEdit
In the case of EcuEdit the hex file (If the ECU rom was obtained via EcuFlash) needs to be resized also.
Some of the XMLs I have used for the TT are only compatible with the older versions of the programs.