Quote:
Originally Posted by steve99
Certianly seems a strange co0incidence
maybe log
KC Learned
FLKC (the problem one)
Ignition timing total
You should see a corresponding drop in KC Learned and Ignition timing total when FLKC goes negative. If their was a weird logging issue then it should show up. if FLKC goes -3 their should be corresponding dip in KC learned and Total Ignition timing applied.
logging is done by the OFT software asking for the contents of a specific RAM address in the ECU a scaling factor may then be applied and the result is presented in the log. Each ROM type ie C/G/A ect and sometimes the different revisions of those ROM's will have different locations for these RAM addresses ,its possible something is wrong but everyone on same ROM would have the problem. But it may not be a universal issue for all ROM types.
I doubt they have changed anything in the Flashing side of things and if that was out of wack the FLKC would be the least of your problems. The OFT corrects the checksum and I would imagine then checks the checksum of the flashed ROM and would throw an error if that was incorrect. If the flash was bad its likely the car would not run.
As @ troek said you can trigger false knock indication from loose bolts or a washer or similar dropped down near knock sensor or exhaust hitting on sub-frame ect |
Wasn't able to capture much flkc spikes aside from 2 little .65 in 5th gear I was not aware what was actually going on looking at the OFT display as the flkc decided to freeze at .65 and kc at .68 seconds after I started to log... will try again in warmer weather or get my oil temps hotter before I start next time. or maybe reflash the more knock prone OTS tune.
http://datazap.me/u/solidone/stg1-20...0&data=1-12-14
No changes were made to the car or tune since yesterday BTW.