_       
| \    /\
|  \  / /
|  (_/ / 
|   _ (  
|  ( \ \ 
|  /  \ \
|_/    \/
         

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

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

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

 _______ 
(  ____ \
| (    \/
| |      
| | ____ 
| | \_  )
| (___) |
(_______)
         

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:
Need some help with '''4cyl crank + camsync triggersetup'''. '''60-2 Cranktrigger''' Ditributor with one "tag" for camsync, fully adjustable. Currently 90* btdc cyl1, perfect. But is that for rising or falling edge? How wide is it? If only a few degrees, it does not matter. http://i4.photobucket.com/albums/y123/tomik85/crtrigger.gif The missing tooth points down when cyl1 is at TDC. So depending on rotational direction: * tooth0 is appr. 80 degrees before cyl1 TDC * tooth0 is appr. 260 degrees before cyl1 TDC, so 80 degrees before cyl2 TDC (cyl2 is just before cyl1 in common 1,3,4,2 sequence) In any case, trigger_tooth=03 ign_tdcdelay=7C (use timing light to finetune ign_tdcdelay) # One squirt per camrevolution sounds good divider=01 alternate=03 # or alternate=13 would also use 3..0 entries in h[0], but fire all channels at cranking rpmk[0]=0B rpmk[1]=B8 # This is a little bit strande in manual/edis, can somebody please explain? => Currently these are not used. cam_sync_f_edge_phase=03 cam_sync_r_edge_phase=06 reset_engphase_after=F0 # decimal 240 # this is not cam nor crank degrees. # it's 720 degree / reset_engphase_after = 3 crankdegrees (but they are not used at the moment) tooth_wheel_twidth1=02 tooth_wheel_twidth2=06 primary_trigger=01 # from global.h : uint8_t secondary_trigger; // trigger2, bit0 0:falling/1:rising, bit1 0:enable/1:disable, bit2 0:no filtering/1:filt ering, bit3 0:toothwheel/1:coil, bit4 0:alien advance/1:cam sync, bit5 0:single edge/1:both edges when cranking secondary_trigger=1d # single edge, camsync, coil type,filtering, enable, rising edge # provide info about HALL signal rising and falling tooth positions so we can doublecheck consistency trigger_tooth=03 another_trigger_tooth=1E # (decimal 30) teeth from triggertooth ign_tdcdelay=7C # decimal 124, which is 62 degrees tooth_wheel=3A # 58 teeth between the missing tooth crank_minper=50 # for std. coil tach signal ign_crank_advance= #advance from tdc. 0.25 degree resolution, like if it was in the n[] table, just that engine.rpm < config.cranking_thres it does not depend on MAP, just one value in config ignchmax=03 # yes h[2]= .... provide info about your ignition wiring Old stuff ----- Hi CapriceTwinTurbo - I'm about to install genboard 3.2 in a caprice 66 460cui twinturbo. Just a little experiment in my sparetime Made a triggerwheel (60-2) and built an expanded Stimboard Runs ok in a drillpress after som fiddeling with config Some questions: See GenBoard/Manual/Tables for tables dimensions. * The are many '''free inputs''', primarily the MCP3208 ADC inputs. I counterrecommend using uC pins directly. * MCP3208 inputs can be used for analog (up to 12 bits resolution and beyond with filtering) or on/off or steps (like gear1, gear2, ....). * Make sure you don't exceed 5V (use 10..100k protecting resistor on the input if unsure) * Just connect the one that is convenient and is likely to remain free in your install. Check the schematic, they have recommended mapping like fuel-pressure, exhaust backpressure, EGT1, EGT2, etc... * We have to check the ALS code how it can be setup to use that. (yell 4..7 days in advance for firmware feature of this amplitude). * 2step revlimiter seems simple, but what is the purpose? If it's for wife and repair-crew, the revlimit depending on authentication button (see ButtonImmobilizer) is the good solution. Revlimit is not normally reached, so I don't see other reason for 2 step revlimit than restricting someone, so the simple switch makes little sense. The 2step revlimiter is for dragracing application, when clutch is "in" i want the engine to rev 4500 but with full throttle When i release the clutch the revlimit should go up to 10000rpm RedMist wrote: Emil, standard two step launch controllers are a little more complex than that. You want to offer a ramping rate then a cutoff RPM. This will keep your wheels from spinning immediately after clutch release. IE You two step the car, both clutch and accelerator depressed (you'll need a basic switch, like a brake light switch on the clutch). The car sits at a pre determined RPM (4.5k) then ramps up slowly, say 1000rpm / sec and introduces either a misfire and or fuel restriction in order to stop too much power from spinning the rear wheels. At another pre determined RPM the ramping switches off and you are allowed to rev right to the standard RPM limiter. All that being said, if you have the ability, you are much better off modulating the throttle plate yourself. The plates introduce turbulance at low / mid RPM that keep fuel in suspension. IE You have more HP at 4000 RPM with a part throttle than you do at WOT. This may not necessarily be true on a single throttle body, however is proven dyno true on my ITB Toyota. I'm sure there is a page in the WIKI dedicated to launch control. However I'm having issues finging it.
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.