_____ |__ / / / / /_ /____|
## # # # # # ###
#### ### ## # #### ### # ## ### ###
___ / _ \ | | | | | |_| | \___/
### ## ##### ## ## ##
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: '''Mitsubishi EVO VI-VIII''' *4 cyl, 2.0 4G63 engine *Vems V3.3 *wastedspark active coil *turbocharged *stepper IAC valve *4 bar MAP sensor * '''HALL crank sensor''' * '''HALL cam sensor''' My plan is to use the stock trigger system. It is important because the race rules don't allow to modify it and mitsubishi EVO-s are more than 90 percent of the racecars here. It's a very big market. Here is the stock crank triggerwheel. It has two simple big 67 deg tooth, The '''rising edge of the tooth is about 67-70 deg before TDC''': http://www.vems.hu/files/Fero/mitsubishiEVO/crank1.jpg http://www.vems.hu/files/Fero/mitsubishiEVO/crank2.jpg ------ And here is the problematic cam trigger: a bigger and a smaller tooth, '''I don't know the exact TDC position yet''' => '''The position would be VERY important. A scopeshot (both triggers) would help a lot''': http://www.vems.hu/files/Fero/mitsubishiEVO/cam.jpg * Erik Englund grinded off 1 tooth earlier, and used it as 4+1 trigger system. * We are working on firmware implementation (and related config) to support the factory trigger ** we assume that the 270 degree big camwindow (HALL is high or LOW there?) contains 2 primary triger pulses (rising edge of the crank-HALL) '''Please measure the positions'''. It is possible that the big camtooth "overlaps" the crankpulse rising edge, while the short camtooth not. In this case we can make a simple (2-line) filter in the cam-trigger-code to filter out the small tooth. Otherwise it's a bit more complex, but let's see first. Maybe the multitooth bit in the config.secondary_trigger could be used for this (actually seems like a good place, not currently used). MembersPage/PhatBob - Rob Van Asbroeck has this engine running on simple trigger with one of the cam teeth removed. Triggerlog from evo3, one with rising, one with falling edge for cam sensor: http://media.vems.se/mitsu/ 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.