|\     /|
| )   ( |
| |   | |
| |   | |
| |   | |
| (___) |
(_______)
         

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

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

 _____ 
|  _  |
| | | |
| | | |
\ \/' /
 \_/\_\
       
       

  ___ 
 |_ _|
  | | 
  | | 
 |___|
      

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:
New Boostcontrol strategy allows '''even easier configuration''' since firmware 1.2.9 '''Overview''' * '''reference DC can be configured in a 2 dimension table: as a function of RPM, boosttarget''' * with this "target based reference PWM duty", PID boost is easier to tune for very quick reaction and small overshoot ** if the hardware actuator is good PID can be configured to switch to PD when boost is way too low, or to PI when boost is too high * actually, configurable thresholds for operation ranges: * boost off * max-DC (to help spoolup) * ref-DC * ref-DC + PD * ref-DC + PID * ref-DC + PI ---- '''Mattias Sandgren was kind to contribute''' some documentation embryo - will be moved to [http://vems.hu/vt/help/v3/v3_boost_control_pid.html VT help] at "birth-time" Begin by setting the "Boostcontrol PID integral limit" to 0 and adjust the "refDC Table vs boost target" so that you get a good starting point for enabling the PID regulated boost controller. Apply max DC until To shorten turbo spool time you can apply the maximum dutycycle allowed. This can only be done up to a certain limit below the boost target, set this limit here. This must be kept low enough to avoid an initial boost target overshoot that the PID regulation will not be able to stop. PD control (far from target) PI control (close to target) PID overlap range Boost P, I, D Boost control PID integral limit Set how large the integral is allowed to build up. This value is what is added/subtracted to the reference dutycycle in order to reach boost target. In effect setting this to 0 will disable the boost control PID regulation completely and you will just send reference dutycycle to the boost control valve. (needs some explanation of how much x of max is, like what is normal limit, etc) Boost PWM maximum value Limit the maximum dutycycle the boost control valve receives. Boost PWM minimum value Limit the minimum dutycycle the boost control valve receives. ---- Copied from IRC discussions : Overlap is PID mode, where its far enough from target to still might need the D term PD is for not winding the integral up when too far from target PI is close to target (its now control range) when close to target, PI only is used, as D wouldnt make any big difference anyway so it can be used with higher settings from far away, still not messing with close to target control What is the buildup range and control range? Buildup integral is frozen and control derivate is disabled. It means "too far from target, probably not physically possible to reach, don't build up a integral error" and disabling D term "close enough to target, error for P is small, so no D needed". Overlap is PID P is not active between max dc and buildup Buildup = I frozen outside this range buildup enables PD control is PI between buildup and maxduty there is referece only Future ? the buildup range might go, just enabling PD from maxduty its easier to find the optimal P if its scaled in kpa / % --- (may2013 FPhil)This is what I get from above, I hope that is correct ||DOMAIN || zero to maxDC||maxDC to BuildUp||BuildUp to Cntrl||Cntrl to Target||Target to ? (Overlap)|| ||STRATEGY||DC|| ?? || PD || PI || PID|| ||PARAMS|| ||PWMmin & max||id & I limit||id & I limit|| id & I limit || What happen if for some reasons boost enter the Cntrl to Target domain at fast increase? one can then expect a large overshoot. * he needs to tune better then. The Boost-buildup depends on the settings, eg maxDC and the ref-PWM table values. ** The good strategy is to tune from low-boost (and low values in REF-DC table), only climbing as the control is tuned and confirmed to be consistent. ** or you mean "what if some tube comes off, resulting in unexpected boost sky-rise" ? Yes, that is a concern.. even worse, in many cases the control could hardly do anything about it (or it would be very time-consuming to tune the parameters/thresholds to notice that some tubes came-off and limit boost some other way, eg. with intentional misfire - maybe feasible for 1 million engines but possibly more risk for a few engines than it saves)
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.