Dwell Time after spark event

[Keithg]

James,

I appreciate that you put this in the code just for me! Thanks! I do have a question, though. Has it been bench tested with the Jimstim in COP mode? Something is just odd and It may be that the time after spark is not right. I cannot really check anything but at idle. I am running a 36-1 and 2nd trigger. I'll run it as wasted spark tomorrow to see if that makes any difference.
It acts as if it has the proper dwell time after the spark, but above 3k, it seems to have a problem and it may be getting shorter. Is that possible?

KeithG

[Keithg]

Well, I increased the time after event and the problem seemed to go away. It may be that the value I was using was less than the COP circuit needed to spark properly. So far, it seems to run very smoothly and cleanly with the new time value.

I was running 0.1 and thought it was 1ms. The specs on the Saab DI cassette state that 0.5ms is minimum. No wonder I was blowing out the spark with fuel at 0.1ms! At 0.5 it works nicely. I may go to 1 just to make sure there is enough spark.

thanks, James, for putting this in!

KeithG

[Mitch318i]

Any idea what this value actually does?
I'm running 0.1 as well, I always assumed it had to do with telling the MS how soon another spark event can take place.
Maybe I should increase it farther.,
See specs below...

[Keithg]

This value is the dwell time after the spark event.

James put it in to drive a specific COP unit that used CDI. (Saab DI).
It needs the line to be held high then pulled low for a minimum of
0.5ms to create the spark. It then goes back high. If it gets pulled
down for a duty cycle (50% or what not), you can get to the point that
it will not fire or have enough energy to ignite the mixture.

What would be really cool is if we had another an A2D input and could
look at ionization energy by holding the line low for 60 degrees after
the firing event... but that is a totally different story for another
day. Very advanced COP unit.

KeithG

On 6/15/07, Mitch318i <me_mitch@hotmail.com> wrote:

Any idea what this value actually does?
I'm running 0.1 as well, I always assumed it had to do with telling the MS
how soon another spark event can take place.
Maybe I should increase it farther.,
See specs below...

[Keithg]

Ok, I think this is broken. I have been running this and trying many things over the past few days. I have tried leaning out the WOT bins for fear that they are too rich and blowing out the spark. I have tried many time values. I was running 1ms with MS1/E and that will not work at all, though it should according to the math.

http://www.msextra.com/viewtopic.php?p=164085#164085

KeithG

[Keithg]

Just tried again with the latest Beta 7/24. This is still broken. This time, basic trigger and 36-1 appear to function identically, but all flat line the spark outputs and effectively create a rev limiter. When Dizzy Mode was broken, it put out a very odd signal with this setup on a single spark output.

With 1.4ms dwell time after spark and 36-1 and second trigger (what I effectively ran with MS1/E), the rev limit is about 2450 rpm on my 4 cyl COP setup in the car. I can duplicate this effect with basic trigger with the stim. The spark output will flat line above a certain RPM and it is not to the point that the spark is running out of time.

The MSQ I am running is here:
http://ys3al35l.googlepages.com/ms2_08.msq

KeithG

[muythaibxr]

I tested this at all rpms on 36-1 but using wasted spark.

Could you possibly post your msq?

Thanks,

Ken

[Keithg]

MSQ is a link in the previous post.

Thanks for looking at this!

KeithG

[muythaibxr]

duh, I missed it, lack of sleep catching up with me I guess!

Ken