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

  _     
 | |    
 | |    
 | |___ 
 |_____|
        

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

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

   ___ 
  |_  |
    | |
    | |
/\__/ /
\____/ 
       
       

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:
Box nr. v3/17302 DBW '''After fw upgrade and reboot serial connection lost (and could not recover).''' Most likely install/wiring docs and following instructions (eg. GenBoard/Firmware/BootLoaderLoopback ) could help, but replacement was sent. Orig spec (oid13684) - for replacement to be made. Checked. (note: more important to check and confirm spec, than sending old device to HU) '''ECU VEMS V3 DBW''' * MAP connection: 115kPa ('''Simple nipple''') * ignition driver: 0 IGBT * primary_trigger: HALL * secondary_trigger: HALL * EGT input: 2 * '''ETC BridgeOutput_Interface: 1''' (used with standard BridgeOutputDriver , SSC6 conn ?)'''Yes Standard''' * Knock input channels: 2 * Flyback: HighZ-only 30V flyback * mounting-style: flanged case * Hi-side PFET outputs: 0 * withSDcard: no * LCD connection: no * 1-wire interface: no * '''DUAL Wideband sensor''' v3/17302 '''replacement => v3/17468 sent with oid14543 ''' * Extra connectors (EC10 or whatever) was not specified during the replacement request so examine the papers, especially any extra connectors: ** verify carefully against install/wiring docs (also not provided). * Please take ESD precautions during handling and install, to avoid elevated risk of device damage. ---- 05-07-2018 I think this AVR is dead and i can think of to solutions to get the car running: 1. I send the box to .hu for repair express 2. vems.hu send a replacement box asap What do you think? Measured serial * '''ecu pin 2 to gnd = -8,46V''' (not connected). ** Are you sure ? Maybe -8.46V ? * pc pin 3 to gnd = -6,49V (not connected) ** Are you sure ? Maybe -6.49V ? '''Was this in bootloader mode apparently? Or ...''' Yes loaded bootloader.Hex ISP and Measurement is made after this. * '''Measured c7 = 4,9V good''' * '''Measured c5 = 0V (AVR pin62 AREF)''' hmm... Should go up when firmware starts ** Was this in bootloader mode apparently? Or ...? Any sign of ECU actuating (eg misc outputs, or LCD, or inj / ign ?) ? Is there '''anything''' else I can try? * '''Supply current (thru EC36/pin25)''' = ... mA '''Measured 0,13A''' ** This INDICATES (strongly suggests) '''v3 is in bootloader mode'''. It is '''easy to upload fw'''. See GenBoard/Firmware/BootLoaderLoopback ** new device being manufactured and sent before old arrives (you can '''keep old for +1..2 months''', some chance it turns out in the meantime that it's just fw to be uploaded, or accidental short or similar happened during home-disassemble, or something simple), so take your time ** easiest to remove the fuse and close with the DVM in 2A or 20A mode * '''MAX232 / Pin6''' (C57, -8V expected) '''Measured -7,60V''' * '''MAX232 / Pin2''' (C60, +8V expected) '''Measured 8,60V''' * MAX232 / Pin1-3 and 4-5 are "pumping", can only be measured with scope, not with DVM (but not interesting if pin2 and pin6 are good. ---- 19-06-2018 We did flash the ecu but no serial communication. Did load boot.hex and set all fuses. before flash VT could see the ecu? Maybe there is something wrong with a part of the AT128. Is there anything else we can tray? Thank you for fast support 16-06-2018 New Serial connection problem Need help Box nr. v3/17302 DBW Car Supersaloon LS2 1000 Nm End user saved config from old (2017) ecu and uploaded to new ecu. Perhaps we could review that config ? I will upload it later was it uploaded to 1.2.31 firmware ? or 1.2.38 fw ? He did not do a firmware upgrade so believe it is 1.2.31. Using a new Vemstune, after "upgrade ini from web" ? Was VT "upgrade ini from web" as recent as the fw or newer ? What was the exact VT version ? I think they used latest stable from 2016 and did not do a ini update. you know, we could try to reproduce, but the very config would be very essential... After reboot he could not get serial connection. GenBoard/Firmware/BootLoaderLoopback is the '''first to try''' to go to bootloader (which allows testing serial conn, or verify or upload fw). Helps 99% of cases (even if fw or config uploaded is severely problematic in some way). Can you try it ? I have tested but no luck. measure voltage on DSUB9/pin2 (from ECU) and DSUB9/pin3 (from PC), just in case. replacing any IC (or even disassembling) only (only after some more diagnostics) as a last resort (very rarely necessary) can we, maybe think of some similar environmental circumstance (high voltage from an USB-RS232 adapter ?) similar to v3/17956 ? VT says ecu found and when it start to load pages it stops at page 1. Then ecu disconnected - no ecu found. Replaced max 232 but no luck. Car and team must be racing at 22-06-2018. How can we help them ASAP- new ecu-isp firmware flash or any other help will be great. Do you have ISP hardware ? (eg. "bsd" cable or '''"usbtiny"''' cable ?) I have [https://shop.vems.hu/catalog/cable-p-165.html isp from webshop] but never tested it Thank you Peter
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.