Okay, we all know the values in the eprom can be from 1-255 the accuracy is in steps of 1 which can either be extreamely acccurate or very sensitive (vague).
I was going through me copy of the 8746 ecm hack document and I ran into the following.
LD263: FDB 65 ; max sync bpw to exit async fuel, 992usec
LD265: FDB 45 ; min sync bpw to enter async fuel, 687usec
LD267: FDB 26 ; injector bias, added to bpw, 396usec
LD269: FDB 786 ; max async bpw, 12msec
LD26B: FDB 45 ; min async bpw, 687usec

The hex location is the LD___. Now I figured the constant multiplier out by simple devision and it turned out to be 15.26 to get the correct usec. My question is this, how did they come up with the 12msec. The value needed to convert is 786! That's huge, way bigger than 255, but it still makes sence in the hack file and if you think about it, 12msec = 12000usec. Help me out on this one guys, It's the only thing hanging me up.

------------------
, Jon (350 TBI!)
91 Red My website

 

16 bit double byte for 16 bit math. Allows 65,535 instead of 255 for an 8 bit single byte.

You'll notice that they are defined as "FDB" vs "FCB". FDB is a 16 bit byte and FCB is an 8 bit. You should also notice that hex address of the labels "LDxxxx" are FDB and increment by 2 instead of the normal 1 for FCBs.


[This message has been edited by Glenn91L98GTA (edited November 29, 2001).]

 

How the hell was I suposed to know that
Thanks

 

Simple, get into Assembly Language Programming. With Source Code you can then not only change the tables, but the actual instructions on how the programming deals with the various sensor readings.

Come to the Dark Side of the Force and discover powers you never imagined.