Composite Logger, request for help with interpreting

[Buzda]

I have yet to start my jalopy after converting from DIS to COP. In an attempt to diagnose the no start condition I captured the attached Composite log file. Total noob question, but is the red line along the bottom an error indicator, and if so how do I correct/overcome the errors?

2016-07-02_17.29.58.csv

For reference here is my MSQ:

2016-07-02_17.59.04.msq

Thanks,
-john

[billr]

Yes, the red line indicates "sync errors", an error every time there is a vertical (red) spike. You want that red line to be a flat line. Just three teeth on the crank wheel? I can't say that won't work, but sure seems like the ECU is having to work with limited input, you may have to have everything perfect. Timing of the cam signal relative to the crank may be critical. I'll take another peek at the comp file, but am not too familiar with anything other than the easy-to-use 36-1 or 60-2 configs.

Post a tooth-log, too.

[slow_hemi6]

It is reading false tooth signals on both the Cam and Crank inputs. At one point together and another just on the crank. If it over or under counts crank signals between cam signals it will loose sync.

[Buzda]

I pulled all the spark plugs and captured the attached data logs.

Composite Logger.jpg

Physically the car is outfitted with a single window cam sensor, and a three tooth crank trigger wheel.

The data shows many different combinations. Does this imply that the crank and cam signals are noisy? Should my next step be to dig into the shielding on those two signal wires and/or move the harness away from the ignition coils?

Is there a TunerStudio Manual somewhere that describes all of the different types of loggers that TS has? I couldn't locate one on EFIAnalytics website nor in the MS Manuals section. Maybe I overlooked?

Thanks!
-john

[slow_hemi6]

In the Tuner Studio manual. Starts here. http://www.msextra.com/doc/pdf/html/Meg ... 4-318.html

[Buzda]

Thanks for the link!