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

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

______ 
|  ___|
| |_   
|  _|  
| |    
\_|    
       
       

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

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

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:
Alpha-N test page. ---- Find the problem. Had to change config13 to 04 manualy and then upload config. So now it works like before. Is it possible to change this bit in megatune? ---- '''Firmware version''' = -D "2004/11/24 16:00" The patch(es) that I made from the CVS head did not apply to Nov 24 firmware cleanly (that was the reason for the failed compile) Therefore I made this [http://www.vems.hu/files/Firmware/patches/alphan_against_nov24_good.patch alphan_against_nov24_good.patch] directly for Nov24 firmware (no need for the earlier patches, just start again from a clean cvs snapshot without the old patches applied): This patch works good, Thanks Marcell. =) Have not started engine yet but TPS now follow load as i should. ---- Problem: Alha-n tuning is not working ? Megatune ->useing MAP not TPS load the VE-Tables. Ini file -> vemsv3_v13_r021.zip, firmware -> 1.0.13 rc3 I commited the following to CVS STABLE1_0 branch, comm.c MTsendRTvar(): // high resolution MAP or load for AlphaN case 4: return (config.hybrid_rpm_m ? engine.kpa_tps_blend << 3 : engine.kpa250) >> 8; case 5: return (config.hybrid_rpm_m ? engine.kpa_tps_blend << 3 : engine.kpa250) & 0xFF; When AlphaN is configured, this is load instead of MAP, so MAP is only visible on LCD (if there is MAP signal at all). ---- The way to patch firmware: * go to the dir that has the firmware to be patched (eg. Nov.24) * make sure the .c and .h files are not corrupted (eg. by earlier half or badly applied patch) * and say: <code> C:\vems\firmware>patch -p0 < ....patchfile.location.... patching file `global.h' Hunk #1 succeeded at 177 (offset -1 lines). Hunk #2 succeeded at 500 (offset -2 lines). patching file `ve.c' Hunk #1 succeeded at 214 (offset -121 lines). Hunk #2 succeeded at 381 with fuzz 2 (offset -1 lines). Hunk #3 succeeded at 296 (offset -120 lines). C:\vems\firmware> </code> Than compile as usual * rm *.o or make clean * (sh) * make (make all) ---- I checked * tps_low tps_high seems OK * config13 bit2 = high (* MAP not applied) * hybrid_rpm_a = hybrid_rpm_m = 9600 RPM => alphaN applied "always" Sounds good. You could also check with * RPM > hybrid_rpm_m and * between: hybrid_rpm_a < RPM < hybrid_rpm_m (both MAP and TPS should effect) Change hybrid_rpm_a and hybrid_rpm_m for these tests if more convenient that way.
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.