____  
  / __ \ 
 | |  | |
 | |  | |
 | |__| |
  \____/ 
         
         

___  ___
|  \/  |
| .  . |
| |\/| |
| |  | |
\_|  |_/
        
        

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

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

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

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 The vemstune version 0.10.80 (2011.11.15) I tried 3 different driver version but it didnt want the true. I installed 4th driver . (PL2303_Prolific_DriverInstaller_v1417) wherewith it can connect. But its not 100% perfect. When disconnect the ecu it cant reconnect. One way to reconnect. close vemstune -> disconnect the usb connector and reconnect -> open the device manager, and i must to change the com ports number from com9 to comX. -> save the config. -> open the vemstune, -> add suply to ECU, detect ecu on comX port. it cant connect yet. -> supply off. in device manager the com ports number change back to com9. If i do it the ECU can connect. I think this driver not the best but i didnt find better. I think i will reinstall my Op.system. * I reinstalled my op.system so it became perfect with v1417 driver. ---- My car: Audi 1.8 8V 90ps carburated with vacuum-hall ignition. The plan to vems: "New" 1.8 GTE 112ps cylinder head. It has a bigger valves, and ports with injectors. (Maybe later i will try this config with a low boost (~0.4bar) turbo with k16, or k03 charger.) V3.7 unassembled genboard. Firmware 1.1.96 MPX4250AP 250kPa MAP 4x IGBT 9X FET IDLE driver 4x20 green LCD BOSCH TPS Audi S4 AAN harness with JPT55 connector. * 12-1 only primary CAM-HALL trigger (like in the picture). Is it good for "COP" ignition? And which ones hall sensor to work with it? Only 1GT101DC? http://www.vems.hu/download/sensors/triggerwheels/VEMS_12-1_trigger_wheel_Honeywell_1GT101DC_HALL_sensor_m.jpg The coils like that: vems.hu/files/MembersPage/NanassyPeter/PIC/P1020164.JPG * The vemstune doesnt allow to use 4 ignition outputs with these settings: Primary settings: Edge: Falling Type: Missingtooth Missing tooth type: N-1 Spec: Normal TDC After the trigger: "40.0" Number of teeth: 11 First tooth: 0 Next tooth: 6 Angular width: 30.0 Secondary: disable Whats the wrong? 4x 350ccm/4bar ~16ohm Bosch injector from S4 AAN * PWM Bosch type idle motor. Should i use like this contact? ->http://www.vems.hu/files/Norbitron/iac.jpg Or should i joint the power flyback? http://www.vems.hu/files/Marteleur%20Tim/flybacklead.JPG
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.