Jump to content
LegacyGT.com

ripemeat

Members
  • Posts

    562
  • Joined

Posts posted by ripemeat

  1. I've ridden in many LGT's, both auto and manual and certainly notice the stumble that's mentioned in this thread. It seems to be limited to the manual tranny crowd though (and verified by the posters in this thread and an overwhelming majority). You can always flash an auto map onto a manual car and see if the problem resolves, just disable the neutral safe switch CEL, might be worthwhile...it could eliminate a mechanical fault as being the culprit.
  2. Cobb OTS maps do knock at low loads, if you have some learned knock there, the stutter you feel is the car moving in/out of load cells that have a jump or dip in timing from one to the next. Solution is to get a better tune. Another possibility is fueling. Best bet is to check a learning view to see if either of those two things are a reasonable cause for your particular car. Another option is that the Cobb timing tables (the base and advance) are not smooth, this is the fault of cobb themselves and can very well cause a stutter on it's own, even if you aren't knocking. This is why open source, or a custom pro tune is beneficial for driveability.
  3. I said IAM, not IAT(intake air temp)....Mostly for those people reading this that don't use cobb. IAM is DAM for open source people. Don't log independently, just add it to your log parameters(you know you can log multiple parameters at once to file).

     

    If you just want to know if you're knocking at all, or in the recent past, log FLKC and DAM. If you only log FLKC, you could very well have 0 all across the board but your DAM could be <1, which means you had significant knock in the past and the ecu is fractioning your total ignition down so that you don't have any more learned knock. That's still a bad situation even if your FLKC is all 0's.

  4. If I log FBKC for a WOT run and there's no correction for knock, that would lead me to believe I'm relatively ok... Correct?

     

    I will occasionally log Boost and FDKC independantly just to see that I'm not knocking and can still hit peak boost, but I'm not an experienced logger. Been running Cobb's stg1 maps on my last couple Subaru's without issue, and all my motors have had great compression when tested. Pretty much have always run a catless UP of some sort, clean filters on the stock intake, and stock DP with aftermarket CBE of some sort.

     

    This is slowly becoming my next project to tackle with regard to modding, and a large reason why I haven't gone past stg1.

     

     

    fbkc only tells you if you're currently knocking. you still need to log DAM and fine learning knock to see if there's previous knock events bad enough for the ecu to learn to reduce timing. your fbkc might be zero the entire pull yet you could have oogles of learned knock or an iam/dam of less than 1.

  5. If my AF learning A is 6.1 what does this mean? the others are around -.7 , .07. and like 1.02. hittin target boost.

     

    cob ots stage2 stock air box

     

    it means your ecu is detecting you afr is too lean and it's adding 6% more fuel in order to reach 14.7 at idle. your maf scaling may be too low and the ecu is compensating. general you'd like to see negative (richer) rather than leaner. the rest of your numbers are great so i wouldn't worry too much about it.

  6. to be honest, if you pull a couple degree in your timing table and it still knocks there and sometimes dropping the iam with it, disregard it, do you really think you're running >4* too much timing there? I highly doubt it, and 3 other tuners probably would've noticed. I'd forget it assuming the rest of your tune is kosher- fueling and WOT.
  7. If you're staying at throttle and it's that low of a load and rpm, and it knocks the IAM all the way down I would suspect bad grounds or engine noise, or bad gas. You're talking closed loop areas there so fueling shouldn't be a problem(unless your maf scaling is off and your LTFT are well in the positives in the respected g/s range). If timing was the problem, the knock sensor shouldn't be picking up more events after it pulled a degree or two already.
×
×
  • Create New...

Important Information

Terms of Use