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

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

  _____ 
 | ____|
 |  _|  
 | |___ 
 |_____|
        

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

_________
\__    _/
   )  (  
   |  |  
   |  |  
   |  |  
|\_)  )  
(____/   
         

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:
Hello! I assembled my new board into a motronic box with motronic55 connector. I think this pinout is ok from Econoseal to Motronic55. This harness from S4 AAN. http://www.vems.hu/files/Norbitron/econoseal-motronic.xls ---- '''Serial connection''' I tried to connect my ECU to the PC but ... * Found the problem: serial port is wrong (it doesn't want to communicate anything, i don't know why) ** I bought an rs232->usb converter. With that the ECU can connect to my computer. * I am not sure that the serial port was wrong. When i tried the usb-serial converter i just connected the ECU and i didnt test it. ** test the serial port with terminalprogram and loopback wire (and measure voltages to include in any report) * When i would try to connect the vemstune it's write me " ECU not connected" and the vemstune freezes ** when VemsTune freezes when opening the port, it's actually the windows driver that freezes (unfortunately usb-rs232 drivers often freeze, especially from Prolific) ** instead of "Detect", see "Device manager" and select the actual comm-port you have connected. This can avoid wasting time and running into windows and device problems and delays when opening unrelated serial devices (like GPS/bluetooth phone/GSM/etc...) ** you can check for "electric contact problem" but the root cause is usually a windows driver problem (in linux the same HW just requires a reopen and works, in windows the user usually has to pull the USB). However the windows-driver tends to freeze more if the usb-serial chip resets (often seen first when one starts to fire sparkplugs), so re-doing connections (with shielded cable) and stronger ground can also help Using * prolific serial-usb driver (which prolific driver version? Tried some other/older/newer version ?) * and vemstune latest version (it does not matter in this case but the word "latest" is not good in reports. Use exact date !) In 99% of cases it's the '''prolific windows-driver problem''' that causes symptoms exactly like yours. * if TerminalProgram also fails to communicate, than you know 100% that it's not VemsTune but windows-driver related: ** after closing VemsTune (if windows blocked the program too heavily, then kill it) ** in 19200,8n1 open port and type "SManmdV" ** or use a pin2-pin3 loopback wire (or metal-contact, but carefully) on the DSUB9 connector, and see that it appears what you type ** while windows-serial drivers often freeze and block the program accessing it, the TCP driver is very stable: so if one cannot fix windows-serial-driver, avoiding it can be a good solution by using an external tool for serial => TCP: OverTCPWifiModule, OverTCPWireless
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.