/\    
    /  \   
   / /\ \  
  / ____ \ 
 /_/    \_\
           
           

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

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

   _____ 
  / ____|
 | (___  
  \___ \ 
  ____) |
 |_____/ 
         
         

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

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:
Any known of any succesfull setups for a flywheel based Bosch trigger setup. Such as Porches and early BMW´s. Most likely two VR sensors 116 + 1 Trigger 129 + 1 Trigger 130 + 1 Trigger 132 + 1 Trigger - Gunni * Are you sure that those 1xx numbers are trigger teeth? -Used to think that those are starter gear teeth and the +1 is the only trigger (?) - Gunni - Yes, the starter teeth are trigger teeth for the ecu to know the speed, the one trigger is to located the TCD and then the ecu can know the exact location from the starter teeth. ------------ individual power : What is the measurement exactly? * the difference of time spent between 2 pulses exactly 1 event apart (eg. 120 deg in 6cyl, 180 deg in 4 cyl) minus the last similar data I was thinking that whatever it is now it might be improved upon by having it calculate the time '''it should take''' from 0-90° (or an adjustable value) only and then report the delta time as crank angles. * inside the ECU firmware it is stored in 4 usec resolution. Of course in VT it can be displayed in crankangle (maybe it is already multiplied with RPM, or the ini can be tweaked easily). ** note that '''there is no "it should take" value, as RPM can change continuously'''. That's why - as the closest thing - it's displayed compared to last measured value (better than the average of last few). This would eliminate variation in a complete cycle due to other cylinders and concentrate solely on the firing cylinder. Then cylinders can be compared and misfires extremely clear and potentially knock could be determinable. * it seems the current implementation already gets as close as possible TPS accel enrichment : The scale in Vemstune is what appears to be millivolts against time, but there is no channel that represents this for measurement only an actual dTPS/dTime, it would be ideal to convert the scales to TPS/Time as if one where to replace the TPS with another the tuning wouldn´t have to be replaced as well as being closer on similar engines with different TPS´s. ----------- Lambda heater duty cycle monitoring. i have on a few occasions had a situation where lambda isn´t read for quite a long time even if engine has been run up to temperature , 10minutes for instance. Any reason to this? I want to be able to monitor the Heater DC% to determine if the heater is actually on or not. Lambda then usually comes in but takes way to long. Any update on this?? ----------- LSU 4.9 support? Is there support as Vemstune now suggest that there is
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.