Results 1 to 6 of 6

Thread: Scanner not consistent with editor

  1. #1

    Scanner not consistent with editor

    I did some WOT runs and I had a constant 25deg of timing advance. Some 26s and even a few 27s. In my high octane table I have 24s in the large area where my WOT runs occur. Nothing higher. In order to dial in my timing exactly the way I want it, I need to understant this phenomena.

    The problem is that I'm getting 2 deg of knock at certain RPM under WOT, not always. I need to know wheter lowering timing will actually lower timing. Or what other factors also influence this addition of timing to the octane tables. Any ideas?

  2. #2

    Re: Scanner not consistent with editor

    There are other factors that add and subtract to come up with the final timing value. Usually a 1* decrease on the High Octane table will show a 1* decrease in final timing

  3. #3

    Re: Scanner not consistent with editor

    How do you figure out from which cells it's taking the timing from?

  4. #4

    Re: Scanner not consistent with editor

    It should be plotted in your histogram(spark for timing, retard for cells that showed KR)... If that doesnt answer you question can you re-ask it with a little more detail.

  5. #5
    Senior Tuner
    Join Date
    Nov 2002
    Location
    Central Florida
    Posts
    2,503

    Re: Scanner not consistent with editor

    Be sure you log the Dynamic Cylinder Air PID
    alond with RPM, these are the two spark table
    axes and you should see the value from the table
    at the indicated coords. If not you have to look at
    the modifiers (KR, burst knock, IAT/ECT/EGR adders
    and like that).

  6. #6

    Re: Scanner not consistent with editor

    Thanks for the help. Next time I can get a laptop I'll log Dynamic Cylinder Air.