_    _ 
( )  ( )
`\`\/'/'
  >  <  
 /'/\`\ 
(_)  (_)
        
        

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

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

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

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

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:
'''v3/19769 sent for repair''' (2021-10-26). ECU '''communicates reliably, and no issue with inputs or outputs was found.''' * "fuel injector activated (not for a short time)" ** injector ouputs and all other outputs activate as they should. Tested with test config. '''Most likely the problem is caused by configuration''' * however, more details about the engine and harness are needed so we can give tailored advice related to configuration. See [http://www.vems.hu/files/MembersPage/UnknownFourCyl/v3.3_u019769-A-2021.10.25-VEVOE.vemscfg 2021-10-25.vemscfg Config file] (most likely problematic): ---- '''ECU communicates without any problem with good USB-RS232 adapter''' Most likely cause of any comm-problem is bad '''USB-RS232 adapter, or windows driver''' (or cable or USB port or similar) problem * "sometimes ECU cannot be reached" => with good cable: works 100% reliably * "some values couldn't be read out or implausible" ** perhaps related to USB problem. Otherwise some example vemslog would be interesting, with exact examples. Hello Marcell, i sent you an overview of the wiring with the ECU. When the control unit is supplied with power, the fuel infectors were activated 100% immediately for a short time and there was a real blow to the injection rail. Another problem was that the injection maps could be changed in the software, but the ECU did not accept or process them. This will cause too much fuel to be injected. Then we tried a ECU from a friend and it worked perfectly. Is it possible that you still change the mainboard and I will pay for the change? Motor setup: VW ABF 2L 16V G60 bore 83 mm connecting rod 159x21 mm stroke 92.8 mm 1700 cc injectors VW TFSI ignition coils red NGK spark plugs Optimized cylinder head Camshafts TK Motorsport ECU tuning by Kevin (VW Watercooled Racing) in Friedland Thank You, Michael ----------------------------------------------------------------- '''Old and new ECU sent, use old. (new only as last chance)''' New ECU is also sent, but only for last chance, and price of that is not included (in appr 150 EUR fee). Please * '''verify and fix harness''' * and preferrably use the __old__ ECU because it was reliably communicating during all tests, with inputs outputs behaving. '''If and only if your harness is really documented here __and__ verified''' * and still experience problems (which must be documented very exactly including ECxx pin numbers and values, without the word "some") * than pay +80 EUR and connect new ECU, * upload your config after inputs are good, and outputs also tested. * Please make the verifications and test in next few weeks, and '''latest on 2022-02-22 please send back new ECU (that hasn't been plugged in)''' ** (to Budapest address specified by crew) ** or send back old if the new has been plugged in, +80EUR must be paid in that case * (or keep both, and pay +400 EUR in that case)... Please carefully check that all 5 GND-s are connected, and EC36/23 flyback also. See the paper of the new ECU (apply to the harness). Plugging in new ECU without carefuly checking harness and documenting __and__ thorough verification is not recommended, and voids warranty. (As the old ECU also worked fine on test-bench but misbehaved in the harness, the new ECU will most likely misbehave or get damaged if plugged in without thorough harness verification or rework, so it is very important to do thorough checks). Even if it works with one ECU but not the other ECU, it is very likely the harness has some problem (and might surface in the future). We hope the thorough tests reveal something, and old will work well... But include the new so you have the option to try (without more delays), but - however tempting it might be - plugging in new is not the way to solve this.
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.