[Castr_85M]

I figured i'll get a faster response on here. Thanks guys

I just got a procede from you guys last monday rev 2 with v4, i'm very
happy with everything. Its far superior to my old jb3 tune in almost
every aspect. Only issue i'm having is that my SES light keeps coming
on and when i check the code with my BT tool its giving me the no cat
codes. I'm running DCI and catless downpipes. I have cleared the code
with my BT tool and with the procede and it keeps coming up. The
canclear function is on and 02 setting is at 50%. I keep getting the
code for some reason when the canclear is sopose to not even let it
show up. Please let me know what direction to take with this.

[OpenFlash]

Originally Posted by alofoque

I figured i'll get a faster response on here. Thanks guys

I just got a procede from you guys last monday rev 2 with v4, i'm very
happy with everything. Its far superior to my old jb3 tune in almost
every aspect. Only issue i'm having is that my SES light keeps coming
on and when i check the code with my BT tool its giving me the no cat
codes. I'm running DCI and catless downpipes. I have cleared the code
with my BT tool and with the procede and it keeps coming up. The
canclear function is on and 02 setting is at 50%. I keep getting the
code for some reason when the canclear is sopose to not even let it
show up. Please let me know what direction to take with this.

Sounds like you have a very old DME software version (circa 2007/2008?). My suggestion is to get updated software so that the cat codes go pending before the SES light comes on. This gives the procede the time it needs to automatically clear the code without it every being visible. In this respect, he CANclear feature is only compatible with software versions from late 2008 and up.

If you don't want to update your DME software, you will just have to dial in that o2 modifier value. Which takes time to get it right. Start off at 50% and drop it in 5% increments if the code comes back. Don't go too low or else you will trip various o2 sensor codes.

Personally, i don't like tinkering with o2 sensor signals if i can get away with it. Doing so usually has other side-effects such as reduced fuel economy due to wacky fuel trims. Misfire is also more likely when running such a device. Because of this, I recommend the DME software update solution.

Glad you are enjoying the new tune

Shiv

[Castr_85M]

Actually its a 2010 135i with the latest software put in september when i went in for a HPFP replacement. I posted on e90 because i mainly see the visnu guys on here rather then 1addicts. Maybe i have to let it adapt more? Log a couple hundred miles, this is what happend when i had my bms o2 fix, had to give it time and it just went away.

[OpenFlash]

Originally Posted by alofoque

Actually its a 2010 135i with the latest software put in september when i went in for a HPFP replacement. I posted on e90 because i mainly see the visnu guys on here rather then 1addicts. Maybe i have to let it adapt more? Log a couple hundred miles, this is what happend when i had my bms o2 fix, had to give it time and it just went away.

Hmmm.... What is the exact code? Are you sure they are cat conversion codes (29F4 and 29F5) and not something else? CANclear should work on your car. Which means you shouldn't use the o2 modifier feature at all (leave it at 100%).

[Castr_85M]

These are the codes bt tool is giving me. Car runs sound though, not stuttering or hesitation running better then ever. I dont know what these codes are or why can clear wouldnt clear them before they come up.

2C77:
2C77 Lambda probe behind catalytic converter, signal
Error will cause a warning light
Error is currently present
Test conditions have been completed
Timeout

Freeze Frame Information
Event 1Odometer 14936kms 9280miles
exhaust fume temperature behind catalytic converter bank 1 368.00 °C
resistor Lambda probe behind catalytic converter bank 1 65,280.00 ohm
voltage Lambda probe behind catalytic converter bank 1 0.41 V
time since start end 76.80 s

Event 2Odometer 14936kms 9280miles
exhaust fume temperature behind catalytic converter bank 1 400.00 °C
resistor Lambda probe behind catalytic converter bank 1 65,280.00 ohm
voltage Lambda probe behind catalytic converter bank 1 0.41 V
time since start end 102.40 s

Event 3Odometer 14968kms 9300miles
exhaust fume temperature behind catalytic converter bank 1 288.00 °C
resistor Lambda probe behind catalytic converter bank 1 65,280.00 ohm
voltage Lambda probe behind catalytic converter bank 1 0.41 V
time since start end 76.80 s



2C78:
2C78 Lambda probe behind catalytic converter 2, signal
Error will cause a warning light
Error is currently present
Test conditions have been completed
Timeout

Freeze Frame Information
Event 1Odometer 14936kms 9280miles
exhaust fume temperature behind catalytic converter bank 2 352.00 °C
resistor Lambda probe behind catalytic converter bank 2 65,280.00 ohm
voltage Lambda probe behind catalytic converter bank 2 0.41 V
time since start end 76.80 s

Event 2Odometer 14936kms 9280miles
exhaust fume temperature behind catalytic converter bank 2 384.00 °C
resistor Lambda probe behind catalytic converter bank 2 65,280.00 ohm
voltage Lambda probe behind catalytic converter bank 2 0.41 V
time since start end 102.40 s

Event 3Odometer 14968kms 9300miles
exhaust fume temperature behind catalytic converter bank 2 272.00 °C
resistor Lambda probe behind catalytic converter bank 2 65,280.00 ohm
voltage Lambda probe behind catalytic converter bank 2 0.41 V
time since start end 76.80 s

2FCA:

Error will not cause a warning light
Error is not currently present
Test conditions have been completed
Short circuit or signal interruption



2FDB:

Error will not cause a warning light
Error is not currently present
Test conditions have been completed
Short circuit or signal interruption



2FDA:

Error will not cause a warning light
Error is not currently present
Test conditions have been completed
Short circuit or signal interruption



2C77:
2C77 Lambda probe behind catalytic converter, signal
Error will cause a warning light
Error is currently present
Test conditions have been completed
Timeout

Freeze Frame Information
Event 1Odometer 14936kms 9280miles
exhaust fume temperature behind catalytic converter bank 1 368.00 °C
resistor Lambda probe behind catalytic converter bank 1 65,280.00 ohm
voltage Lambda probe behind catalytic converter bank 1 0.41 V
time since start end 76.80 s

Event 2Odometer 14936kms 9280miles
exhaust fume temperature behind catalytic converter bank 1 400.00 °C
resistor Lambda probe behind catalytic converter bank 1 65,280.00 ohm
voltage Lambda probe behind catalytic converter bank 1 0.41 V
time since start end 102.40 s

Event 3Odometer 14968kms 9300miles
exhaust fume temperature behind catalytic converter bank 1 288.00 °C
resistor Lambda probe behind catalytic converter bank 1 65,280.00 ohm
voltage Lambda probe behind catalytic converter bank 1 0.41 V
time since start end 76.80 s



2C78:
2C78 Lambda probe behind catalytic converter 2, signal
Error will cause a warning light
Error is currently present
Test conditions have been completed
Timeout

[OpenFlash]

Solution: don't run the o2 modifier. Hardware based downpipe fixes are outdated and finicky when used with newer DME versions. Also, update your pnp harness. And leave CANclear on. That will keep your SES light from coming on from running without kitties. As suspected, the codes you were getting weren't from running without kitties. But rather from improper settings on your o2 modifier which is no longer needed.

[Castr_85M]

I just got the procede on Thanksgiving week i think day before thanksgiving so it was your lastest batch. I dont know if the harness is the latest one or i have to change it.

[OpenFlash]

Originally Posted by alofoque

I just got the procede on Thanksgiving week i think day before thanksgiving so it was your lastest batch. I dont know if the harness is the latest one or i have to change it.

Just take a look at it. It may or may not be updates.

[Longboarder]

Originally Posted by shiv@vishnu

Solution: don't run the o2 modifier. Hardware based downpipe fixes are outdated and finicky when used with newer DME versions. Also, update your pnp harness. And leave CANclear on. That will keep your SES light from coming on from running without kitties. As suspected, the codes you were getting weren't from running without kitties. But rather from improper settings on your o2 modifier which is no longer needed.

I upgraded to autotune a couple months ago and just yesterday got an SES light...noticed my o2 modifier was set at 50. Interesting that it took 2 months for the SES light to come on. I just changed the value to 100 and no SES light for now...and hopefully never.

[Calvin@Vishnu]

Originally Posted by Longboarder

I upgraded to autotune a couple months ago and just yesterday got an SES light...noticed my o2 modifier was set at 50. Interesting that it took 2 months for the SES light to come on. I just changed the value to 100 and no SES light for now...and hopefully never.

o2 sensor related faults are funny like that. Which is why I don't recommend using that feature any more. Relying on CANclear as a DP fix is a much better solution. Update your harness!

[Castr_85M]

Well i just checked my harness and apparently it did not have the jumper cables on the empty pins (6,7) but it did have the 2 yellow wires removed and taped. The stock harness actually does have a pin going in to the PNP harness which their was nothing there before. I'll take the car out in a lil while after i clear all codes and see if it comes back.

[Castr_85M]

It worked updated my harness as per the thread. No more ses light (knock on wood) 50 miles in. Thanks shiv for the prompt responses

[OpenFlash]

Originally Posted by alofoque

It worked updated my harness as per the thread. No more ses light (knock on wood) 50 miles in. Thanks shiv for the prompt responses

No problem!

[Thumperx]

Shiv,
Currently I have the V3 in my 07 335i, and I'm ready to step up to the V5. But I'm concern if I have my DME updated (solving the turbo rattle), the new software will introduce throttle lag.

What are your thoughts about this new software throttle lag issue? Does the V5 compensate for the loss of power? (I'm familiar that your product has turbo rattle adjustments)

[OpenFlash]

Originally Posted by Thumperx

Shiv,
Currently I have the V3 in my 07 335i, and I'm ready to step up to the V5. But I'm concern if I have my DME updated (solving the turbo rattle), the new software will introduce throttle lag.

What are your thoughts about this new software throttle lag issue? Does the V5 compensate for the loss of power? (I'm familiar that your product has turbo rattle adjustments)

One of the unique things about the Procede is that it has absolute control over the boost control solenoids and throttle valve. So it doesn't matter what BMW does to the DME to introduce lag. The Procede will over-ride it. Go ahead and get the updated. Or don't. Doesn't matter once the Procede is installed

Shiv

[Castr_85M]

Originally Posted by shiv@vishnu

One of the unique things about the Procede is that it has absolute control over the boost control solenoids and throttle valve. So it doesn't matter what BMW does to the DME to introduce lag. The Procede will over-ride it. Go ahead and get the updated. Or don't. Doesn't matter once the Procede is installed

Shiv

So go ahead and drop that V5 like its hot!

[Thumperx]

Thanks Shiv for the advice. I will go in and update the DME.