David - ditto, if useful a STI 1 map to download ( as long as I get a copy to play with as well ! ).

I'll be at the rr day at Well Lane, this might be a good time to do this.... ?

Paul Houbart

 

David,

If you are going to do download at the RR day make sure you have mains power or good battery life.

My PC takes about 1 1/4 hours to do a full 'DUMP' and has been know to cop out just before it finishes if running on battery power.

 

got a 12v to 240v invertor if this laptop wont run off 12v... Do we need to do a full dump, cant we just dump 256k?

David

 

Over an hour for a dump , sounds painful

 

Dump 8000 To FFFF to get all the data, this is what I calss as a 'FULL' dump, the rest is blank.

 

I can bring along a laptop as well, the battery ain't up to more than 40 minutes of hard work, but if an inverter will run it, then it should do the job.

Any help at all ?

 

Scott, I think you're application is rather slow. I know you had reliability problems, but I think the last map I did took about 35 minutes.

Paul

 

I think its very dependant on the capability of the RS232 port, as you know one PC I used hardly worked at all.

The one I currently have is O.K but setting the Labview code timings any less produces too many error reads.

 

Alternatively, if someone wants to send me a copy of the relevant software, I could download the map myself. I'm fairly computer savvy, although advice on how to wire up to the ECU would be required.

Ah, the old days of programming in HEX - you lot with your assemblers/compilers/intepreters, in my day you programmed with a rock ! And were glad of it, as well.....

 

So as far as std ecu's go, what would be the best, un-modified ecu, for a particular MY range. ie. What would be the best std ecu for my 92 legacy. I had previously tried a 94 WRX ecu, and it was crap.
Is there any easy way to re-program to remove the speed limiter too. I may be able to get hold of an RA ecu, which I do know are good, and im sure that Andy F will confirm this.

 

stevie... pass but we can program any to any year of std code..

BoxerFLat4... not that easy as you need a little box of tricks that we have...

I now have a toshiba laptop which was borrowed long term hopefully (from work )

not the quickest but just rebuilding it at the moment...

David

 

The P1 and STi have larger values in the correction maps than the MY99/00 UK ECUs. The MY00 ECU has a differences between the high and low octane ignition and fuel knock correction maps. The MY99 and STi 5/6 and P1 do not.

AFAIK the knock sensitivity on the P1 and STi 5/6 are all the same as are all the fuel and timing maps. Maybe there are other areas in the P1 code that are different, but they seem identical from all I have heard and seen.

I don't have massive faith in the UK ECUs ability to knock correct when you run high boost on a big turbo. Mine seems to register trivial knock correction (even with OEM headers) when there is good going det. I still do get little splashes of transient det, might need to sort the cam cover ventilation out - the crankshaft is already going to the can.

 

David -

Any chance of some details on this "black box" you've got ? Fancy doing some micro processor programming, re the other thread, considering getting Bascom, but need to brush up on my soldering techniques.

E-mail me offline if necassary, like to contribute something to the pre 97 cars if possible.

 

Speed Limiter can be removed as it just means changing 3 HEX values. Most Jap tuning Maps have this set to 200mph, it will however require the adaptor board and EPROMS to be plugged in as you cannot change the on board settings on a Standard Pre97 ECU.

The reason the WRX ECU was crap in the Legacy is probably down the the Turbo being smaller and the WRX ECU will have a duty cycle mapped for the TD05.

Paul (PAVLOS) runs an early Legacy and has remapped it using the Prodrive/WRX95 style map with adjusted solenoid duty cycles.