Hello!

I have now done some more testing and scoping on the ignition.

I have noticed that the ignition timing is lagging with higher revs even if the angle is set to a constant angle.
To test this I made an ignition curve with a constant 40deg advance. I can then see that the angle decrease almost 10deg at approx 17k.
When looking at the scope, it sems there is a delay of abt 60us from the pulse on the input arrives until the output reacts. This is with the 40deg curve (all constants in the code is 00).
When calculating it, a delay of 60us would give a spark retard of 3,6deg @ 10k rpm, so this seems logical (since I only have an approximate delay value).
I think all processor controlled ignitions have some lag, and that is why the trigger always needs to be set in advance, so there is time to compensate for the lag.

The question here (to the one who made the code I guess) is if the 60us delay I measured seems reasonable based on processor speed/number of operations?

I think there could be a possible solution to the problem as well:

-If I'm not mistaken, the C-code contains delay-values for diffrent RPM's, and if we know the format of these, we could remove 60us from all delay values to compensate for the delay in the processor.
I think ths could easily be incorporated in the Excel sheet?

-The trigger would also need to be a few degrees ahead of the maximum ignition angle to give the processor some time to do the math(higher reving engine would need trigger to be further ahead).
I think the 'trigger advance angle' could also be included as a constant in the Excel sheet?

What do you think guys? Maybe it's not so critical for you? I guess the airplane engines operate below 10k?

I have been running the engine quite a lot on a stand now, and the ignition seems to work flawlessly exept from the delay-issue.