Didn't work with Chrome, IE9 or Firefox... Firefox just downloads the error HTML page instead of the XDF when selecting Save Link As. IIS reports HTTP Error 404 - File or directory not found.

Dan
'91 928GT S/C 475hp/460lb.ft

 

Oops. I guess the Rennlist server doesn't like the extension.

Rename the XDF definitions from ".txt" to ".xdf" after downloading.

 

Email sent.. and your xdf links are still broken (link text changed but not the URL)

I left my eprom reader set for 27c256 as I was being lazy and didn't fancy changing the fiddly dip switches for 27c128 (which is what EZK chips are IIRC) - but shouldn't make any difference.

Also - I can recommend grabbing some Atmel AT29C256 eeproms to save all the hassle of UV erasing.

 

Got it, thanks! Links fixed.

FWIW, my '88 has a 92861812411 2227355520 EZK chip.
Code changed, but maps are identical to the '89.

 

OMG, nothing is ever this easy!
I guess I'm gunshy because nothing (but a ST1) ever worked right with LH2.2.

I plugged in the Ostrich 2.0 28 pin EPROM connector and strung it out of the case (loose fitting the lid).
I loaded the '88 EZK image via TP5 RT and it fired right up! Yay!

 

I sense money coming out of my wallet. Once the spinning stops maybe we could convince this company to offer some kind of group buy?

Have you tried the Ostrich on a S3?

 

I bought the Ostrich for S3 tuning, but could never get it to work correctly.
I admire the ST1 for it being able to work properly with S3 brains.


AFAIK, the Ostrich 2 has trouble with 24 pin EPROMs. It has a setting for it, but it didn't work for me.
I used the socket booster, but it still didn't work. OK, it worked, kind of, with the EZ-F, but not always.
LH2.2 was a disaster. It would occasionally work, but mostly it would blank out and flood the engine.

LH2.3 and EZ-K are 28 pin. Seems to work great with those.


BTW, you can run multiple instances of Tunerpro RT...
I could get another Ostrich 2 and tune both computers at once.



After looking at some Volvo EZK XDFs, I'm thinking table 1100 may be a knock sensor sensitivity table.

 

Subscribed, tons of info in this thread (and much more to come): thanks Ken (and all other who posts here)!

And I hope one day you can also put your magic touch onto the GTS based EZK and LH bin files (lets see/read what can of worms that wish opens up... ).

 

25 years ago I was burning a pile of 2716 every day and had a Romulator, which cost about $350 as I recall. Very basic circuit according to the EE types I worked with, static ram and some buffer chips, too bad I didn't keep it.

Did a socket extender work with the S3, that is close to the minimum practical situation rather than messing with the factory socket and opening the case.

OTOH LH2.2 is kind of done, so not a lot of need for rapid chip swaps.

Back of my mind I keep wondering if at some point it won't become practical to use a reprogrammed LH2.3 in the early cars? Or maybe just the EZ-K for the knock detection with a nice reliable LH2.2 FI?

 

More color maps, please.

That part I get.

Well, not really, but they look nice.

Good luck with the project!
Huge implications for the S4.

 

All this sorcery and witchcraft confuses me...although I don't understand it, still a great read!

 

Subscribed! Thanks for sharing Ken!

 

I was able to do some quick address tracing and emulation using the Ostrich.

I am able to see what cell the EZ is accessing in a table (turns yellow).

While emulating (instant changes from screen), my netbook died (old battery) and the car kept running, reverting to the stored image.


XDFs are changed to reflect new observations.

Cat mode is the first set of tables.

'88-up use addresses 4000-7FFF. (You can change the offset in the XDF header.)
'87 only uses addresses 0000-1FFF.

Added more constants. I think they are correct.

I tried 0 and 20° for the 'off idle' retard, that works.
It eases the transition from idle to cruise.
I left it at zero for instant response.

I reduced the knock increment to 1.9°.

 

Im glad there are guys like you in the world Ken. I have no clue what all that (x'x and O's...numbers..etc) means but It appears to be a break out box and tuning capability via the Ostrich and tunerPro?
Is that the idea of it?

pretty cool!

 

Tony - pretty much, except no breakout box.

The Ostrich is like the PEM for the SharkTuner.
Load it up and it will keep the EPROM image for years.
I'm going to get another one for the LH.


The only thing missing now is the (serial) data output from the EZ and LH.
Tunerpro has a whole 'nuther side where you can set up data channels for a 'dashboard'.
It would be cool if I could figure out how to interface the outputs of the EZ and LH for this.

There's a fellow that figured out how to do some logging with LH2.4 (Volvo) using a VAG-COM cable, so it may be possible.
I think he may have changed the Porsche proprietary data format into a more standard one.
I will take a look at his code at some point.
http://www.jetronic.info/wiki/tiki-i...%20Datalogging