# # ##### # # # # ##
_ _ | | | | | | | | | |_| | \___/
______ | ___| | |_ | _| | | \_|
## ## ##### ## ## ## ## #####
##### # #### # #####
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: Subaru JDM/Euro EJ207 CarInfo: Subaru Impreza STI JDM/EURO 2001-2005 (265-280)standard pink topfeed injectors 550cc Cop ignition coils firing order 1-3-2-4 the engine is a '''boxer engine''', there for there is right and left cyl 1+3 is right side cyl 2+4 is left side 1: __primary trigger__: Crank trigger Vr (36-2-2-2) http://img.photobucket.com/albums/v41/Denmark/crankwheel1modi.jpg 2: __secondary trigger__ : Cam trigger Vr left '''cam(2pulse)none moving''' http://img.photobucket.com/albums/v41/Denmark/a1463ee5.jpg This is the trigger setup to get the engine running sekventiel http://img.photobucket.com/albums/v41/Denmark/cf70e38a.jpg 3: __Third trigger__ : Vvti intake cam left side Vr sensor (boxer)4 spots/90degrees moves when avcs is controlled ** any idea at which primtrig tooth does it cross the 0V line (negative-going edge) ? *** no sorry, this is scopeshot while cranking 180rpm http://img.photobucket.com/albums/v41/Denmark/f4480a56.jpg 4: __4th trigger__: Vvti intake cam right side Vr sensor (boxer)4 spots/90degrees moves when avcs is controlled. With the "wheelspeed2 calibration=1" config, "secondary trigger position" will reflect the angle of this (so control will use this as feedback signal instead of sectrig) ** any idea at which primtrig tooth does it cross the 0V line (negative-going edge) ? *** no sorry, this is scopeshot while cranking 180rpm http://img.photobucket.com/albums/v41/Denmark/558e660f.jpg See 1.2.4 on GenBoard/UnderDevelopment/FirmwareChanges , it refers very clearly to where the 3d and 4th trigger 0/5V logiclevel pulses must go in. This setup uses all 4 vr sensors: * since "only" 2 VR => HALL LM1815 chips are onboard ** obviously 2 VR => Hall adapters needed (for 3rd and 4th cam sensor inputs). ** Unlike when used for wheelspeed, both __withOUT divider__ (which unfortunately results in MUCH shorter pulsewidth), and because of the shorter pulsewidth filtering capacitor must not be used (must be removed if the controller was ordered with wheelspeed2 input !) ** '''Trigger4 via VR=>HALL adapter''': wheelspeed2 input (without heavy filtering and without divider) used for 4th trigger. '''Summary''': * Triggers 3 and 4 seem to be unsuitable for secondary trigger camsync, (because they are indistiguishable in both crankshaft rotations - unlike the sane implementations in BMW, Honda, Suzuki, Ford, ...). * The cam sensor is good for secondary trigger camsync, but not moving, so useless for camshaft-angle control * in other words "the good trigger doesn't move with camshaft actuation, the moving ones are not good pattern for syncing". __Firmware mod was implemented in 1.2.4 to use all 4 sensors__, see GenBoard/UnderDevelopment/FirmwareChanges : with wheelspeed2 calibration=1 "sectrig position" measures "4th trigger input" (SCL pin similar to 2nd wheelspeed input) ** a good workaround, required because the camsync does not move with cam actuation (and the signals that move are not suitable for camsync as it would make sense like in all other VVTI implementation BMW, Honda, Ford, etc...). ---- Is this correct? http://www.vems.hu/files/MembersPage/PeterJensen/subaru/Subaru-cam-trigger1.jpg 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.