So just curious about using a dial-advance timing light with our wasted spark systems. I've head you half the reading for actual degrees off the crank, because of the way the light calculates the advance. Would that mean if I shot the notches of the cam gears it should be dead-on? Cam timing would be half the crank, then doubled for the light would make it actual... makes sense in my head

Since timing is ECU controlled, it'd fluctuate while you were trying to watch it. Kinda hard to use a timing light when the timing keeps moving around...

sig... ms2. Tryin to verify trigger angle. I know it might-should go in the engine management section, but thought it was a general enough question.

if you set your spark map for, say, 10* across the board and let it idle, it should stay steady enough for you to check it with a timing light. With a stocker, there's no way to lock the timing in place.

i know that, and that is what i did on my maps. I just want to know about using a light with wasted spark, configurations and all, if any degree adjustments/mulitpliers need to be considered for actual reading, when taken off cam gears.

No need to change your Spark Advance tables... just go to the More Ignition Settings menu and change to Fixed Timing and set the degrees you want... then hit it with your timing light. No problems with wasted spark and timing light.

Don't forget to change your timing back to use the tables again.

You're not going to be able to check the crank angle by lighting up the cam gears. You're going to have to find top dead center and mark your pulley and timing cover. You really don't need to do this at all because your trigger angle will always be zero. The trigger wheel is machined into the crankshaft and the sensor is non-adjustable. What you see in Megatune is your total ignition timing.

I assumed this, but it just seemed to buck at zero, and ran more smoothly with trigger aroune -8. I've heard of at least one guy on neons.org that said his was off about -4. I know the sensor/crank is unadjustable, but there may be something in MS that is off a bit. I'm just tryin to verify before i re-edit all my spark maps again

hmm, dunno.