Hondata

I am very pleased to see this option in 1.1.4.4.

Question though, could we make these values affect the AFR.corrected? It would be neat to see what the ECU is "seeing" via the normal AFR... and what the corrected value really is... via the AFR.corrected. Since the corrected value is just a number anyways and not used for anything, this could be done by an equation that adjusts itself based on values we put into the LAF field.

IE The LAF could lie to the ECU that 2200mv is 14.5 AFR instead of 14.7, so the ECU leans out to 2100mv or what it thinks is 14.7 AFR, in actually the AFR.corrected would be reading ~14.9 AFR, which will yield better fuel economy etc. The AFR.corrected value could just act like feedback/reminder of whats really going on for those that want to play with this field.

Again though, pleased to have access to this.

Steve

Just a note to others using this table, it works backwards to what you might think.

My experience with this table:

--Wrong logic explained--
As in, because 2200mV is equal to 14.7 and 1995 is 15.79, therefore you deduce assuming a linear relationship think that 2162mV is equal to 14.9.

Therefor you might think if you make 2162mv = 14.7 the ECU will cycle around 2162mV... or what it thinks is 14.7... when in actuality is really 14.9.

Well you would be wrong. It works the opposite of that. As in consider this table as at the sensor... and not in the ECU, think of it as you are flashing the sensor output...

--Correct logic explained--
As in you are telling the sensor to send 2200mV for 14.7 AFR or telling it to send 2162mv for 14.7 AFR, this means that the ECU sees 2162mv and references its OWN internal table which is identical to the one above, and looks up 2162mv and sees... oh... I am running 14.9 AFR... lets inject more fuel.

Think of the table like that, and you will see in order to cycle around around 14.9 AFR you must enter 2238 mV, or simply leave it at 2200mv and change the 14.7 to 14.9.

If you change the 14.7 value to a number between 14.5-15.5 the ECU will target those values you enter.

Alot easier then all that math huh?

Just sharing,

Steve

Above results were on 1.1.4.5, I will try this again to see if works the way one might think in 1.1.4.6.

V1.1.4.6 changes:
• Fixed stock wideband voltage / lambda conversion table, which was inverted. This table will be reset back to stock with V1.1.4.6, so if you made changes to this table you will need to make them again.

Thanks,

Steve