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

 ______  
(  ___ \ 
| (   ) )
| (__/ / 
|  __ (  
| (  \ \ 
| )___) )
|/ \___/ 
         

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

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

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

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''' '' [http://megasquirtavr.sourceforge.net/manual/Detailed.Control.Alpha.html#Operate [Manual: Detailed.Control.Alpha.Operate]] If something is not clear on this page, please check and understand GenBoard/UnderDevelopment/AlphaN and try to make this page clearer from what you have learnt. ---- [http://megasquirtavr.sourceforge.net/manual/Detailed.Control.Alpha.html#Config [Manual: Detailed.Control.Alpha.Config]] Note that it is highly '''recommended to place an RPM bin''' (r table) '''on both hybrid_rpm_a and hybrid_rpm_m''' (3200 and 4800 RPM in the example) because the tables will look strange (and possibly steep) between these columns. The reason for this is the smooth, continuous change (in the function input that selects relevant table-lines) from (the unusual, nonlinear, quite different from MAP) TPS signal input to the (commonly used) MAP signal between these RPMs. ---- [http://megasquirtavr.sourceforge.net/manual/Detailed.Control.Alpha.html#Operate [Manual: Detailed.Control.Alpha.Operate]] ---- '''How?''' I have no hybrid_rpm_a and hybrid_rpm_m. What to do? Using the 2004.Nov (production at the time of this writing) kernel needs a patch for this: * download [http://www.vems.hu/files/Firmware/patches/alphan_against_nov24_good.patch alphan_against_nov24_good.patch] * go to the firmware dir * issue patch command. See below how, with appr. output that you'll see. Anything like "failed to apply patch" would sound bad. <code> C:\vems\firmware>patch -p0 < alphan_against_nov24_good.patch 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). </code> ---- '''See also''' * [http://www.megasquirt.info/manual/mtune.htm#alphan MegaManual part dealing with tuning alpha-n] * GenBoard/UnderDevelopment/AlphaN
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.