Slowly tracking down AT transmission retard function and I hit apon an idea of how it works.

My hypothysis is this:
Timing is a function of an interrupt that fires some useconds after the CAS routine. So finding the variable for this timing or how the timing works will lead to the function that is retarding timing.

The timing variable never is directly set as can be seen in the CAS interrupt aka "long sub" routine. Instead it seems to be just set from the start using some kind of "base" timing number which is subtracted everytime the CAS routine takes place. So after a certain point there seems be an interrupt in service to the CAS routine which in turn indirectly freezes the timing variable.

I'm trying to figure out what causes this interrupt in service to the CAS routine. Specifically I'd like to know how the CAS routine is even called, IE the interrupt service mechanism, or if possible how to keep it running such that the routine is in play until -1 timing which seems to be the general retard limit for a lancer.

I'm sure it has something to do with the routine itself but i'm baffled to how. Maybe its just staring me in the face lol.

 

Argh so close yet so far.

So I took a little different approach this morning to figuring out where the hack the ignition coils tie into the ECU. Unfortunately it seems their transistor inputs tie into a programmable logic chip called a e328

Tried finding a datasheet on it but i can't its an 80 pin chip which is essentially a black box to the IO routing and stuff. It could be used as some sort of expansion to IO but its hard to tell.

 

Well thanks to last attempts complete failure i went back to the CAS routine to discover that it seems to have a sort of ignition coil charge variable which it sets. It also seems to have some kind of reset to the timer status 2a and 2b which i need to read more on.

ATU-II stuff is large and complex