[STirish]

Is there anyway to look at the Ignition Learning Maps? This could prove helpful when trying to figure out the timing algos and "why is my timing dipping there" w/o a ECU reset.

Is it true that the ECU only sees the binary knock value to adjust timing by or can it see the full voltage range of the knock sensor and we only get the binary value? Trey said something about the binary value being the only one avalible to them.

I would about give my left hand to see some of the timing algos. Wouldn't it be awesome to know how the ECU populates the Ignition Learning Maps? Whoa do I have a lot of playing and learning to do.

BTW, the ST is in and let the games begin!

Thanks,
Rob

[darkcrystal05]

What's up Rob. Nice to see you got it. You'll have to let me know how the tuning is going. So does ST have the capability to control the voltages and knock values, similar to what lemmiwinks does for the Audi guys?
BTW - I'm still waiting for my downpipe, ugh! It's been like a month and their still backordered. I even tried Tarmac and they said the same thing. I'm just itching to get it. Need... mo... powah!

[daemon]

No way to see what has been learned timing-wise that I know of, other than trying to piece it together from log files (good luck trying it that way ).

I imagine the ECU has to do a bit of signal analysis on the knock sensor output to filter out meaningless noise. That is probably why only a binary value is available (or easily available). Ten samples per second is most likely not good enough for us to really utilitze that sensors voltage anyway. Easier for the ECU to do the highspeed calculations and give us a binary output. It would be nice if it was a latched output though, or better yet, an incrementing counter.

What do you mean by "control the voltages and knock values"?

[STirish]

Originally Posted by daemon

No way to see what has been learned timing-wise that I know of, other than trying to piece it together from log files (good luck trying it that way ).

I imagine the ECU has to do a bit of signal analysis on the knock sensor output to filter out meaningless noise. That is probably why only a binary value is available (or easily available). Ten samples per second is most likely not good enough for us to really utilitze that sensors voltage anyway. Easier for the ECU to do the highspeed calculations and give us a binary output. It would be nice if it was a latched output though, or better yet, an incrementing counter.

What do you mean by "control the voltages and knock values"?

With Lemmi (Free B5 S4 ECU tool) we could add timing on top of what the ECU calculated, change idle speeds, play with fuel trims, scale injectors, change MAF calibration, and a few other things I can't remember. It was pretty lean, but a great tool for free. It is kind of like the basic params you can change with ECUTek's DeltaDash.

A counter would be awesome. I would imagine the Knock sensor either has a 0-1V or 0-5V output that would also be pretty awesome to have. Ah heck, I'd settle for a latched value too

It seems we should get access to the Ignition Learning Maps, even if it is read only. Cobb should be able to give this to us with little work

D -
Yeah, the ST is in and we're playing and testing at this point. Probably start tuning this weekend. Mo pOWar hO! It's time to start breaking kneecaps if that DP doesn't show soon

[WolfPlayer]

There is some stuff that you guys are forgetting.

Cobb uses the Subaru Select Monitor (SSM). The SSM does not output any Knock values other than Yes/No as far as I am aware. Thus, this isn't a very simple change for Cobb. Also, the learned values to which you are referring are also not part of the SSM. They are part of the memory that the ECU uses for storage and not part of the SSM.

t