History of MembersPage/Suzuki36-2-2
Older Newer
2022-02-09 07:28:47 . . . . 178.189.51.10 [splitting bogus pattern to make it less confusing]
2022-02-09 07:28:13 . . . . 178.189.51.10 [splitting bogus pattern to make it less confusing]
2022-02-08 10:42:43 . . . . customer-185-091-251-159.solcon.nl [reviewed current state, configlet upload problem found]
2022-02-08 08:03:58 . . . . 178.189.51.10 [pattern and wav]
2022-02-08 07:44:56 . . . . apn-94-44-228-192.vodafone.hu [triggerlog]
2022-02-07 21:34:43 . . . . 178.189.51.10 [Was specified wrong. Signalgen, trigger detect firmware mod, release, configlet,]
2022-02-07 14:48:03 . . . . 188-143-69-12.pool.digikabel.hu [Minor typo]
2022-02-07 12:48:09 . . . . apn-94-44-228-192.vodafone.hu [triggerlog]
2022-02-07 11:53:42 . . . . apn-94-44-228-192.vodafone.hu [question]
2022-02-07 10:51:41 . . . . 188-143-69-12.pool.digikabel.hu [Configlet]
2022-01-16 18:49:50 . . . . 254C3D51.nat.pool.telekom.hu [implemented]
2022-01-15 13:05:00 . . . . 254C3785.nat.pool.telekom.hu [note about cam photo: contradicts scopeshot]
2022-01-15 12:56:30 . . . . 254C3785.nat.pool.telekom.hu [signalgen 1 1 2 2 camsync implemented for 36-2-2]
2022-01-14 21:55:19 . . . . 254C3977.nat.pool.telekom.hu [camsync photo]
2022-01-14 20:02:55 . . . . 254C3977.nat.pool.telekom.hu [sectrig same as sSuzuki 36-2-2-2]
2022-01-14 15:49:17 . . . . 254C0D39.nat.pool.telekom.hu [36-2-2]
2022-01-14 14:40:05 . . . . 254C0D39.nat.pool.telekom.hu [sectrig]
2022-01-14 14:14:13 . . . . 254C0D39.nat.pool.telekom.hu [36-2-2]
2022-01-14 14:04:12 . . . . 254C0D39.nat.pool.telekom.hu [36-2-2 pic]
2022-01-14 10:53:03 . . . . 254C0D39.nat.pool.telekom.hu [if exists and different]
2022-01-14 10:42:54 . . . . 254C0D39.nat.pool.telekom.hu [teeth]
2022-01-14 10:24:05 . . . . 254C0D39.nat.pool.telekom.hu [36-2-2]


Changes by last author:

Changed:
However, was originally specified wrong .... as tradition for 36-2-2-2 (was also specified wrong imitially).
However, was originally specified wrong .... as tradition for 36-2-2-2 (was also specified wrong initially).

See MembersPage/BogusSuzuki36-2-2

Changed:
Signalgen, trigger detect firmware mod, release, configlet, testing done according to the specified wrong pulsetrain.
Signalgen (z342), trigger detect firmware mod 1.2.44, release, configlet, testing done according to the specified wrong pulsetrain.

* Luckily apparently new firmware is not needed

** [trigger configlet] should still apply with minor config change secignore=01 for the new pattern.

Changed:
The actual is:
The actual pattern:
Changed:
Note that sectrig pattern is 24 tooth based, not 18 teeth... (total is 3*24 not 4*18)

swift_trigg03_scope.png

trig07_camsync_clet.png

http://www.vems.hu/files/MembersPage/Suzuki36-2-2/trig_07_camsync_clet.wav

http://www.vems.hu/files/MembersPage/Suzuki36-2-2/v3.3_u022060-A-2022.02.07-13.28.53_trigg_camsync.vemscfg

http://www.vems.hu/files/MembersPage/Suzuki36-2-2/v3.3_u022060-2022-02-07-13.35.02.triggerlog

Note that sectrig pattern is 24 tooth based, not 18 teeth... (total is 3 groups 240 crankdeg apart not 4 groups 180 crankdeg apart)

Changed:
* Or secignore=01 or 00 might be tried instead of 02

** Please report RPM and vemslog with sectrig disabled also, if no success with enabled

* Try secignore=01 (instead of 02; 00 is unlikely to work well).

** If no success with secignore=01 and sectrig enabled, please report RPM and vemslog with sectrig disabled also

Changed:
NOTE: camwheel image contradicts "scopeshots" (and drawing) regarding the width of first tooth of the double campulse.

Most likely the sectrig falling edges are inside the tooth-runs (either 1 or 2 falling edges, depending on cam position).

Suzuki_M16_36-2-2-2_camsync.png

----

(2022 or newer) Signalgen z342 . please check wav in audacity and compare with your real scopeshots (provide your scopeshots or triggerlogs)

* [signalgen generated z342 wav, camsignal with 12crankdeg offset] - believed to match real signals

* [OLD WAV with 1 pulse camsync] - known to differ from real signal (perhaps close with grinded camwheel)

Suzuki_36-2-2_M16_signalgen_z342_primtrig_and_1_1_2_2_sectrig_camoffset12.png

Check where the double campulse hugs the 36-2-2-2 single missing => it is fully inside the short (10 teeth) run of the 36-2-2 because of the different positions of the primtrig missing tooth.

(Suzuki assumedly changed the crankwheel so that initial syncup at cranking can be a few teeth faster with sophisticated code.)

2022.02.07. Question: How can I set this trigger without camsync? It is available default pattern, or should I set some special? Thanks, Roland

I did triggerlog with a configlet from Marcell.

swift_trigg03_scope.png

trig07_camsync_clet.png

http://www.vems.hu/files/MembersPage/Suzuki36-2-2/trig_07_camsync_clet.wav

http://www.vems.hu/files/MembersPage/Suzuki36-2-2/v3.3_u022060-A-2022.02.07-13.28.53_trigg_camsync.vemscfg

http://www.vems.hu/files/MembersPage/Suzuki36-2-2/v3.3_u022060-2022-02-07-13.35.02.triggerlog

2022.02.07. Question: How can I set this trigger without camsync?

The same configlet, just disable sectrig (no camsync; Burn and reboot).