[dirtmaster666]

Hey guys

I am still having issues with my car randomly leaning right out then suddenly jump back up to normal while driving and when idling. I thought maybe my wide band o2's might have been bad so I changed those and still having same issues. I'm thinking my next plan if attack would have to be injectors. Would that be a good idea?

Also did log when this happens and it's my bank 1 that completely leans out and bank 2 is completely normal. Any thoughts?

[cwarren]

not sure why it would be random .first thought is o2 but since you changed them who knows injector is possible .

[The Ghost]

Originally Posted by dirtmaster666

Hey guys

I am still having issues with my car randomly leaning right out then suddenly jump back up to normal while driving and when idling. I thought maybe my wide band o2's might have been bad so I changed those and still having same issues. I'm thinking my next plan if attack would have to be injectors. Would that be a good idea?

Also did log when this happens and it's my bank 1 that completely leans out and bank 2 is completely normal. Any thoughts?

What do your fuel trims look like at the time? I had this happen with the Procede when adjusting the OL fueling. He fuel trim flat lined for a single bank under certain situations. Wen I reverted the map changes it went away.

[enrita]

More likely procede related. Any codes?

[dirtmaster666]

Originally Posted by The Ghost

What do your fuel trims look like at the time? I had this happen with the Procede when adjusting the OL fueling. He fuel trim flat lined for a single bank under certain situations. Wen I reverted the map changes it went away.

Fuel trim in bank 1 only flatlines.

[dirtmaster666]

Originally Posted by The Ghost

What do your fuel trims look like at the time? I had this happen with the Procede when adjusting the OL fueling. He fuel trim flat lined for a single bank under certain situations. Wen I reverted the map changes it went away.

Which maps are you running?

[The Ghost]

Originally Posted by dirtmaster666

Fuel trim in bank 1 only flatlines.

It is tune related. Revert to a prior map or reduce OL fueling some which I've found reduces these occurrences.

[OpenFlash]

If the problem is happening at idle and during cruise, it's either going to be injector or o2 sensor related. It's important to see what codes pop up as that will give you a good starting point for troubleshooting.

[BQTuning]

When last was the intake valves cleaned and how many miles on the car ?

[OpenFlash]

Originally Posted by enrita

More likely procede related. Any codes?

Procede isn't doing anything during idle or cruise so that may not be a good diagnosis. The only thing that the Procede can induce is when you running too high of an Open Loop fuel value which can, in some cars, make the fuel pressure signal voltage drop too low under boost (loggable as debug byte 4). When that happens, you will see a very rich AFR and inconsistent timing. But then again, this only applies under heavy load/boost.

[dirtmaster666]

Don't get any codes and I also just re uploaded the maps and firmware and still nothing has changed. I guess I prob look into Injectors

[themyst]

borrow another tune, rule that out. that would be cheaper than replacing parts that dont need replacing.

[dirtmaster666]

Been running procede for a while and never had these issues before. It happened again during a cruise to a business meeting and while it happens I get huge hesitation. I switched to map 0 ( stock map) while it was happening and still felt major hesitation. So I think I pretty much ruled out tune. Also took another log at idle and bank 1 Afr hits 18+ :1 and bank 2 is at 14ish:1 do its definetly something on my bank 1. My car is a 07 with 72xxx km on it and apparently injectors were done before I bought it which would have been at least 2 yrs ago. So I think injectors for bank 1 is next. Anyone know where to buy them? Or since I can't code myself taking to dealer is best?

[Eric335]

Originally Posted by dirtmaster666

Been running procede for a while and never had these issues before. It happened again during a cruise to a business meeting and while it happens I get huge hesitation. I switched to map 0 ( stock map) while it was happening and still felt major hesitation. So I think I pretty much ruled out tune. Also took another log at idle and bank 1 Afr hits 18+ :1 and bank 2 is at 14ish:1 do its definetly something on my bank 1. My car is a 07 with 72xxx km on it and apparently injectors were done before I bought it which would have been at least 2 yrs ago. So I think injectors for bank 1 is next. Anyone know where to buy them? Or since I can't code myself taking to dealer is best?

You might have to replace all 6 injectors unless your already running the updated injectors. The old ones are not compatible with the new ones. Could get expensive

[acdHQK713K]

Originally Posted by dirtmaster666

Been running procede for a while and never had these issues before. It happened again during a cruise to a business meeting and while it happens I get huge hesitation. I switched to map 0 ( stock map) while it was happening and still felt major hesitation. So I think I pretty much ruled out tune. Also took another log at idle and bank 1 Afr hits 18+ :1 and bank 2 is at 14ish:1 do its definetly something on my bank 1. My car is a 07 with 72xxx km on it and apparently injectors were done before I bought it which would have been at least 2 yrs ago. So I think injectors for bank 1 is next. Anyone know where to buy them? Or since I can't code myself taking to dealer is best?

We are working on nearly the same issue it seems. I bought O2 sensors but looks like that won't be the fix. My issue was slightly different in that it would lean out and then data from the O2 sensors would just cut out completely and then a second or two later it would reestablish a connection but the AFRs would be ~17+ at WOT.

I reported last time my injectors were replaced but that was not true. I still have the old injectors in the car but hopefully this week the dealer will replace them and I can let you know if that fixes the issue.

It's a very frustrating problem considering if basically keeps you from pushing the car whatsoever.

[dirtmaster666]

Originally Posted by Stangorang

We are working on nearly the same issue it seems. I bought O2 sensors but looks like that won't be the fix. My issue was slightly different in that it would lean out and then data from the O2 sensors would just cut out completely and then a second or two later it would reestablish a connection but the AFRs would be ~17+ at WOT.

I reported last time my injectors were replaced but that was not true. I still have the old injectors in the car but hopefully this week the dealer will replace them and I can let you know if that fixes the issue.

It's a very frustrating problem considering if basically keeps you from pushing the car whatsoever.

Totally agree. Seems like same issue. Keep me updated for sure


Thanks

[135Hoser]

I had similar issues with my procede. wacky afr's under idle/cruise. replaced injectors, o2 sensors, cleaned valves, reset adaptations, etc. Had a ton of misfires on stage 3/94 oct+meth, some misfires running stage 2, and under stage 1 it'd run mostly properly.

JB4 fixed it. No CEL, no weirdness, none of that crap. Put foot down and car goes every time.

[enrita]

Originally Posted by themyst

borrow another tune, rule that out. that would be cheaper than replacing parts that dont need replacing.

[Jeff@TopGearSolutions]

IDK why everyone is quick to blame the tune with the OP has had the tune for quite a long time and the problem happened recently. It's clearly a hardware issue on the vehicle and not the tune. Especially if it happens when the tune is out or on stock map.

The first rule is to check for codes.

If no codes are found, send logs to your tuner of the event.

If the problem persist on a stock map then it's even more apparent it's not tuning related.

I wish the hater camps would provide more accurate insight instead of just blasting a tune every time.

There is proper procedure for diagnosing a problem and it doesn't need to be buy a new tune or buy more parts right out of the gate.

Between codes and logging you can solve 95% of problems and at that point one or the other will tell you what needs to be fixed.


FYI, screen shot logs are not very valuable. They dont show the whole picture. Proper data log reading requires all of the logging sensors and only a CSV will show that.
In the future, people should post their CSV log files to the tuner and if need be here. (Although the majority of people here won't know what to look for but there are some).

[135Hoser]

Originally Posted by Jeff@TopGearSolutions

IDK why everyone is quick to blame the tune with the OP has had the tune for quite a long time and the problem happened recently. It's clearly a hardware issue on the vehicle and not the tune. Especially if it happens when the tune is out or on stock map.

The first rule is to check for codes.

If no codes are found, send logs to your tuner of the event.

If the problem persist on a stock map then it's even more apparent it's not tuning related.

I wish the hater camps would provide more accurate insight instead of just blasting a tune every time.

There is proper procedure for diagnosing a problem and it doesn't need to be buy a new tune or buy more parts right out of the gate.

Between codes and logging you can solve 95% of problems and at that point one or the other will tell you what needs to be fixed.


FYI, screen shot logs are not very valuable. They dont show the whole picture. Proper data log reading requires all of the logging sensors and only a CSV will show that.
In the future, people should post their CSV log files to the tuner and if need be here. (Although the majority of people here won't know what to look for but there are some).

unless of course, the piggyback itself is failing.

[enrita]

Originally Posted by Jeff@TopGearSolutions

IDK why everyone is quick to blame the tune with the OP has had the tune for quite a long time and the problem happened recently. It's clearly a hardware issue on the vehicle and not the tune. Especially if it happens when the tune is out or on stock map.

The first rule is to check for codes.

If no codes are found, send logs to your tuner of the event.

If the problem persist on a stock map then it's even more apparent it's not tuning related.

I wish the hater camps would provide more accurate insight instead of just blasting a tune every time.

There is proper procedure for diagnosing a problem and it doesn't need to be buy a new tune or buy more parts right out of the gate.

Between codes and logging you can solve 95% of problems and at that point one or the other will tell you what needs to be fixed.


FYI, screen shot logs are not very valuable. They dont show the whole picture. Proper data log reading requires all of the logging sensors and only a CSV will show that.
In the future, people should post their CSV log files to the tuner and if need be here. (Although the majority of people here won't know what to look for but there are some).

is not about "hater camp"... is just the easiest way to rule out something.

[acdHQK713K]

Went back and looked at my data logs, the data is actually there for the AFRs, just the graphing program hacked it out to make pretty graphs since they spike up pretty high making a graphed datalog look like crap.

My AFRs jump up to the mid 20's during WOT....