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

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

 _    _ 
( )  ( )
`\`\/'/'
  >  <  
 /'/\`\ 
(_)  (_)
        
        

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

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

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:
Hi! My name is Sam Johnson. I live in Victoria BC, Canada. My project is an Onroad/Offroad Jeep. I am installing a '''GM 4.3L V6 engine''' * sequential EFI (Bosch 0.280.155.968 injectors) * wasted spark ignition (Bosch 3x2 coil) * a single Masterpower MPR R6164-12 turbo, 60mm external wastegate (with 4 way boost control solenoid) ** Air to Water aftercooler. ---- '''Trigger''' * 60-2 crank ** Primary trigger is a Gen4 58x GM sensor (grey in color.) It is a 3-wire sensor with a 5V supply, ground ref and signal output. The hardware is packaged in a round body housing a magnetic sensor and solid state electronics. The electronics convert the AC signal to logic level 0-5v square wave signal. It outputs a (supposedly) very clean waveform. What do I need to do for the vems to correctly interpret this signal? ** Here is pic of the crank reluctor (linked from EFI Connection web site.) http://www.eficonnection.com/projects/syty_engine/58xCrankshaftReluctor.jpg * 4x cam sensor (?) ** can you detail this ? Is that a VVTI V6 with 4 cams (2 intake + 2 exhaust sensors ) ? ** or 1 camsensor with 4 pulse-pattern ? How are the pulses timed (they should not be evenly spaced, at least that does not make sense for camsync/secondary trigger) ** secignore can be used to neglect eg. tooth > 13 (just an example), but of course sectrig pulse should only come every 2nd crankrot (tooth 0-12 in the example) There is a single cam sensor with an unevenly spaced 4 pulse-pattern. Here is a picture of the cam reluctor: http://www.eficonnection.com/eficonnection/images/4x_Cam_Reluctor_300w.jpg I am making an effort to find a waveform depicting the cam pulses referenced to crank position. Just capture triggerlog with * '''sectrig=falling''' * and '''sectrig=rising''' It is very likely that with rising or falling edge the first pulse after tooth0 will only be present (say, at tooth6) on every other crank rotation ... than secignore=9 can be used to neglect other sectrig pulses and sync fine. That should be it. Seeing your 2 triggerlogs we can help to configure. ---- Hoping to use VEMS genboard to control the engine with wideband EGO feedback and pre-turbo EGT thermocouple for tuning. I intend to get anti-lag working with my 3 speed automatic transmission (obviously anti-lag NOT required for shifts, only for closed-throttle deceleration and launch.) ---- Also hoping to use genboard on-board MAP sensor for '''dynamic BARO correction''' with an engine-mounted Bosch TMAP (2.5 Bar) as the primary MAP sensor. * baro correction can use external sensor (115 kPa, or same range as internal MAP sensor are most common to use, but... ) ** See [http://www.vems.hu/vt/help/v3/v3_engine_setup.html Barometric Pressure Correction] Do you mean to say " baro correction can use INTERNAL sensor " ? * yes, you can request in the order comment "an internally mounted baro pressure sensor connected to mcp3208" (dynamic compensation during running - dynamic baro compensation is required for mountain rally or airplane) * or even internal or external MAP sensor can be used for baro compensation if it's sufficient to sample barometric pressure at boot-time ** a common method for engines rarely driven at a much higher altitude than it was tuned... -20% pressure that requires appr +8.2% fuel can be handled easily by tuning +8% rich and leaning with wideband-lambda-ego. ---- Also of possible interest to the community is my effort to model the engine in Ricardo WAVE. I have a working model now but am still calibrating with dyno logs from similar engines. Once calibration is complete, I hope to link the model to a SIMULINK model of the VEMS. Has anyone modelled the VEMS firmware in SIMULINK? * Probably not
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.