#    #  
 #    #  
 #    #  
  #  #   
   ##    
         

 _______ 
(  ____ \
| (    \/
| |      
| |      
| |      
| (____/\
(_______/
         

 _   __
| | / /
| |/ / 
|    \ 
| |\  \
\_| \_/
       
       

  _____ 
 |_   _|
   | |  
   | |  
   |_|  
        

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

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:
||MembersPage/Sascha/JPDiaz|| '''From Aug 2014''' Issues with lambda getting "stuck" at 0.83 Issue with lambda getting stuck when doing a power pull, issue started out of no where and consistently getting worse so the point that I can no longer read lambda under large loads. Wiring has been checked, and re-checked... Sensor is new. Sensor had a hard time to calibrate at the beginning (seemed like heater wasn't activating correctly all the time under calibration) I had to start/stop the calibration process a few times in order to get the O2 heater activated for free air cal. Seemed to read fine otherwise and is accurate under light loads @ idle. Screen shot of log: https://lh3.googleusercontent.com/-PXarbxmwzf0/U-ETDvLJ1lI/AAAAAAAAX5E/kiRoSY0Sm58/w1317-h681-no/jp-log-lambda-stuck.jpg Lambda sensor eventually recovers in approx 2-3 seconds of overrun: https://lh4.googleusercontent.com/-PIzTVd8e_Zw/U-EWczHTrbI/AAAAAAAAX5U/m_ilyylYQ50/w869-h767-no/jp-log-lambda-stuck-recovers.jpg ---- '''Update - Aug 2016''' Late last year the owner replaced the WBO2 w/ a new sensor and let me know that it calibrated ok. I wrote the lambda issue off to the sensor after all. 2 Days ago, pre-test race w/ swapped to E98 (from E85) and I noticed the WBO2 was not working at all again. After numerous attempts of free air calibration with the new sensor, the original sensor and one brand new never used O2 sensor. All 3 sensors had the same issue. '''During calibration the heater would never stop heating.''' Checked wiring again, everything checks out, 12V source is good. I did not have my resistors with me to check the WB output from the ECU so I swapped to a known good ECU and the issue was solved. It's clear the customers ECU has a defect from HU. Unfortunately it is outside of the warranty period now, but I will be bench testing the ECU and hopefully can be guided to do the repair on the ECU. I'm hoping it is maybe just a bad solder point or driver/IGBT for the WB heater. '''UPDATE FEB 2017''' I have bench tested the ECU with the following results: Following test steps listed here: http://megasquirtavr.sourceforge.net/manual/Detailed.Sensor.Wide.html#Operate Voltage test / ECU ON / WBO2 ON (Heater): Pin 5 (pump -) + GND = 3.98V (no change to this when adjusting pw_zero up or down - w/ burn + restart of ECU) Pin 1 (nernst) + GND = 4.41-42V Pin 1 + Pin 5 = 0.445V GenBoard/Manual/WBSensorControllerTesting steps: Voltage Test / ECU ON / WBO2 OFF (Heater): pump- = 0.0V GND = -3.97V (again no change when adj. pw_zero) Voltage Test / ECU ON / WBO2 ON (Heater): pump- = 0.0V nernst+ = 0.445V pump+ = 0.910V All tests done with correct 100 ohm resistors as stated in the links. * '''tests seem OK''' * pump- value = constant 3.97V is perfect ( 4 +- 0.1V so well within... even more deviation would not cause any problem) ** it is constant, pump- should NOT change lower then recommended 4.1V and will not change up/down when adjusting pw_zero setting at all. * Sensor is not the problem ** how do we know ? * So issue must be related somehow to this ECU ** HW seems good (please measure that WBO2 heater output is not continuously pulling to GND, eg. measure between +12V and EC18/18 before and after ECU powerup) ** so '''perhaps some (wideband related) configuration'''. Perhaps RI target is too low ? (normally 165 .. 180, try 180) ** Include config (as in any report), or better: vemslog captured during free air calibration ECU SN: 8501 -----sometimes it happens that exhaust is blocked and then lambda fails Dave reviewed config, all defaults applied no config issues found * for '''any further diagnosys a vemslog of wb calibration''' (warmup from cold to operational running 1-2min after operational, engine NOT running, '''knock realtime data set to: individual power''') * IMPORTANT: use recent firmware (1.2.31 or higher) ** the config shows current firmware is 1.2.28 which does NOT log enough information for this problem *** Updated FW last night, set knock realtime data correctly, started WB calibration to ensure warm up... saved vemslog here: http://www.vems.hu/files/MembersPage/Sascha/JP/v3.3_u008501-2017.06.15-22.25.52.vemslog Please let me know the next step.. this box is still not working, where the other VEMS box works perfectly fine without issue with the same CFG and any FW.
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.