Changes by last author:
Changed:
| Hi, try setting the trigger at 60 degrees before TDC. If you added your own trigger wheel, you have to check where the missing tooth/teeth are. |
| Odd-fire V2 bike engine ( it helps to state the case :-) |
| Second cylinder fires 420 degrees later, first cylinder fires again 300 degrees after that and so on. |
|
* 420/300 degrees
** (60 degrees V2 engine) |
| I assume the first cylinder is the rear one and that the crank rotates in the same direction as the wheels. |
| This install seems to have stalled because of neglecting 2016-11-22 recommendations to capture triggerlog with recent (eg. 1.2.31) firmware |
|
* Also review page, apply some cleanup, and correct errors (eg 34-2 and things like that)
---- Trigger setup * primary trigger on crank: 36-2 (not 34 - 2 as previously stated) ** VR-sensor sits at 65 degrees when cyl 1 (rear cylinder) is in TDC off the trigger tooth No. 6 and cylinder 2 is top off the tooth No. 12 Events aligned to 300/420, not 360/360 * we've set it up for the odd fire, we assume that it is correct. ** maybe. Odd fire means RPM is measured every 2nd trigger to smooth out the unevennes (essential for low toothcount "coil type wheels", might be needed here also) assuming a 36-2 trigger wheel I would set it up as 4 cylinder with individual spark delay * next trigger tooth = 18 (events every 180 degrees as a starting point) * individual spark delay=60 degrees where needed (verify triggerlog and with scope on bench, than with strobe-light) * use min 2 (4 if possible) unused ignition outputs (alternating fashion) in the slots where no ignition needed (no cylinder). Repeating any certain ignition output might shorten the dwell-limit (angle, matters at high RPM) for ALL ignouts. * try to enable odd-fire if RPM reading fluctuates, but also try with odd-fire=disabled. * use recent (>=1.2.31) firmware and publish triggerlog and .vemslog (captured with that) ** if you have triggerlog, and can export a reasonable wav from your triggerlog, can be useful (but triggerlog file still important) ** signalgen "m342" can be used to simulate 36-2 on bench (setting up soundcard+bench and LEDs is useful to start any odd setup before applying to real engine) ---- Try setting the trigger at 60 degrees before TDC. If you added your own trigger wheel, you have to check where the missing tooth/teeth are. |
|
Hello and thank you.
We have a trigger wheel 34 - 2 and our VR-sensor sits at 65 degrees when cyl 1 (rear cylinder) is in TDC off the trigger tooth No. 6 and cylinder 2 is top off the tooth No. 12 we've set it up for the odd fire, we assume that it is correct. And yes rotation direction is the same as the wheel spins. But it will not really run and when it does, it goes really hard and then goes out after about 10sec. |
|
Second cylinder fires 420 degrees later, first cylinder fires again 300 degrees after that and so on.
* first cylinder is the rear one * the crank rotates in the same direction as the wheels |
| Hello Dennis, |
| Hello Dennis, (2016-11-22 <= Continue from here) |
| Than regarding the triggerlog itself, good format and length, perfect. Your triggerwheel is 36-2 and signal is without errors. |
| Than regarding the triggerlog itself, good format and length, perfect. Your triggerwheel is 36-2 and signal is without errors. |
|
* in spark delay table use 0 60 0 60, this will cause the reftooth 24 cylinders to be offset by 60 degree.
* tdc delay should be around 65 degrees. |
|
* in spark delay table use 0 60 0 60, this will cause the reftooth 2,4 cylinders to be offset by 60 degree.
* TDC delay should be around 65 degrees. |
|
Thanks!
Best regards, Dave |
| <= IMPORTANT: required to continue. Required condition for support |
|
Yes, see if you can do a triggerlog like Dave suggests. (BTW, this is an odd-fire V2 bike engine). If the triggerlog looks nice, you probably just have the wrong amount of fuel or wrong basic fuel settings. Also, look at the top indicators in VemsTune. They will indicate trigger failure when the engine stalls, if the trigger setup isn't correct. |
| Yes, see if you can do a triggerlog like Dave suggests. If the triggerlog looks nice, you probably just have the wrong amount of fuel or wrong basic fuel settings. Also, look at the top indicators in VemsTune. They will indicate trigger failure when the engine stalls, if the trigger setup isn't correct. |