Thread: Ostrich 2.0

I quote:



And my question being:



edit2

Also see this:



My daughterboard uses the 27C512 chips.

Well i decided to do some more testing tonight, still had the emulators on the daughterboard, so tried running EmuUtility and Romeditor, and it worked 1st time with the same rom as i tried with TunerPro.

Tried tunerpro again and its working and map tracing and all. This was all on a De ecu, soldered a daughter board in a spare VE ecu tonight, but havent had a chance to plug it in and fire it up yet.

Im wanting to make a test rig on the bench for testing ecu's, ive got spare loom, just need to wire it up to a battery, and fit some injectors, dizzy, tps/maf signals etc, and also a consult plug.

Keep us updated with this useful info!

I find it hard to believe that you killed one of the ostriches. Literally I have one of the first production models and it is still kicking to this day, minus needing a new battery.

I would check your ribbon cable and the ends for any bent pins as I have had problems with the ribbon cable in the past.

You don't need to have everything hooked up to be able to run the ECU on the bench, it just depends if you want to do engine running simulation (which you'll need some way to drive the CAS and blow air through the maf etc etc) or just simple things like connect and download a rom with consult.

If you're just looking to connect with consult to check function and make sure a board is working/installed correctly then you need little more than 12V, Gnd, TX/RX/CLK.

1st thing is to get it so i can run a consult plug on the bench, but ideally i want a engine simulator, prob use a battery drill to turn the cas, have plugs and injectors in a rail, a tps on the trigger of the battery drill, and maybe a small fan to blow over a maf sensor in a smaller diameter pipe.

All seems to be all ok now, same ecu, bin file. Not sure what went on, but will inspect the ribbon cable etc.

I'm gonna buy the Ostrichs at the end of this month. I have no indications it wouldn't work. And my sources are very reliable.

Tried another Sr20ve ecu tonight, and TunerPro would not upload a file that would work. Ended up using EmUtility again, and it loaded the bin 1st time no problems. Opened TunerPro, and it would accept minor changes, but changing too much data caused the ecu to 'hiccup' on update of bin file to emulators.

Also map tracing was very inconsistant.

Uninstalled Tunerpro, and all other signs of it, and reinstalled, and got it working on my DE ecu ok, but map tracing is still a bit hit and miss.

Not sure if this is purely a TunerPro issue, or the emulators, the data certainly seems to be getting messed up somewhere.

Im going to get TunerCode as soon as i can afford it, and looks like Nismotronic may be on the wish list too.

I there any other free software that works well with the Ostrich that can map trace?

Oh, and whoever created Launch Control bin file? Well Done, love it, works a treat

Have you tried "live edit" i'm pretty sure it supports emulators, but ive never tried it !