______ 
 |  ____|
 | |__   
 |  __|  
 | |     
 |_|     
         
         

 __     __
 \ \   / /
  \ \ / / 
   \ V /  
    \_/   
          

  ____  
 |  _ \ 
 | |_) |
 |  __/ 
 |_|    
        

 __      __
 \ \    / /
  \ \  / / 
   \ \/ /  
    \  /   
     \/    
           
           

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

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:
Hallo I am from Denmark and I am planing to use a V3.2 on my VW Golf GTI 8V. MembersPage/HansK/IgnitionSetup MembersPage/HansK/EgoReadingProblems MembersPage/HansK/History ------------- 2005.08.09 '''Problems!!''' It started a morning 3 days ago, the enginge started duing strange tings (worse then reaching the rpm-limit) resulting in "bang" fra exhaust and a "jumping car", when reaching 5000RPM. After it been through the carwash it started fine but 10 minutes later it would not start. When it finaly started it was hard to keep running and MegaTune showed everyting from 0 - 8000 RPM, the fuel-pump relay was going crazy and so was my shift-lights..? After some time it got better and better, but It has been coming back :( I thought it was because of moisture the hall-sensor vas going crazy, but should I not bee able to see the "spikes" in a datalog?? In this datalog I was trying to keep the car runnig!! http://www.vems.hu/files/HansK/datalog200508072050.xls *MY 2 cents, without actually knowing what you have checked, and I'm no VEMS expert, actually, I am pretty usless, but my gut feeling as a mechanic for the last 13years would be check for water in the secondary ignition (dist cap, wires, sparkplug holes etc. depending on setup), check for good grounds (as well that the coil body is grounded), failing that, try a coil. The bad grounds is almost always the case when I have seen similar problems, but usually there are other indications like the vehicle tach going stupid etc. ------------- 2005.08.01 The engine has been running fine a few days now :))) The problen was a "air-leak" around injector #3 :o I added the original Bosch ignition-module so I have not been looking more on the dwell settings (they are both just 2mS). * Can dwell chance after RPM or some thing, or is it just the same all the time? ** Dwell depends on VBatt only. In the future we should add dependence on MAP (for enlarged dwell on "high boost") and maybe CLT and lambda ------------- 2005.07.28 As PeterJ also write my car has got a bad habit by starting "misfirering" (at least I think it is, because lambda does not go lean) after it has been runnig fine fore 15-25 min. or so. It is not when it get warm it starts but 5-10 minutes after it has reached the 90-95' clt (where it also stays), and it just get worse and worse until it get a break. But short break = misfirering again after short time, so it got to bee something to do with temperature, right?. Any ideas?? Too hot coil might cause similar behaviour. When i look at the data-logs Dwell is always 2, even though I set it to 3mS?? What does LCD show ? Maybe it's a vems.ini problem ? What is your VBatt ? ------------- 2005.07.27 '''??''' I was going to change en value in the Lambda-map when I noticed that when I chanced the value down (towards lambda 0,9 (richer)) MagaTune road wrote "leaner". This is just the "note" being wrong,right? Check the table printed out by "Man" "mct" to be sure. 0x38 is stoich, above 0x38 it's richer. below 0x38 it's lean. lambda = 256/(200+ lambdacorr) Yes I did it right then.. Thanks ------------- 2005.07.26 '''It is running :)''' I installed all the wires and stuf this weekend and after recharging the batteri it started yesterday evening. I have not had the time to tune it properly yet, but I have a few thins in the config im not so sure about so please put a comment to this (I use the original hall sensor and distributor): primary_trigger=03 # this combination is not really used, We use filtering with coil-type trigger (07). Actually, traditionally we use FF for rising edge (same as 07, the higher bits don't care) and FE for falling edge secondary_trigger=02 crank_minper=FF # "Cranktrigger min. period [16 usec]" is way too high (where did you see this?), use 60 or so. Period times (period=180 crankdeg for a 4 cyl) shorter than this are considered bogus (trigger error) so this value should be below the period times seen at max RPM The values below don't matter for coil-type trigger without camsync. tooth_wheel=02 trigger_tooth=0A # ? another_trigger_tooth=12 # ? tooth_wheel_twidth1=B4 # ? tooth_wheel_twidth2=FF # ? cam_sync_r_edge_phase=FF cam_sync_f_edge_phase=FF reset_engphase_after=D8 # ? ------------- 2005.07.16 * MAPdot should be fine with any recent firmware Q.2)When i open my Lambda Table in MegaTune (r18 and Firmware 1.0.12) the numbers are all wrong.. http://www.vems.hu/files/HansK/Lambda_Table.jpg I can get the same numbers out of the board again with the Terminal-program as I put in.. But they don't show in MegaTune? The lambda-tuning works good with recommended latest released firmware (GenBoard/UnderDevelopment/FirmwareChanges currently v14_rc1) and latest MegaTune (verify with mct that MegaTune vemsv3.ini is acting properly). '''Yes''' It works again with the new firmware and MegaTune r23. Q.3) If I download the new Firmware 1.0.14 to the board, I want to to do some new testing on the table but now I mounted all the transistors in the box.. Should I just put a lightbulb on all the outputs or what to do? yes. Actually final testing is done after mounting the TO-220 FETs and IGBTs and clamping them to the Alubos (the IGBT-s can short to neighbor or case if not done right). Likely you have a few econoseal recepticles that you can hook up. * OK, but don't there have to be something connected to FETs and IGBT outputs? ** the FETs and IGBTs are not at risk when nothing is connected to the output. In fact most setups run with typically 2 IGBT-s connected (4cyl wasted spark), while often 8 IGBT-s are installed in an assembled ECM. However, testing with some load is nice, because it provides more information: someone reported that after he killed a FET with short-circuit output to 12V (without a sufficient fuse) the FET still switched a few microAmperes and looked OK with the DVM as only load: they had no power to switch on even a small 0.5A lightbulb load though. ** poweroff test: with DVM measure ohm (or diode-mode) between EC recepticles of neighboring IGBTs (or between any 2 IGBT outputs if you are lazy to look for neighbors: this is 8x7/2 = 28 measurements, takes 2 minutes with DVM, especially fast with beep mode) to see that none shorts ** We apply LEDs and series resistors between output and 12V supply (or 5V supply OK too, eg. EC36pin28 or EC36pin29 suitable as well). Than apply mdh commands (see GenBoard/Manual/DigitalOut/Table) to see that outputs switch on/off as needed. Take care that ..._channel=FF in config during this session, otherwise the output will be what the firmware thinks appropriate for that channel. ---- Please post your config.txt so that others can review and hopefullly learn (especially me ;) Thank you. http://www.vems.hu/files/HansK/Config.txt It is not in use yet so don't put too much in it, but you are welcom to give input. ------------- 2005.06.19 Q.1) I have a 2-pin idle-valve, but what settings should be used fore this.. PWM, ON/OFF? Any solenoid works with ON/OFF. Only some work (well) with PWM. ** what is resistance ? ** anything known about original application? Does it have real idle-air control or just simple "fast-idle" ? Does some one use the the same valve, and have a config-file that I can see or just some input to what settings to use? http://www.vems.hu/files/HansK/P6220090.JPG Q.2) Is there some way to test the idle-output? ** which output did you choose in iac_sol_channel ? ** PWM type iac output can be tested with forced iac.position: mdi01..mdiff . Do NOT forget to set back to mdi00 (or reboot) after you executed the tests to revert to normal control. ** alternatively it can be tested like any other digital output, with mdh.. command. See GenBoard/Manual/DigitalOut/Table. In this case, do NOT forget to set iac_sol_channel=FF to prevent interference and set it back after the test. 2005.06.01 I got the new Megatune "mt-r014" and I tryed to use the firmware that was together whit it, but then I got no "output" on inj. or ign. and the the config and table was the same..? '''No problem..''' Just needed to chance secondary_trigger to "02" instead of "FF".
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.