[PSIG]

You have some weird stuff going on in that log. Please include the exact tune file used to take a log, as a pair.

Yes, agreed on all that about hardware testing. But, you can test coils on hardware test if you temporarily insert a ballast resistor into each active coil's power feed, typically just one-at-a-time for testing. Yes, the same big resistors used with old points distributor coils, with the same purpose - to protect the coil from extended over-current and over-dwell.

While not entirely risk-free, it may allow you limited testing for general spark, but is also slow enough to see when it fires (signal applied or removed, firing going high or going low).

[RowdyDouglas]

Attached ZIP contains log file from cranking and tune file.
@reliant_turbo, will you post your tune for comparison?

[RowdyDouglas]

I tried Trigger edge=Falling with basically the same results. A next step is to figure out how to view triggers in TS / logs to see how well the sensors are picking up edges. Secondary trigger edge is grayed out in tune I think because the cam sensor goes up for 360 then down for 360. I am still trying to understand decoder.ino, particularly I want to run sequential ignition but the decoder has decoderIsSequential=false. The next step I will probably to try is changing the tune to Single Channel Spark to see if that effects my logs.

[RowdyDouglas]

How do I view trigger readings in TS? I looked in the High Speed Logger, Logger Type=Tooth Logger but saw nothing in the graph area.
Sidenote: the Logs look the same regardless of Single Channel or Sequential Spark output mode.

[RowdyDouglas]

My new approach for troubleshooting is to reduce wiring connecting to Speeduino to only what is needed for crank and cam sensors and change tune to use a more basic decoder; this way I can at least make sure I am getting tooth logging.

[RowdyDouglas]

I removed all wires, except those needed for crank and cam sensors, and changed the tune to Dual Wheel. I got this screenshot from the composite logger which looks as I would expect. I later realized that cam detect are set to CHANGE in code rather than just RISING or just FALLING, so in later sketches I might be getting cam detect on rise and fall. Not sure why only cam falling seems to trigger here.

[RowdyDouglas]

How meaningful and trustworthy is Sync Loss # = 0 in logs? Attached is a screenshot of log (log and tune also, I dumbed down my tune to make sure I wasn't getting interference from injector PW or something, so ignore the VE and AFR tables). As you can see I don't have any sync loss but my RPM periodically dropping off seems concerning? Thoughts?

[LPG2CV]

I'm suspcious your tune is corrupt! it's showing an odd signature!

[RowdyDouglas]

Interesting thought. I started with the basic tune but am using a yet to be proven decoder that I renamed in the code. Maybe I should modify the decoder but leave it named Jeep200 so as to not miss renaming anywhere.

[LPG2CV]

I say that because the signature in the tune is 'speeduino 202108yj'. TS complained when I loaded the tune. TS could not find an ini with that signature.

Have you changed it deliberately?

Not saying this is the main issue.