_____  
 |  __ \ 
 | |  | |
 | |  | |
 | |__| |
 |_____/ 
         
         

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

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

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

 ___   
|  _`\ 
| (_) )
| ,  / 
| |\ \ 
(_) (_)
       
       

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:
Genboard is not designed for racing use and it haven´t some fuctions than are very usefull in racing: This fuctions (ordered by importance) could be: *Quick shifter *Datalogging (to tune ecu on track) *LCD Dash with RPM bar and Temperature (to replace original dash) '''Quick shifter''' - to shift up with full throttle. It is very simple method, if you are full throttle and you try to shift then you feel than lever is very hard and it is unable to move because torque make impossible gears to be un-engaged. The quick shifter fuction cut ignition for a short time when rider or driver try to shift gear. It could be simple, A simple ignition skipping during programmable time when input line is actived (ignition is reactived despite input line continue active. MembersPage/JoseLCortes/QuickShifterSensorsTypes '''Datalogging''' I think there are others users interested in logging fuction of Genboard. It is only a personal opinion of this stuff: Which type of datalogging is necessary on a ecu? Profesional data logging like 2D datarecording have very complex pc software, otherwise on ecu only some fuctions dedicated to tune engine are necesary. Why datalogging? the fuel map and ignition map setting in race vehicles never work in closed loop. The method to tune engine is very easy. the data logged are downloaded to a pc-software and analyzed, then consequent changes are maked in ecu tables. Which channels are necesary? Any internal variable of the ecu would be suitable to record but I think there are funtamental four channels *vehicle speed *throttle position *lambda *knock??? (i have never use it, i have never modify ignition tables on track) The frequency with which one samples each piece of data can be different, engine coolant temperature maybe only every 200 ms but MAP must have much higher sampling frequency. This can save precious space. -MS '''LCD Dash with RPM bar and Temperature''' alphanumeric or grafic display showing RPM bar and engine temperature and shifter flash (a number of led shoot a light flash when programmed RPM are exceeded. Another interesting fuction could be: Drivebywire - It could be a lot of fuctions *Lower gear power output reduction - The GSXR and motoGP bikes have a shift gear position sensor, In the lower gears the engine power output is decreased. By the time 6th gear is selected the engine realises its full potential. Only MotoGP have pure drivebywire, street bikes like Yamaha R1 and GSXR1000 have a secondary throttle valve (two throttle valve in the same thottle body, one manual handled and the other servocontrolled), it is managed exactly in the same way than drivebywire but it is more sure. [http://www.nmine.com/msavr/sec_throttle.jpg throttle_bodies] *Traction control acction. *Torque improve at low RPM, in high speed engines with long duration cams at low RPM the engine delivery more torque with partial throttle than at full throttle.
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.