I am currently on a custom Tephra V5 88590015 2D SD ROM with "Knock Sum Required for Slow Cell" = 3 and "Knock Sum Required for Fast Cell" = 5. This has been working fine and EVOScan properly logs any knock count as it should and the "Check Engine Light" has flashed as it should. I transferred all of my maps to the TEPHRA V7 88591715 2D SD ROM so I could get it all updated and working the same prior to swapping to the 88592715 3D SD ROM since they both use the base 88590715 ROM.

Anyway, all of my maps were transferred over and I go to drive the car and everything seems as it should. However, because I just installed the FIC 1650cc injectors I haven't dialed in the Injector Scalar so I don't expect it to be ok under boost. However, I tip into the throttle just to see what the AFR's do and the cell light starts to fast flash. It does this several times so I go into the log and it shows just a few random 1 counts here and there, but nothing in the specific area that I saw it flash. I have slow flash set to 3 and fast flash set to 5. I do this several times and the light fast flashes, but logs show nothing.

I transferred over all of the major knock table values with the exception of the Single Gain and Tripple Gain tables, which my map has different values vs the stock ROM. I don't think this can be the source of the issue, but don't know. What would cause the cell to flash and not show up in the log? I put back the old Tephra V5 88590015 ROM and this does not happen. If anyone has thoughts I would like to hear them as I want to try the 3D stuff to see how I like it.

 

I still have not got this figured out so I thought I would post the code in both of the ROM's to see if anyone has thoughts on the issue. I am not sure it matters if they are different or the same, but perhaps someone with better knowledge than me can respond.

Below is the code from the TephraMOD-88590715-V7.XML ROM that is having the issue. I put in bold the address for the various features, which are different than my current 88590015.XML ROM.

<table name="KnockSum Required for Slow CEL (Low Knock)" category="Knock Light Settings" address="4823c" type="2D" scaling="uint16">
<table type="Static Y Axis" elements="1">
<data>CEL will flash SLOWLY once KnockSum exceeds this value:</data>
</table>
</table>

<table name="KnockSum Required for Fast CEL (High Knock)" category="Knock Light Settings" address="4823e" type="2D" scaling="uint16">
<table type="Static Y Axis" elements="1">
<data>CEL will flash QUICKLY once KnockSum exceeds this value:</data>
</table>
</table>

<table name="Load Required for CEL on Knock" category="Knock Light Settings" address="48240" type="2D" scaling="Load">
<table type="Static Y Axis" elements="1">
<data>Load must EXCEED this value before 'CEL on Knock' activates:</data>
</table>
</table>
<table name="High Knock Boost Drop and Knock CEL Flash time" category="Knock Light Settings" address="48242" type="2D" scaling="ECUTime">
<table type="Static Y Axis" elements="1">
<data>Duration CEL continues to flash AFTER the last occurance has stopped:</data>
</table>
</table>

Below is the code from my current 88590015.XML ROM, which is working just fine. I put in bold the address for the various features, which are different than the ones above

<table name="KnockSum Required for Slow CEL" category="V5 Mods" address="4815a" type="1D" scaling="uint16"/>

<table name="KnockSum Required for Fast CEL" category="V5 Mods" address="4815c" type="1D" scaling="uint16"/>

<table name="Load Required for CEL on Knock" category="V5 Mods" address="4815e" type="1D" scaling="Load"/>

<table name="CEL on Knock flash time" category="V5 Mods" address="48160" type="1D" scaling="ECUTime"/>.

 

there is a feature that also flashes the cel if afr is out of range. Check to see if that is enabled and what the threshold is.

 

I found a table called "AFR Safety Boost Drop and CEL Flash Time." This may be what is causing the flashing cell because this feature was enabled. Will check and report back.

 

We posted at the same time....thanks!

 

That was it!

 

hah thats awesome. Glad you figured it out.

 

its a good feature though, you should use it when you get your tune dialed in.

 

You figured it out first , but I had not refreshed my screen when I posted so I did not see your post from 14 minutes earlier.

 

I do like the feature so I might go ahead and turn it on. I just need it to stay on a longer time so I can differentiate between LEAN AFR and High Knock Count.

 

I set mine to blink for 10 seconds on AFR, thats how i can tell the difference. Also you need a wideband wired in to your ECU in place of the rear 02 sensor for it to work correctly. So its not as simple as just turning it on, there is some more steps involved.

 

It's already setup, which is why I started this thread