[Joshboody]

Below is a DIC 2-7 datalog.

What is the ign cor (maps) channel and how does it relate to typical IC?

Also i noticed boost setpoint when off boost is now 0 instead of -0.7psi (I'm at about 700ft above sea level). What's the change?

I little more info on Shiv's DIC would be great, as I expected to see some IC reduction in 3rd.

Also I seem to remember other user logs showing more total IC at maybe 3 or 4deg at the same setting of 100% IC. Are there other determinants?

Talking about bog in the other thread, this log seems a little different than past at shift... the retard not as late into the shift... but not sure on this one and have to look at more logs.

[themyst]

Maybe bogfix not enabled? Maybe shiv can chime in. Timing should be reduced at the shift point.

On another note, no knock anywhere!

[Alessandro]

Originally Posted by Joshboody

Below is a DIC 2-7 datalog.

What is the ign cor (maps) channel and how does it relate to typical IC?

Also i noticed boost setpoint when off boost is now 0 instead of -0.7psi (I'm at about 700ft above sea level). What's the change?

I little more info on Shiv's DIC would be great, as I expected to see some IC reduction in 3rd.

Also I seem to remember other user logs showing more total IC at maybe 3 or 4deg at the same setting of 100% IC. Are there other determinants?

Talking about bog in the other thread, this log seems a little different than past at shift... the retard not as late into the shift... but not sure on this one and have to look at more logs.

do you work in a connector seal company?

[Joshboody]

Originally Posted by Alessandro

do you work in a connector seal company?

no why do you ask?

Originally Posted by themyst

Maybe bogfix not enabled? Maybe shiv can chime in. Timing should be reduced at the shift point.

On another note, no knock anywhere!

there's timing retard during shift, just not as deep into the shift like I would think. but i was only curious because of the other thread... i actually think bog is more dependent on your foot and shift timing then anything else.

Yes, no knock... but this is not new to procede. The maps do feel great... i was just expecting more reduction in IC with it being dynamic.

[Alessandro]

Originally Posted by Joshboody

no why do you ask?



there's timing retard during shift, just not as deep into the shift like I would think. but i was only curious because of the other thread... i actually think bog is more dependent on your foot and shift timing then anything else.

Yes, no knock... but this is not new to procede. The maps do feel great... i was just expecting more reduction in IC with it being dynamic.

just saw your open tabs with the PO numbers.

[Joshboody]

Originally Posted by Alessandro

just saw your open tabs with the PO numbers.

awww, super secret info... I need to watch that. Telecom and Infrared imaging starting materials is my biz.

[Brey335i]

Originally Posted by Joshboody

awww, super secret info... I need to watch that. Telecom and Infrared imaging starting materials is my biz.

lol I never noticed that. Don't you love how observant some people on here are

[Joshboody]

bumpity bump for Shiv

[OpenFlash]

Originally Posted by Joshboody

Below is a DIC 2-7 datalog.

What is the ign cor (maps) channel and how does it relate to typical IC?

Also i noticed boost setpoint when off boost is now 0 instead of -0.7psi (I'm at about 700ft above sea level). What's the change?

No difference really. We just made some minor changes to barometric compensation. Wont have an effect on anything.

I little more info on Shiv's DIC would be great, as I expected to see some IC reduction in 3rd.

Also I seem to remember other user logs showing more total IC at maybe 3 or 4deg at the same setting of 100% IC. Are there other determinants?

Talking about bog in the other thread, this log seems a little different than past at shift... the retard not as late into the shift... but not sure on this one and have to look at more logs.

Also, you can ignore the "ign corr (maps)" channel as it doesn't show DIC corrections. Or any other correction for that matter. Just look at "ign corr" instead. It's the actual cumulative correction that you care about. But everything looks fine. And look, a revised ignition advance target. Go figure

Shiv

[Sniz]

=Joshboody;8944973

I little more info on Shiv's DIC would be great.

[Ilma]

Originally Posted by shiv@vishnu

Also, you can ignore the "ign corr (maps)" channel as it doesn't show DIC corrections. Or any other correction for that matter. Just look at "ign corr" instead. It's the actual cumulative correction that you care about. But everything looks fine. And look, a revised ignition advance target. Go figure

Shiv

Huh?

I can only see two possible data channels in the list that seem to apply:

Ignition trim
Ignition Total Correction Desired.

Is it one of those? cause I have been using ignition correction (maps) as well.

[Ilma]

Originally Posted by Sniz

[OpenFlash]

Originally Posted by Ilma

Huh?

I can only see two possible data channels in the list that seem to apply:

Ignition trim
Ignition Total Correction Desired.

Is it one of those? cause I have been using ignition correction (maps) as well.

Ignition Correction (maps) represent the ignition correction induced by the static load x rpm table. It doesn't show additional corrections applied after that by the DIC system, bogfix, etc,. So if you want to see what is actually happening in there, log "Ignition Correction" instead. For the sake of clarity, we'll probably just eliminate the Ignition Correction (maps) channel with the next software update.

[Ilma]

Originally Posted by shiv@vishnu

Ignition Correction (maps) represent the ignition correction induced by the static load x rpm table. It doesn't show additional corrections applied after that by the DIC system, bogfix, etc,. So if you want to see what is actually happening in there, log "Ignition Correction" instead. For the sake of clarity, we'll probably just eliminate the Ignition Correction (maps) channel with the next software update.

OK....but I can't seem to find a data channel with that specific name in the list