Crank Sensor pattern:
The choice to have the long gap detected at 30 BTDC and 0 TDC is weird.
- for fastest sync during cranking, 40 BTDC and 10 TDC would make most sense.
- for most precise timing during the whole range (and also for programmer's convenience) 90 BTDC and 60 BTDC would make most sense
Camsync:
The relative position of the cam (aving the camsync pulse coming inside the middle of the long gap) was a reasonable decision.
On both pics with the wheel, it turns anti-clockwise. The engine runs clockwise, but the pic is of the back of the wheel.
If we look at it as 15+3, 12+3+3 than the "funny part" is right after the 12.
- TDC is 30 crankdegrees after the single missing 2
- in other words, TDC is the 4th tooth after the single missing 2
There is a camsync signal 45 crank degrees before Cyl 1 TDC, then the second comes 135 crank degrees after TDC
svn ci -m "subaru 36-2-2-2 implemented first without camsync: derived from c012 - untested"
- |http://www.vems.hu/download/v3/firmware/experimental/ 1.1.78 experimental]
- start from a sane config, than at the bottom of primary trigger dialog click the subaru configlet (so primtrig subaru mode), than change:
- nr of tooth on wheel = 12 (yes, not 30 !)
- tooth width = 30 degree (=3 * normal tooth)
- another_trigger_tooth=6 if 4 cyl
- (3 if 8 cyl, but assuming 4 cyl here)
- reference tooth from top to bottom: 0 6 0 6 ...
- disable camsync (burn, and might need to reboot)
Please measure+figure how to set trigger tooth and TDCdelay.
(tooth 0 is after the long gap after the group of 16 normal tooth).
Test pattern
Here is a [wav file]
Here is a [vemscfg file] of the setup described above (trigger settings)
I had the trigger working early yesterday (but had drops to 0 or 220 RPM frequently) but late in the day it wasn't working at all. I can't find any setting that stopped it from working. The lm1815 is getting the signal, and the output looks right (20uS 5V square wave pulse), but no RPM registered. Changing from Fiat/Subaru to normal "Special Trigger" does show RPM, so there must be something with the tooth gaps not processing right.
Is there any way to tell which firmware build the ECU has (like in the case of several 1.1.78's, which one is it?) I'm quite confident I have the right one since I made a clean install of VT and only put the firmware just downloaded in to we webcache/fw directory.