Afr spikes in BBL only

[ntae]

We reloaded the Boot & firm in the V2 . Formated the V2 config , internal & Sd card and all is good now

[alian]

We reloaded the Boot & firm in the V2 . Formated the V2 config , internal & Sd card and all is good now

Yep, who would have thought, Thanks again Geoff. Ian

[vxleather]

just gota work out where to put all that acurate scaned info now..

[Blacky]

The value that it "spikes" to is significant. The FlashScan firmware will set the AFR to 25.00 whenever it reads a data packet from the wide band controller that is not valid AFR data.

For example the PCM may have gone into deceleration fuel cutoff and the WO2 controller may be outputting a "free air" value rather than the AFR value.

Try logging the EXT.WO2STATE PID(s) as well to see what the data state is when the value goes to 25.00

What you are seeing may be legitimate - in which case you should use the data filters to filter out frames where AFR=25.00.

Regards
Paul

[ntae]

Both people there V2 units work in passthrough ok . its just when you use BBL there is the problem . Both of these units had the same problem with the same techedge 2J1 unit a week ago and mine was ok & know of about 12 others that BBL with serial PLX & Techedge with no problems . I got the first one working as per my post . VX did not format the V2 internal memory. i think that is his problem today . He is on to it as we type


Geoff

[vxleather]

ok have tried reformating the memory, procedure went full format of both memories, then re load boot block, then re load firmware and re formate it all again.. did this 3 times and it did not fix teh problem...

Blacky can you do aquick explanation of what it means when it hits 25 afr... i really dont understand... Free Air..???

And why do we see it in BBL only and not Pass threw, or when using non serial ????

[Blacky]

Try logging the EXT.WO2STATE PID(s) as well to see what the data state is when the value goes to 25.00

Did you try this?

What this will tell you is whether the data being sent from the WO2 device is sending valid AFR data and FlashScan is not reading it correctly, or whether the WO2 device is sending invalid data which causes FlashScan to log 25 as a place holder for the invalid data.

Regards
Paul

[vxleather]

Will give it a try as soon as i get a chance thanks for the promt..

Shane

[vxleather]

Okay cant find the pid you are talking about!! Blacky,

I did find "External WideBand Sensor State" EXT.W02ST1 is this what you mean, or am I on the wrong path here...

Have attached a log with this pid being logged...

Shane

[Blacky]

Yes, that was the PID I meant.

See how that PID goes to zero and the AFR goes to 25.00. The AFR only goes to 25.00 because the STATE PID is not "Lambda".

Now, the question becomes why does the state change from "Lambda" to something other than Lambda. The only reason I can see is that junk data is being received by FlashScan. Junk data could be caused by noise on the serial line or a bad cable, specifically the ground pin.

1. Make sure you are using a shielded cable.

2. Make sure the ground pin is connected properly between TE's serial port and FlashScan's serial port.

3. Try running a three way ground wire to these points:
- Pin 5 of the OBDII connector.
- The ground pin on TE's serial port.
- The ground pin on FlashScan's serial port.

Regards
Paul