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

 _____ 
/  ___|
\ `--. 
 `--. \
/\__/ /
\____/ 
       
       

 _______ 
(       )
| () () |
| || || |
| |(_)| |
| |   | |
| )   ( |
|/     \|
         

_________
\__   __/
   ) (   
   | |   
   | |   
   | |   
___) (___
\_______/
         

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

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:
Checklist of major steps (of a successful install). Skipping any of these steps makes support impossible or ineffective, and adversely effects the chances of success and happiness. * '''MembersPage''' (preferrably with 4..5 subpages for subsystems) ** project page is '''required for tech support'''. (otherwise optional) * '''pinout mapping (usually .xls)''' ** [https://shop.vems.hu/ Webshop] can wire ECxx pins to mot55 or mot88 pins based on xls. (similar to Audi 3B engine). ** installer can build custom harness, or customize [https://shop.vems.hu/catalog/universal-harness-c-1_24.html generic harness] * verify/measure/test * InputTrigger/TriggerLog * find '''similar engine .vemscfg''' (or .vemslog) and '''adjust''' (according to wiring; differences) ** refer to the information being used eg. the exact wiki pages or sections of [https://www.vems.hu/vt/help/ VT help]. Never assume that others see the same as you without referring exactly * check that the '''plans are as detailed as possible''' ** (number of cylinders, firing order, trigger type, type of ignition transformers/coils, wiring, vemscfg ...) ** ask for '''review''' (if it hasn't happened automatically; often you find suggestions as you go along documenting your plans, install and measurements) * '''start engine''', capture logs * '''tune''', capture logs If there is some project page with engine information, references + pinout mapping in xls, techies can review, make recommendations. * if a project follows these lines, the probability of success in reasonable time is great (and chances of hidden problems are small) => makes it possible for '''installer and tech support crew to see the exact same set of information and cooperate''' ** otherwise expect '''response : continue along these lines''', fill in the missing bits ---- '''Notes, hints:''' * Use real PC with 14" .. 65" screen ! ** Android and I-phone is no substitute for a real computer. Wastes a lot of time, and often stands in the way of effective work, really * sometimes use paper, take notes ** make sure the '''spreadsheet and project page''' is '''updated soon with important notes, measurements, changes'''
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.