TTP Engineering

iTrader: (465)

What clutch are you using?

tephra

iTrader: (6)

yeah if you go through the ROM there is another 2 or 3 ign tables which arn't defined in EcuFlash XML's.

Actually the whole ign routine is very complex, not just a case of selecting the advance from a map... I just don't have the time (or the patience) to document it properly.

For our purposes playing with the 1/3 ign tables is "good enough".

However it would be nice to find out why ppl like allupo (sp?) wern't getting the timing advance the requested..

JohnBradley

iTrader: (30)

Went from a totally worn out and broken stocker to an Exedy Twin HD now. Thanx for the insight David.

RazorLab

iTrader: (8)

cruise map portions in non-cruise areas? I'm not following.. ahha

lemmonhead

ya people have always said map 2 is for normal, #1 for cold start, #3 for problems.
I never bought into this and from my experience made more sense that 1 map is for cold start, then 1 base map and the other is the additional added when no problems are found by the ecu.
I mathematically thought I soved it but it eventually did not work,
but I think map 2 is the base map, then the ECU does its thing and if it determines its ok it adds #1 map to the #2 map in a mathematicaly way, slowly ramping up.

JohnBradley

iTrader: (30)

The map that you refer to you I was calling the cruise map...sorry I spose I should have defined the terms. Non Cruise areas would be last load column the car sees, for instance lets say 270ish. Its an odd concept that probably doesnt work, but one of the 99 mistakes I intend to make on the way to 100% coming to terms with this concept.

Lemmonhead that is covered as part of the MIVEC advance/retard based on load relative to TPS/Load/etc. This is actually different just in case that wasnt clear before.

RazorLab

iTrader: (8)

oh I understand now, editing the low det ign advance table I was referring to by adding timing in the non-cruise areas.

Yea I suppose so. I haven't even messed around with the table yet to really know though.

Jorge T

iTrader: (18)

Ok I'm lazy you're right I did not look..I did now, but if load log is close to 2byte looks like he is in closed loop timing advance. I've seen timing in mine advace up to 40* at 40% load . There must be a table for limits on this somewhere.

JohnBradley

iTrader: (30)

All 3 of those values are 2 byte. The car is also running in open loop (TPS and Load table altered). The tables have been mentioned but this isnt so much about if they're there or not but what they can do for us

TTP Engineering

iTrader: (465)

If you think you have issues with the twin HD, don't try a triple carbon on steel. 36 counts in vacuum anyone?

Jorge T

iTrader: (18)

In non computer controlled cars, vacuum advance was used to extend the burn cycle even longer than what was set by the mechanical advance(in our case timing maps) so that all the heat energy gave more more power yield per measure of fuel and more mpg. It may be the same concept on our evos but computer controlled

GTLocke13

iTrader: (1)

I thought vacuum advance was to change the timing based on RPM and load, i.e. the same function our maps perform.

Has anyone tried to pinpoint where timing advance is generated in the ECU (I assume the MUT request for logging points to this) and actually derive the equation from the assembly code? I know it would be a royal PITA, but it would answer all of these questions.

JohnBradley

iTrader: (30)

I am glad that this has generated some interest. Sooner or later it will get disassembled, but the vacuum advance allusion (while technically accurate) isnt what I am curious about this doing. It might serve a similar function to that as well but thats not what I am concerned with

smartbomb

I have noticed this myself, I see more timing than is in that load cell, especialy when logging at part throttle, lighter loads.

al\lupo

Yep, I'm just investigating and found this thread
I will try a less aggressive MIVEC next.

Btw, with low det cruise map do you mean this?