History of MembersPage/JasonRussell/SubaruSTi
Older Newer
2011-08-05 12:21:47 . . . . 3e44ba0f.adsl.enternet.hu [subaru-nocamsync hints]
2011-08-03 15:42:54 . . . . MembersPage/JasonRussell [Added config saved during the firmware upgrade, please benchtest]
2011-08-03 15:34:35 . . . . MembersPage/JasonRussell [Added config for bench testing/review please]


Changes by last author:

Changed:
Process for upgrade: Connect to ECU, Upload 1.1.95 which saves the config, after the upgrade it asks if you want to re-apply the saved config. I answered yes, asked if you want to fill in missing values with defaults, I answered yes.
Process for upgrade: Connect to ECU, Upload 1.1.95 which saves the config, after the upgrade it asks if you want to re-apply the saved config. I answered yes, asked if you want to fill in missing values with defaults, I answered yes.

Without camsync, you have to use [1.1.97] or newer (or the old ~1.1.85)

* around the AVCS changes, the subaru+camsync was made more versatile, but subaru + nocamsync was shortsightedly used up by the originally misdefined evotrigger around 1.1.91: available for subaru+nocamsync again in 1.1.97

** the code stealing the config was dropped (after the mitsubishi evo was defined properly with real scopeshot and triggerlog, it has a different implementation anyway with a non-conflicting config).

* just to be sure, from primary trigger dialog upload 'configlets/trigger/subaru 36-2-2-2_noCamSync.txt' after upgrading to 1.1.97

** and review the validate results

* the code supports the sectrig (with camshaft-position measurement for VVTI-AVCS) in a variety of combinations (including the old double-pulse camsync), see [VT help]

* capture triggerlog, preferrably with both trigger enabled.