I haven't datalogged in years now...
What is the interest in posts from five years ago?
I guess I should try one of these days to see if it still works...

The FN8000, FN060 and FN061 locations suggested here are correct... FN8000 type=table address=e994 rows=6 cols=10 size=1 unsigned BP=8 FN060 type=function address=e802 rows=8 xsize=2 xbp=15 unsigned ysize=2 ybp=8 unsigned FN061 type=function address=e822 rows=10 xsize=2 xbp=12 unsigned ysize=2 ybp=8...

Just to clarify, HP_CIDSEL = 1 means that a cam position sensor is used for cylinder identification (it uses a hall effect sensor, which is completely separate from the VRS). HP_CIDSEL does not imply either Hall effect nor VRS - just that there is a sensor there. The type is selected with the other...

Anyone have information on these catch codes?
I have a box full of junk-yard EEC's I got for little dough...

LC8
8NC
8KF
8MZ
Z9A
9 (Yes - just a 9!)
S1S2
A2D2
J2T1
D2D
A4L0
L4W0
E4H1
Z4D0
A4J2
JJX0

Here is a code snippet from the A9L. I checked against the cbaze (t4m0), and it is basically the same (slight difference in how the filtered TP value is done)... The first part ensure that the TP is in range. Failure management is used if not. The second part updates the relative close throttle TP v...

Looks like CalCon is displaying the ECT value for BOTH ACT and ECT for my attempts with an A9P (A9M) logging... The values are always the same and appropriate for ECT. Interestingly enough when I use the 1.20b2 CalCon (with the 1.20b3 payload), I get different values as expected, which seem to be th...

MYTKWIK wrote:Ray=Raymond and yes I am refering to Alex Smith.

I guess I am an EEC Geek.

My 1.20 experience is limited. There are datalog issues with the A9P, where my current application lies.

DA1 decode is just about where I want them, and I hope that will make it to the released 1.20.

Alex