Ignition Retard Limit
Thread Starter
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
Hi Guys,
While looking for this knock stuff I came across the Ignition Retard limit in the ROM.
88590015 and 88580013 (9's???): 0x133e
96530006 and 94170015 (8's???): 0x173e
2 bytes, so uint16 scaling.
Now it defaults to 203 (or 0xCB), I found that by increasing it to 220 I was able to run -15* as opposed to the previous limit of -10*.
Now whoever disasm'd this ROM (Bez???) already found this, so I don't want to take any credit for it
Also I don't know the proper scaling yet, but if anyone figures it out let me know
Usual deal of test everything at idle - altmaps makes testing this pretty easy, just leave your standard map as-is, and then flick to altmaps with lots of timing retard at idle..
Cheers
D.
While looking for this knock stuff I came across the Ignition Retard limit in the ROM.
88590015 and 88580013 (9's???): 0x133e
96530006 and 94170015 (8's???): 0x173e
2 bytes, so uint16 scaling.
Now it defaults to 203 (or 0xCB), I found that by increasing it to 220 I was able to run -15* as opposed to the previous limit of -10*.
Now whoever disasm'd this ROM (Bez???) already found this, so I don't want to take any credit for it

Also I don't know the proper scaling yet, but if anyone figures it out let me know

Usual deal of test everything at idle - altmaps makes testing this pretty easy, just leave your standard map as-is, and then flick to altmaps with lots of timing retard at idle..
Cheers
D.
That retard limit was referred in this thread as well:
https://www.evolutionm.net/forums/sh...9&postcount=13
90550001 should have the same: 0x173e (uint16)
Have it in my 96530006 def - but not played with it yet (actually do not need such a big retard
https://www.evolutionm.net/forums/sh...9&postcount=13
90550001 should have the same: 0x173e (uint16)
Have it in my 96530006 def - but not played with it yet (actually do not need such a big retard
Trending Topics
Howdy dave
according to bez to get the timing to retard to anything below -10 you had to patch a few different places in the rom as there was a lot of code to stop the timing from dropping,
in the rom bez sent me he has full antilag, realtime tuning and speed density setup.
it would be excellent if you could incorporate these mods with your own to make a super patch,
if the above could be patched along with your own mods it would mean the stock ecu would be as powerfull as any aftermarket ecu,
and as bez has stated he is fully willing to share his findings for the benefit of the community
according to bez to get the timing to retard to anything below -10 you had to patch a few different places in the rom as there was a lot of code to stop the timing from dropping,
in the rom bez sent me he has full antilag, realtime tuning and speed density setup.
it would be excellent if you could incorporate these mods with your own to make a super patch,
if the above could be patched along with your own mods it would mean the stock ecu would be as powerfull as any aftermarket ecu,
and as bez has stated he is fully willing to share his findings for the benefit of the community
Thread Starter
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
yeah because 128 would actually be limitting the retard so much that you are going into advance there... ie not allowing advance to drop below 10* or whatever...
So would 0x2038 workout to be 0x2438 for 90550001 and all other e7 and 8 roms ?
Thread Starter
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia

I looked at the code for 90550001 and its totally different... doh
Interestingly in 90550011 the 0x173e is 0xBC not 0xCB




er, ive enough knock thanks,,think il sharpen up that chainsaw