Evo anti-lag ECU disassembly
Yes there is a table that hasnt been defined yet. BarryC found it for his VIII, but I dont think anyone has started looking for the IX as of yet. I think he found that the value could only be increased on his an additional -5*...from -5 to -10. It may well be maxxed as far what it will allow.
this is for the evo 7 and 8
<table name="Timing Retard Limit" category="Timing" address="173f" type="1D" level="1" scaling="uint8"/>
evo 9
<table name="Timing Retard Limit" category="Timing" address="133f" type="1D" level="1" scaling="uint8"/>
add these tables to evo 7 base or evo 9 base and set the limit to 255
it will allow -10 deg for those that cant get the timing down that low,
makes a big difference to the pops and bangs.
No, 203 is the decimal view for hex 0xCB, that is a negative number in two's complement. So 0xCB means -53. In the code this value seems to be manipulated adding 0x2A (42), so the minimum timing value should be -11 also if we are logging -10 as lower value. The timing calc routine is complex, moreover this limit *seems* to be in some kind of knock reaction... could someone with more experience in the timing routine check, please?
another question...
is it possible to hold throttle open like 25% with ecu?
then we need rich the AFR and timingi -35 to 40 thats hard anti lag thats how n class evost working now!
is that possible.
i know that TPS is physically connected but maybe idle engine can to the trick!
then we dont need hardware to do it!
is it possible to hold throttle open like 25% with ecu?
then we need rich the AFR and timingi -35 to 40 thats hard anti lag thats how n class evost working now!
is that possible.
i know that TPS is physically connected but maybe idle engine can to the trick!
then we dont need hardware to do it!
No, 203 is the decimal view for hex 0xCB, that is a negative number in two's complement. So 0xCB means -53. In the code this value seems to be manipulated adding 0x2A (42), so the minimum timing value should be -11 also if we are logging -10 as lower value. The timing calc routine is complex, moreover this limit *seems* to be in some kind of knock reaction... could someone with more experience in the timing routine check, please?
agron25: i have them for the 88840017 rom (i have xml and hex) if you're interested.
i'm sure they are pretty much the same as the 016 version.
pm me your email if you want them.
i'm sure they are pretty much the same as the 016 version.
pm me your email if you want them.







