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

  _   _ 
 | \ | |
 |  \| |
 | . ` |
 | |\  |
 |_| \_|
        
        

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

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

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

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:
'''ECUs sent in for repair 2021''' '''10026''' Apparently a +5V regulator onboard has problems keeping up. First issue was an issue with no signal on the primary VR trigger input. The P259 was removed in an attempt to fix the problem as it is the usual issue, but it was not that easy. The ECU has a low-Z injector driver board mounted, remove it and let the board run only high-Z injectors if it helps the repair, as the low-Z capability is not needed anyway. I have no known history of this ECU, flyback wire might have been missing. ---- '''711''' * Sent this one in 2018 * higher current draw and no communication. * It has been used in a completely different install since then and suddenly stopped working again. Used with VEMS standard harnesses and replacement ECU have had no issues. Maybe board replacement? '''1284''' * Health check-up. Verify outputs,? inputs? and trigger working correctly. * Upgrade bootloader! '''4572''' * Health check-up. Verify outputs,? inputs? and trigger working correctly. '''8838''' * Bad engine ground. Maybe board replacement? '''12018''' * Lambda sensor not working due?to moisture in the connector shorting?+12V to inputs. '''17990''' * Ignition coil spark jumped from open spark plug (timing check) to a coil signal wire due to careless placement and communication was lost. * Maybe board replacement? ---- '''ECUs sent in for repair 2018''' '''2018-08-17''' Five ECUs sent in. Check function of the boards and report back any issues, or return to me if healthy after quick fix. I authorize mainboard replacement if necessary in all cases. * ''What was done/fixed with these ECUs?'' ** Especially wondering about 3396. ** Never mind 6114, it was replaced with 14497. '''711''' * 300+ mA current draw * No comms '''3396''' (Audi pnp) * Communication initiates and disconnects immediately. * A couple of things have happened. ** The battery had been drained, and the customer claims the car would not start after the battery was replaced. I have a feeling they might have used start help and caused over-voltage or other issue. ** Earlier the intake temperature and IAC connector might have been switched around once, which fried the sensor, which was replaced. '''4600''' * Received this through 3rd party * No description of the probable cause. * No comms. * Simple test bench reveals high current consumption. '''6114''' * Received this through 3rd party. * No description of the probable cause. * No comms. * Simple test bench reveals high current consumption. '''12028''' * Water got into lambda connector, now seems to kill lambda sensors and analog signals (MAP, maybe others) show bogus values. ---- '''11440''' * Power touched bare wire on RS232 port (connector without housing) and customer has has intermittent communication since that time. ** EC18/17 GND trace was cut (for no obvious reason, also, not the solderblob unsoldered, weird). * Customer has tried different USB serial port adapters and in another car/harness as well. ** Almost certainly ground connection problem (RS232 sometimes "kinda works", but not reliable, see GenBoard/Manual/CommHardware). * My personal tests on my test bench show no issues, tried with a desktop computer with proper serial port and laptop with known good USB serial port adapter. ** definitely works with proper ground connection to DSUB9/pin5 * Perform your tests and report back. Even if you find nothing wrong, please replace the RS232 chip (customer request). ** On-site TODO: need to ''' check (and fix) the DSUB9/5 to EC36/26 signal ground connection''' (important), otherwise it will not work reliably. '''4153 and 4254''' * Have recently been returned from you but it is as if nothing has changed, you still can not get a lambda signal. * The current draw from the heater is only a few 100 mA and the sensor doesn't get hot to the touch. ** are you sure it's not the heater +12V or similar (sg in the harness) ? The heater - FET output was tested with >1A load ** My test bench harness is simple and robust and used for calibration and testing. I use a 100W laboratory switched power supply where I can monitor voltage and current (and limit them if needed). Healthy ECUs heat the lambda sensor just fine in this setup and use 1+ A and these ECUs hardly get use 300 mA, of which 150 mA is just the ECU current draw. And don't forget, they were sent to me specifically because moisture got into the connectors and the signal was lost. When they were returned to me and still not working I ran tests with other sensors and ECUs just to verify that my setup is working, and it is. * As described last time, both ECUs has lost the wideband signal after moisture got into lambda sensor connector. * My guess : Voltage from the fused power has probably trickled into the other pins in the lambda connector and damaged the input/control circuitry, and/or possibly the heater FET as well. Please try free-air calibration with a real sensor (it doesn't work) and report back what you find in Wiki. * Please add 27k nernstpullup resistor to enable LSU 4.9 support if you get them working. * Board replacement granted in worst case scenario ---- '''ECUs sent in for repair 2017''' All of the ECUs listed below will not be used in the projects they came from. I've replaced the ECUs already and fixed any/all issues that caused the problems. Check function of the boards and report back any issues, or return to me if healthy after quick fix. I authorize mainboard replacement if necessary in all cases. '''3399''' * Stepper chip removed by customer after short in the coil harness (heat radiation). * PCB damaged around stepper chip, do not replace chip - just leave as is. '''4153 ''' * No lambda sensor signal after water came into lambda sensor connector. '''4254 ''' * No lambda sensor signal after water came into lambda sensor connector. '''4770 ''' * No lambda sensor signal after water came into lambda sensor connector. * ''Replaced by 17319'' IGBT 2+6, LCD, Knock, 1xEGT, VR+Hall, 400 kPa '''8098 ''' * Outputs shorted to power in standard BMW M50 harness (heat melted wires). * I removed one injector FET and one ignition IGBT that had shorted. * There could be more damages. * ''Replaced by 14365'' 2xEGT, VR+Hall, 400 kPa '''10115 ''' * ECU has never been used, only test bench. * It has the bootup/reset problem. I tried the simple fixes with components sent by Marcel but it did not help. ** www.vems.hu/download/v3/doc/assembly/v3_mainboard_resetChips_variants.pdf * ''Replaced by 18357'' LCD, Knock, EGTx2, Hall+Hall '''11820''' * Stepper output shorted to +12V in harness (yes resistor in series now in place). * Symptom is a 250 mA current draw, no VR trigger, possibly damaged P259. * ''Replaced by 17039'' LCD, Knock, 1xEGT, VR+Hall, 400 kPa, SD Card removeable '''14821''' * Same as 11820 * Stepper output shorted to +12V in harness (yes resistor in series now in place). * Symptom is 250 mA current draw, no VR trigger, possibly damaged P259.
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.