VEMS Home Products Documentation Wiki Webstore
WikiHome ProjectPage DocsPage UnderDevelopment MembersPage SiteIndex RecentChanges Preferences
MembersPage/VasilisP/WideBandDiagnose (2015-09-03 15:57:44)

New ECU (v3/10581 AAN) installed and updated the config

  • When i say UPDATED i mean the VE tables which were last known to work. the HTA 12A config i asked you to use in order for the car to run propeply i expected you would have had the WBO2 4.9 checked, as the ECU comes with that WB sensor and not the old 4.2 which was in the config. I noticed that myself.
The 'update' was on VE and lamda tables that i had reviewed myself after recent checks.

Before the engine starts with the key turned to the pre-ignition state, my rev meter jumps to above 2000rpm and my dash warning lights up the LOW OIL LEVEL. Both stay up unless i start the car.

I have only connected the WBO2 sensor and nothing more.

Please tell me how to fix this problem and why it appears.

I have emailed a photo about this and a config at info@vems.hu

Today i also tested the lamda sensor as my VE table showed it was too rich

  • I mean i noticed that all my map was too rich when it should have been perfect from my previous tune (1.2.11)
  • Maybe the lambda reading and/or EGO correction indicated sg... what exactly ?
  • EGO was reading around 85 on all map regions
  • Too rich ?? (if wbo2 calibration is lower than real => lambda reading shows "not rich enough", instead of "too rich" )
  • When i calibrated the WBO2 for the first time the 4.2 was selected (as the config which was in the ECU had not been changed by VEMS) and i did not see that. I calibrated the lamda sensor and used 214 number to achieve a 20.9 air calibration.

after i changed the wide band setting to 4.9 and tried to recalibrate the lamda it went to 255 for me to have 20.1 at air.

Upon check and calibration, the 20.9 was NOT ABLE TO BE REACHED as it required a higher number than the 255 top value.

  • do you have another sensor (LSU4.9 or LSU4.2)?
  • I have a 4.2 lamda sensor lightly used. If i am to recalibrate should i clean it?
  • is it possible the sensor was dropped (eg. to concrete floor) ?
  • SENSOR WAS NOT DROPPED!!!!
  • So what am i supposed to look at to be sure that the correct amount of fuel is being used in all areas of the map?

I am now using my old VEMS and i can send this unit back for all necessary checks

I also tried 1.2.30 version without any success.

The key to success is measurements (even if just a few and simple in this case, they are important).

We suspect

If you publish the required (basic) measurements, and still not diagnosed the issue, then we'll send you LSU4.9 if necessary (a sensor that we might pre-test for you).

Besides the measurement, write the SSC5 pin number and the wire color for each pin (and the wire-color at the LSU4.9 sensor !), and verify connectivity and pin-correctness of the small SSC5-LSU4.9 loom according to the [LSU4.9 pdf].

Hello VasilisP,

To determine what is going on please provide a bit more information, please answer the following questions for me:

  • The first 4.9 lsu calibration (with the wrong selection on vemstune, 4.2 instead of 4.9) was done with a sensor completely new. The second calibration where the 255 was reached without being able to calibrate was done after the same 4.9 sensor was used with the car idling and myself looking at the trigger with a strobe light. So basically very little use.
  • My wiring is as sent from VEMS shop:
SSC5 1 WBO2 1 black

2 3 thick red

3 4 brown

4 5 blue

5 6 thin red

checked and verified

  • It does

Using the provided information i will provide hints on how to proceed.

Best regards, Dave

is the only way to add data here through dropbox? i have some logs already which i can share. i dont have one with the heating cycle but i can make one