Or using the fuel temp sensor

 

Are you actually referring to the Hi-Octane Fuel Map here?

 

By front O2 sensor, baro, and temps

 

yes thats what I was referring to.

and i got the answer... the answer is the 3D surface created by your SD RPM VE and SD MAP VE.

 

There is a decent number of corrections that can take place in that AFR select sub. I think several of them are disabled though.

Also, I think the ECU can also select a couple different AFR values outside of that main AFR value. They may be for fault conditions though. It's one of those parts of code where it looks for an offset to a RAM variable and IDA looses the path at that point.

 

the next step to closed loop is changing the AFR swing for catalyst efficiency. Since we no longer have cats in our cars... our closed loop operation should operate much more stable than it does. I asked MrFred to see if he can find out how to reduce the AFR swing and the frequency during cruise.

 

It doesn't loose the path in my disassem. There are one or maybe two indirect RAM calls though.

 

With LC1 analog out I manage a 15.0-16.0 window at cruise, switching rate depends on RPM. This is with instant sample feedback using flash v1.00.

The ECU NBO2 rear signal (pin 76) is actually hooked up to the front O2 sensor keeping ECU happy thinking it's hooked up to a fired up cat.

Havent figured idle yet

 

Is there a way to make IDA track those indirect look ups directly or are you just talking about you going through and figuring out manually which variables it is calling up?

 

I'm sure a script could be written, but I've never tried. To have the script do it wholesale to the entire disassem would be a little tricky because the script would have to trace back to find the array address. It should be very easy to set up a script that can work on individual subroutines where the user can first deduce the array address and then provide it to the script in a query.

Its pretty straightforward to lookup the RAM address manually. The array address can be found either at the start of the subroutine or traced back through higher subroutines. Once you've got the array address just add the offset, and go there.