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

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

 ___   
(  _`\ 
| ( (_)
| |  _ 
| (_( )
(____/'
       
       

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

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

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:
The same firmware and MegaTune that was used back in the old days for GenBoard/VerTwo (in 2003) should work today as well. Limited a bit, since * v2.2 hardware is just a bit more advanced than the original MegaSquirt, comes nowhere to v3.x * MegaTune was also harder to use with it's own tricks and watchouts * '''TODO:''' find latest working and tested ver2.2 firmware that compiles cleanly. ** as a last chance, try anonymous CVS from sourceforge ** making stable1_0 branch compile for v2.2 should be relatively simple. Start from a recent released (or a newer, yet unreleased if exists) from http://www.vems.hu/files/Firmware/release/ * always publish patches in diff format (made with diff command) * publish what the patch is against ---- Made a diff file for firmware version 1.0.18. look here http://kotisivu.dnainternet.net/sakrkorh/fw/ . Just commented out few things which I don't have any idea. Now it compiles but haven't tested yet. Boostcontrol is difficult to go around cleanly. ---- Working with MT-r027 release. See new diff in last link. Fw compiles and I can use MT to change all setting. Problem is that there is no signal on fet driver. Is there some new config setting that causes this? Please help with this problem. Do you have config and other logs, measurement data ? Most common mistake is to misconfigure fuelcut_min_kpa. Added config files same place. PW gauge shows in MT that there should be squirt, but there isn't. Tested fuelcut_kpa settings, it works fine and PW goes to zero when kpa is under min_kpa. There might be some erratic settings in config files. Also notised that poweron fuelpump pulse works but after that it doesn't give signal when there is rpm avaible. Maybe related to other problems. ---- Solved problems. secondary trigger weren't disabled. Updated new files to folder. Perhaps someone could implement this diff to all new firmwares. It's quick 'n' dirty but I think everyone should be happy. Atleast I am :)
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.