_____ 
|_   _|
  | |  
  | |  
  | |  
  \_/  
       
       

 _   _ 
( ) ( )
| `\| |
| , ` |
| |`\ |
(_) (_)
       
       

 _     
( )    
| |    
| |  _ 
| |_( )
(____/'
       
       

         
         
 ##  ##  
 ##  ##  
 ##  ##  
  ####   
   ##    
         

         
         
  ####   
     ##  
  #####  
 ##  ##  
  #####  
         

IMPORTANT: enter the case-INsensitive alphabetic (no numbers) code AND WRITE SOME SHORT summary of changes (below) if you are saving changes. (not required for previewing changes). Wiki-spamming is not tolerated, will be removed, so it does NOT even show up in history. Spammers go away now.


Visit Preferences to set your user name
Summary of change:
New ECU (v3/10581 AAN) installed and updated the config * can you detail the "updated the config" ? Or perhaps provide the "updated" .vemslog or .vemscfg for review) ? ** 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 * IS there any cure for this? Is this some kind of ECU noise that is reflected in my dash? I need this fixed and corrected as it may cause longterm problems with my dash on parts that are no loger available ---- Today i also tested the lamda sensor as my VE table '''showed it was too rich''' * the VE table is a configured set of constants it does not change... ** 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. * If you care to mention, what was shown O2 % value with wbo2_cal=255 ? * Can you share your measurement of the sensor '''Rcal = ... Ohm ?''' * i am a car owner, and im afraid i have no means to measure what you ask. I can only tune the ECU that is what i have learnt to do. Unfortunately i expected VEMS to be able to provide me with the ECU with all hardware ready to go and for me to tune and adjust the maps to my setup. ** 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!!!! * note that if WBO2 calibration is lower than optimal (eg. not calibrated, or maxed out), the WBO2 reading is still REPRODUCIBLE. ** It just means that lower deviation from 1.0 lamda is '''displayed''' (lower than the real 20.9% O2 value is displayed; and higher than real lambda value dislpayed: eg. 0.95 instead of 0.94, or 0.9 instead of 0.88 ... ** it does not even prevent closed loop feedback EGO/lambda mixture control (just the values would need compensation). *** 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 * the sensor might be faulty (we do NOT heat the sensor, the sensor is tested by the manufacturer - Bosch in this case). * or perhaps the SSC5-LSU4.9 small loom might have 2 wires swapped, or perhaps all mirrored ? (we test the v3, and the manufacturer of the loom tests the loom, we just supply that from the shelf). * we test the v3 carefully before sendout, but of course nernst or pump HW problem cannot be completely ruled out (or misconfiguration, which we should verify also from vemscfg / vemslog). 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 [https://shop.vems.hu/catalog/lsu49-wideband-sensor-p-193.html LSU4.9 pdf]. * DC voltage between '''pump-''' and GND ? (4V or so) ** SSC5/ ... ? loomwirecolor/sensorwirecolor ? * DC voltage between '''nernst''' and GND, if 1k (or other, 1..100k documented value) resistor is connected between nernst and GND ? Near 1/(1+27)*5V = 0.179V ? ** SSC5/ ... ? loomwirecolor/sensorwirecolor ? * DC voltage between '''heater+''' and GND ? (12V or around?) ** SSC5/ ... ? loomwirecolor/sensorwirecolor ? * DC voltage between '''heater-''' and heater+ ? Can you see the sensor internally glow to cherry-red and get warm, and slightly smell while the voltage climbs up above 6..9V when WBO2 calibration is started ? ** SSC5/ ... ? loomwirecolor/sensorwirecolor ? * optional measurement if NOT already diagnosed by the above. DC voltage between '''pump+''' and pump-, with 100 Ohm between pump+ and nernst; and 100 Ohm between nernst and pump-? ** SSC5/ ... ? loomwirecolor/sensorwirecolor ? ----- Hello VasilisP, To determine what is going on please provide a bit more information, please answer the following questions for me: * are you using a new (or old please specify) lsu 4.2 or '''lsu 4.9''' probe during the free-air calibration and is it in free-air not in exhaust ? ** 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. * is your wiring from ssc5 to wideband connector verified and known good ? ** 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 * when trying to calibrate your sensor, does it get warm ? ** It does * could you make a vemslog of wideband calibration warmup cycle (let it run for 4-5min) and add the vemslog to your page here for review. 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
Optional: Add document to category:
Wiki formatting: * is Bullet list ** Bullet list subentry ... '''Bold''', ---- is horizontal ruler, <code> preformatted text... </code> See wiki editing HELP for tables and other formatting tips and tricks.