[DefactoM6]

Originally Posted by Former_Boosted_IS

I hope it is ok for me to ask a question, if not please just delete this post.

Shiv, I asked earlier if the wideband readings were accurate on the procede since there has to be an applied correction factor. At the time you said it showed the exact same as your innovative wideband. So I am correct that these wideband readings are definitely not as accurate as a standalone wideband? Why don't you just allow the 0-5v analog input from an aftermarket wideband, so you can integrate it into the tune? It seems this would be a slam dunk win.

I do remember him saying that, which is my only reservation in feeling completely at ease now. The other thing I wonder is...it sounds like the Procede is taking in the signal and modifying the output, not just blasting out a rich spot willy nilly and ignoring the input. If this is the case, why aren't we able to log the actual sensor input to the Procede, instead of the modified output?

Originally Posted by cn555ic

What software version are you running with your car..Program version??

Both my DME and V4 have the most up to date software/firmware/maps available (AFAIK)

Don't know the exact software revision on my car, but I do believe that it is the most up to date software at the moment, seeing how my car was updated when it went in for service about a month ago. My invoice said perform programming as per SIB 13 09 10.

My V4 has the 8-17 maps, and the version 27 firmware.

[M3irish]

During the logged spikes do you feel the power drop or the car hesitate in the slightest?

Rob

[Former_Boosted_IS]

Originally Posted by DefactoM6

I do remember him saying that, which is my only reservation in feeling completely at ease now. The other thing I wonder is...it sounds like the Procede is taking in the signal and modifying the output, not just blasting out a rich spot willy nilly and ignoring the input. If this is the case, why aren't we able to log the actual sensor input to the Procede, instead of the modified output?

I assume the Procede is taking the wideband O2 data from CAN data. Since the CAN data already has the "cooked" O2 signal, a correction factor needs to be applied. You will have to develop your own opinion if this method is an acceptable means to collect O2 data. I am not sure if the Procede has enough inputs or harness to log the raw wideband O2 data?

[marconi118]

wideband O2 measurement is not so easy as any other sensor (TMAP etc) that outputs a 0-5V signal corresponding to the measured value.

The wideband O2 works as follow:

one O2 sensor wire outputs the "reference" voltage (volt).

another wire is feed by the DME with a certain amount of current (mA) so that the reference voltage is kept constant.
(the reference voltage is a value defined by the manufacturer of the O2 sensor, ours are BOSCH LSU 4.9)

The lambda value is calculated by the DME by measuring the current (mA) it has to feed in the O2 sensor to maintain the reference voltage constant. It is a kind of "indirect measure".

JB3 and Procede alter the lambda value by modifying the reference voltage (the so called JB3 fuel resistors tap in the reference voltage sensing wires of the DME)
JB3 and Procede can alter lets say +10% of lambda, but don't know the real value.

If read from CAN bus the lambda value has to be corrected backward to be the real one.

The simplest way to read the A/F is to install another independent wideband O2 sensor + controller

[Sniz]

Originally Posted by M3irish

During the logged spikes do you feel the power drop or the car hesitate in the slightest?

Rob

+1?

[DefactoM6]

That was the only thing keeping me from really really worrying and removing it. I wasn't hearing knock, feeling any misfires, hesitation or flat spots. What I will say is that my car just threw a CEL about 30 mins ago. Was on the highway, just went WOT running a SN95 Cobra who was purging like crazy on the highway. Pretty embarassing, I hope thats the greatest of my concerns. I'm guessing a HPFP code, I will report back in about an hour.

[DefactoM6]

So here's what it was. What's odd is that I only first saw a CEL now, yet there are 3 recorded instances. Truth is, I reset all of the adaptations roughly around when the 1st instance was recorded, so it was probably due to that. Anyway, here's the readout from my BT:

2F6C:
2F6C Exhaust fumeflap, input signal
Error will not cause a warning light
Error is not currently present
Test conditions have been completed
Timeout

Freeze Frame Information
Event 1Odometer 24216kms 15047miles
Speed 67.00 km/h
time since start end 332.80 s
pedal sensor 1 33.59 %
voltage Kl. 87 13.81 V

Event 2Odometer 24232kms 15057miles
Speed 0.00 km/h
time since start end 0.00 s
pedal sensor 1 0.00 %
voltage Kl. 87 12.49 V

Event 3Odometer 24408kms 15166miles
Speed 0.00 km/h
time since start end 0.00 s
pedal sensor 1 0.00 %
voltage Kl. 87 12.39 V



2FCA:

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



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

Freeze Frame Information
Event 1Odometer 24280kms 15086miles
exhaust fume temperature behind catalytic converter bank 1 896.00 °C
resistor Lambda probe behind catalytic converter bank 1 0.00 ohm
voltage Lambda probe behind catalytic converter bank 1 0.18 V
voltage Lambda probe in front of catalytic converter bank 1 3.20 V

Event 2Odometer 24360kms 15136miles
exhaust fume temperature behind catalytic converter bank 1 704.00 °C
resistor Lambda probe behind catalytic converter bank 1 0.00 ohm
voltage Lambda probe behind catalytic converter bank 1 0.18 V
voltage Lambda probe in front of catalytic converter bank 1 3.20 V

Event 3Odometer 24400kms 15161miles
exhaust fume temperature behind catalytic converter bank 1 768.00 °C
resistor Lambda probe behind catalytic converter bank 1 0.00 ohm
voltage Lambda probe behind catalytic converter bank 1 0.16 V
voltage Lambda probe in front of catalytic converter bank 1 3.22 V



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

Freeze Frame Information
Event 1Odometer 24280kms 15086miles
exhaust fume temperature behind catalytic converter bank 2 896.00 °C
resistor Lambda probe behind catalytic converter bank 2 0.00 ohm
voltage Lambda probe behind catalytic converter bank 2 0.18 V
voltage Lambda probe in front of catalytic converter bank 2 3.20 V

Event 2Odometer 24360kms 15136miles
exhaust fume temperature behind catalytic converter bank 2 704.00 °C
resistor Lambda probe behind catalytic converter bank 2 0.00 ohm
voltage Lambda probe behind catalytic converter bank 2 0.18 V
voltage Lambda probe in front of catalytic converter bank 2 3.20 V

Event 3Odometer 24400kms 15161miles
exhaust fume temperature behind catalytic converter bank 2 768.00 °C
resistor Lambda probe behind catalytic converter bank 2 0.00 ohm
voltage Lambda probe behind catalytic converter bank 2 0.16 V
voltage Lambda probe in front of catalytic converter bank 2 3.24 V

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

[OpenFlash]

Originally Posted by DefactoM6

So here's what it was. What's odd is that I only first saw a CEL now, yet there are 3 recorded instances. Truth is, I reset all of the adaptations roughly around when the 1st instance was recorded, so it was probably due to that. Anyway, here's the readout from my BT:

2F6C:
2F6C Exhaust fumeflap, input signal
Error will not cause a warning light
Error is not currently present
Test conditions have been completed
Timeout

Freeze Frame Information
Event 1Odometer 24216kms 15047miles
Speed 67.00 km/h
time since start end 332.80 s
pedal sensor 1 33.59 %
voltage Kl. 87 13.81 V

Event 2Odometer 24232kms 15057miles
Speed 0.00 km/h
time since start end 0.00 s
pedal sensor 1 0.00 %
voltage Kl. 87 12.49 V

Event 3Odometer 24408kms 15166miles
Speed 0.00 km/h
time since start end 0.00 s
pedal sensor 1 0.00 %
voltage Kl. 87 12.39 V



2FCA:

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



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

Freeze Frame Information
Event 1Odometer 24280kms 15086miles
exhaust fume temperature behind catalytic converter bank 1 896.00 °C
resistor Lambda probe behind catalytic converter bank 1 0.00 ohm
voltage Lambda probe behind catalytic converter bank 1 0.18 V
voltage Lambda probe in front of catalytic converter bank 1 3.20 V

Event 2Odometer 24360kms 15136miles
exhaust fume temperature behind catalytic converter bank 1 704.00 °C
resistor Lambda probe behind catalytic converter bank 1 0.00 ohm
voltage Lambda probe behind catalytic converter bank 1 0.18 V
voltage Lambda probe in front of catalytic converter bank 1 3.20 V

Event 3Odometer 24400kms 15161miles
exhaust fume temperature behind catalytic converter bank 1 768.00 °C
resistor Lambda probe behind catalytic converter bank 1 0.00 ohm
voltage Lambda probe behind catalytic converter bank 1 0.16 V
voltage Lambda probe in front of catalytic converter bank 1 3.22 V



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

Freeze Frame Information
Event 1Odometer 24280kms 15086miles
exhaust fume temperature behind catalytic converter bank 2 896.00 °C
resistor Lambda probe behind catalytic converter bank 2 0.00 ohm
voltage Lambda probe behind catalytic converter bank 2 0.18 V
voltage Lambda probe in front of catalytic converter bank 2 3.20 V

Event 2Odometer 24360kms 15136miles
exhaust fume temperature behind catalytic converter bank 2 704.00 °C
resistor Lambda probe behind catalytic converter bank 2 0.00 ohm
voltage Lambda probe behind catalytic converter bank 2 0.18 V
voltage Lambda probe in front of catalytic converter bank 2 3.20 V

Event 3Odometer 24400kms 15161miles
exhaust fume temperature behind catalytic converter bank 2 768.00 °C
resistor Lambda probe behind catalytic converter bank 2 0.00 ohm
voltage Lambda probe behind catalytic converter bank 2 0.16 V
voltage Lambda probe in front of catalytic converter bank 2 3.24 V

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

Are you running catless by any chance? Now that we have a code to work with, it should be pretty easy to solve.

[DefactoM6]

Yup, I am catless. Have been running catless for approximately 1,200 miles.


Just for the record...This is the first time I've ever seen a CEL on my car...it didn't even throw a CEL when I started and briefly ran my car through 1-2-3 gears post-DP install and I didn't have the V4 installed yet. Will be curious to hear your thoughts, Shiv. Let me know if there are any things you would want me to log to help provide more info.

[OpenFlash]

Originally Posted by DefactoM6

Yup, I am catless. Have been running catless for approximately 1,200 miles.


Just for the record...This is the first time I've ever seen a CEL on my car...it didn't even throw a CEL when I started and briefly ran my car through 1-2-3 gears post-DP install and I didn't have the V4 installed yet. Will be curious to hear your thoughts, Shiv. Let me know if there are any things you would want me to log to help provide more info.

Do you have a downpipe fix in your car? Or are you running an o2 modifier value other than 100%.

[DefactoM6]

No DPFix, O2 modifier is at 100%

[OpenFlash]

Let's try this:

1) Reset lambda and AFR adaptions with the Procede's command center. Then cruise around normally for 5 minutes and turn off your car.

2) Then start driving as you otherwise would. And over the next few days, let's see if the code returns. If it does, we can go on to the next step.

I'm guessing you ran a dpfix before. That does influence what the DME sees for fuel control. And can induce some adaptation values. Which is why we don't recommend those and just rely on CANclear instead. So resetting all adaptions can let us start from scratch.

[DefactoM6]

Originally Posted by shiv@vishnu

Let's try this:

1) Reset lambda and AFR adaptions with the Procede's command center. Then cruise around normally for 5 minutes and turn off your car.

2) Then start driving as you otherwise would. And over the next few days, let's see if the code returns. If it does, we can go on to the next step.

I'm guessing you ran a dpfix before. That does influence what the DME sees for fuel control. And can induce some adaptation values. Which is why we don't recommend those and just rely on CANclear instead. So resetting all adaptions can let us start from scratch.

I will do a second reset of those adaptations, Shiv, and will report back with the results. I actually hadn't been running a DPFix before (owned one but never put it in, since I didn't have my DPs in before I sold it along with my old JB3). Hoping it doesn't come back! Again, given that I had driven around for about 1k miles problem free, and the issues only cropped up after I did a reset of the adaptations, I'm guessing that the problems were my own doing, and not caused by any actual hardware failure...

[OpenFlash]

Originally Posted by DefactoM6

I will do a second reset of those adaptations, Shiv, and will report back with the results. I actually hadn't been running a DPFix before (owned one but never put it in, since I didn't have my DPs in before I sold it along with my old JB3). Hoping it doesn't come back! Again, given that I had driven around for about 1k miles problem free, and the issues only cropped up after I did a reset of the adaptations, I'm guessing that the problems were my own doing, and not caused by any actual hardware failure...

Ah ok.. very possible. Adding catless downpipes can be a little tricky at times as the ECU needs to do some adapting to keep things happy. Resetting them can make it unhappy for a bit. But that should sort itself out quickly. Which means we will need to just wait and see if the code reoccurs before we start looking deeper into things.

Shiv

[Clap135]

i am throwing the same 2c7c and 2c7b codes, however I only throw them when I spray meth and outside temps are under 40 degrees. My EGT freeze frame data is also about 100C colder than yours.

[M3 Eater]

I have been fighting a question with the JB3, a lean situatuion during adapations. It seemed to be at the vanos event but I am running catless and a dp fix as well.

Could the DP fix be influencing the fueling during this event, causing it to go lean and the fuel to taper during meth spray?

It goes away after the car has pulled about 5-7 1/4 runs so its not a problem for me, just a temp situation just after a DME reset. I hate to make the car knock a few times everytime I reset the ECU. A few guys see it on the first few runs and then start changing stuff... controller settings, boost levels, meth mix... trying to trouble shoot it and give up and buy a procede. I seem to have figured it out but I think I will be buying one anyway.....

Sorry to interject on a procede thread but my JB3 is for sale......i bet you know why...