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

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

  __  __ 
 |  \/  |
 | \  / |
 | |\/| |
 | |  | |
 |_|  |_|
         
         

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

   ____ 
  / ___|
 | |    
 | |___ 
  \____|
        

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:
Subpage of MembersPage/BorisRieken '''Opel C20NE engine''' '''Warning: DO NOT TRY TO START YOUR ENGINE until you understand and measure the integrity of flyback and grounds''' See MembersPage/PhatBob/UserGuide * engine code: C20NE. similar to C20XE and C20LET. ** Describe your engine. Really. Don't expect others to know your numbers. * Some people run it with VEMS. Can I use their config.txt? ** yes, if they have the exact setup (with exact same outputs chosen, like ignition and injectors as well) * 4 cyl * 16valves * 2L * 60-2 crankwheel VR * wasted spark * turbo / NA ? * anything special ? ---- * I need to know step by step what to do ** if you want help, you need to document your install, step by step. Every part of it. How it is connected (and verified). How you verified connection. What you measured between what * Is there enough information on my MemberPage to make a config.txt? ** Currrently NO Forget essays that talk about everything yet tell nothing specific. Forget collection of questions. For every question, you need to have explained your particular setup of the given subsystem (usually 6..10 bullets). Make separate subsections (or even separate subpages) for each subsystem. Don't let subsystems mix. Find at least 4 installs from MembersPage that are split to min. 5..6 pages. Read them. * MembersPage/DavidBlades * MembersPage/GergelyLezsak * MembersPage/MarcellGal/EngineSwap ** http://www.vems.hu/files/MembersPage/MarcellGal/EngineSwap/etc/config.txt ** http://www.vems.hu/files/MembersPage/MarcellGal/EngineSwap/etc/tables.txt ** This daewoo engine might be very similar to your opel engine, but only a starting point, because of different outputs used. h[2] must match your ign outputs, *** also check h[0] to match your injector output setup ---- '''Ignition outputs''' passive wasted spark coil. As on GenBoard/Manual/DigitalOut/Table * EC36pin34 ignch2 - cyl1,4 ? * EC36pin36 ignch3 - cyl2,3 ? The passive coil has a common +12V, Use a 7.5A fuse. For 1.0.53 firmware, this means either * h[2]=02 03 02 03 .. .. .. .. or * h[2]=03 02 03 02 .. .. .. .. Will be right. See "Missing tooth position" below. * Note that 1.1.x requires different h[2]=20 30 20 30 .. .. .. .. or h[2]=30 20 30 20 .. .. .. .. because that also allows ign via stepper output. But neglect this for now (just don't be surprised if you find this in a very recent setup) ---- '''Missing tooth position''' Very important to know this, especially if you have no timinglight. The tooth right after the missing tooth is tooth 0. Which cylinder TDC comes next ? How many tooth after tooth 0 ? ---- '''Primary trigger''' * 60-2 tooth wheel (that is 58 teeth) ** another_trigger_tooth=1E (next trigger tooth = 30) * VR sensor ** VR+ is connected to EC36pin27 ** VR- connected to EC36pin26 '''Sensor resistance ?''' Usually 400 .. 600 Ohm. '''Measure it !''' Beware that the Opel VR sensor is often marked with reverse polarity in factory manuals (probably the bosch ecu reads the rising edge of the VR signal, while VEMS reads the falling edge with the LM1815 VR signal processor) * Connect a DVM (200mV DC mode) ** DVM- to VR- (EC36pin26) ** DVM+ to VR+ (EC36pin27) With standard bosch wheel (do you have a photo?), you know that your sensor polarity is right: * When you put a ferrous metal (wrench) to the sensor, you read + few mV * When you take the wrench away from the sensor, you read + few mV The reading just lasts for a very short time, a few 100 msec, when the movement takes place. If you can confidently do this test, you can skip the slightly more sophisticated InputTrigger/TriggerLog. If you like to do that anyway, binary triggerlog can be captured in 3 minutes, than upload the binary file so we can evaluate for you and find if your VR sensor is connected with correct or reverse polarity (Boris 02-01-2007): Primairy trigger info on MembersPage/BorisRieken/PrimairyTrigger ---- '''Secondary trigger''' Not needed for wasted spark. Disabled: * secondary_trigger=02 ---- '''sensors''' TPS, IAT, CLT is responding nicely. * calibrate TPS now. Calibrate IAT and CLT later (if you care), when engine runs. ---- MembersPage/PhatBob You need to use a timing light to check the spark timing is showing the correct adavance (which is determined by the cranking advance setting). Make sure that there is no power going to the injectors so that the engine doesnt flood. '''Yes, possible to start my engine without timing light''' Have a read of this: http://vems.hu/www.vems.co.uk/VEMSLoom/LoomGuideUnitNNN.doc As it covers the starting proceedure '''Cannot read the .doc file (tried MS Office and OpenOffice)''' ---- '''Information from Webshop''' *Board version=v3.3 *Serial_nr=709 *pump-=4.16V * '''wbo2_pump_pw_zero=0x67''' that is decimal 103 *wb02_nernstdc_target=0x85 *pump+=-1.5mV/200 Ohm *AREF=4.9V *(C103=1nF, no D100) ---- '''Wiring''' ||'''Signal'''||'''ECU Pin'''||'''Comments'''|| ||Primairy Trigger = VR ||EC36Pin27||No signal in Megatune|| ||Secondary Trigger = Hall||EC36Pin13||Don't need this in the beginning|| ||CLT||EC36Pin14||Gives signal in Megatune. Not calibrated|| ||IAT||EC36Pin02||Gives signal in Megatune. Not calibrated|| ||Injector 1||EC36Pin07||Not tested|| ||Injector 2||EC36Pin19||Not tested|| ||Injector 3||EC36Pin08||Not tested|| ||Injector 4||EC36Pin20||Not tested|| ||Coil Cyl 1-4||EC36Pin36||Not tested|| ||Coil Cyl 2-3||EC36Pin34||Not tested|| ||Fuel pump||EC36Pin09||Not tested|| ||RPM out||EC36Pin17||Not tested|| ||TPS||EC36Pin01||Is working correct!|| ||MAP||Internal 250kPa||Seen it working correctly|| ||WB02||EC18 Connector||Did some calibration with Hyperterminal|| ---- '''Explain your exact subsystem setup so your question makes sense''' The key to clean page is not the table format. Actually, bullet format is better for questions. When you post a question about your fuelpump, you '''WANT TO''' * '''DO IT IN A SECTION THAT DEALS WITH YOUR FUELPUMP'''. Forget the collection of questions in one place. * '''tell everything you know about your fuelpump''' - eg. fuelpump+ switched by a 30A relay, the relay solenoid- controlled by EC36pin... With questions of enough detail it is possible to give good answers. Otherwise you'll likely get answers like "follow the manual". * What firmware to use? ** 1.0.53 should be fine to start your engine * How to test if VEMS can activate my fuelpump? ** disable the fuelpump in config (eg. MegaTune) and issue mdh.. according to GenBoard/Manual/DigitalOut, GenBoard/Manual/DigitalOut/Table . Eg. if fuelpump relay controlled by EC36pin6 =Inj G than have *** h[0]=.. .. .. .. .. .. 40 .. (which is the entry 6 from the 0..7, and is written as decimal 64 if viewed in MegaTune) *** and mdhe0, mdh60 will turn your pump on and off. * How to test if spark plugs will spark? ** mdn03 mdn02 mdn01 mdn00 * Can I test injectors before trying to start my engine? ** yes, you can. Well: ** If you think about injector outputs, you should ** if you think about injector wiring, you should ** if you think about injectors (which I doubt), than no. Injector flowing bench is out of the reach of most installers
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.