[Diy_efi] newbie - rom tuning questions

[Steve Ravet]

> -----Original Message-----
> From: diy_efi-bounces at diy-efi.org 
> [mailto:diy_efi-bounces at diy-efi.org] On Behalf Of Aaron Bunch
> Sent: Monday, September 12, 2005 8:28 PM
> To: diy_efi at diy-efi.org
> Subject: [Diy_efi] newbie - rom tuning questions
> 
> Hi. I am a newbie here (again). I joined a few years
> ago when I was looking for a bosch O2 sensor. Sorry I
> never contributed much to the list.
> 
> So here I am again, looking for help. I have Techtom's
> rom tuning software (called Mighty Map). Basically its
> is a powerful Hex decimal editor program that allows
> me to (sorta) easily make sense of the 8000 whatever
> lines of code that make up a rom for a Toyota.
> 
> Techtom makes a daughterboard or Rom Board that
> installed where the OEM 64 pin CPU/rom chip went. The
> rom board houses the original CPU/rom a 27C256 E-prom
> and a sort of logic gate (I have almost no background
> in this stuff) that works like a change of address
> form for the data coming and going out of the oem
> CPU/rom. The logic gate (also called a scramble chip)
> makes the ECU look onfor the programable E-prom
> fuel/timing maos as well ar rev limit, boost cut, etc.
> 
> Anyway, that is all well and good but what is lacking
> is a map trace function that would allow me to see in
> real time exactly what cell the ECU is using to run
> the car. So far I have been very successful tuning by
> trial and error..but I am running into several road
> blocks that would easilty be fixed by a map trace
> feature (I think).

I have no idea if there is something specific to your application (what
is it, by the way?) but if you can log scan tool data then you may be
able to put something together.  Look at the map, rpm, and correction
values from the log and you should be able to build a spreadsheet that
shows the corrections the computer is having to apply to your existing
map to maintain stoich.

--steve